Skip to content

Commit ad622af

Browse files
authored
Merge pull request #195 from righettod/master
Add note from discussions 29.
2 parents 146270d + b3508dc commit ad622af

File tree

2 files changed

+13
-0
lines changed

2 files changed

+13
-0
lines changed

assets/misc/backup_discussions_29.pdf

1.44 MB
Binary file not shown.

tab_bestpractices.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,7 @@ tags: headers
1515
* [Prevent CORS misconfiguration issues](#prevent-cors-misconfiguration-issues)
1616
* [Prevent information disclosure via the browser local cached files](#prevent-information-disclosure-via-the-browser-local-cached-files)
1717
* [Prevent CSP bypasses](#prevent-csp-bypasses)
18+
* [Support for a large CSP policy](#support-for-a-large-csp-policy)
1819

1920
## Configuration proposal
2021

@@ -358,3 +359,15 @@ This section describes some points, to keep in mind, during the creation of a [C
358359
📺 This [demonstration video](assets/misc/demo_csp_bypass_due_to_no_frame_ancestors_directive.mp4) show an example.
359360

360361
💡 Therefore, ensure to always specify the `frame-ancestors` directive in a CSP policy to at least, the `'none'` value, to deny the current domain to be "framed".
362+
363+
## Support for a large CSP policy
364+
365+
Tests were performed to identify if any limitation was in place, regarding the definition and usage of a large CSP policy. Tests were performed against the following browsers:
366+
367+
* Firefox `132.0.2`.
368+
* Chromium `131.0.6755.0`.
369+
* Edge `131.0.2903.51`.
370+
371+
💡 Based on tests performed, modern browsers supports a sufficient size to specify a large CSP policy in case of need.
372+
373+
📊 Technical details can be found [here](https://github.com/oshp/oshp-tracking/discussions/29) ([backup copy](assets/misc/backup_discussions_29.pdf)).

0 commit comments

Comments
 (0)