-
Notifications
You must be signed in to change notification settings - Fork 81
Improve and extend the security checklist #2565
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Reorganised the checklist to make it more intuitive.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Self-review.
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
|
regarding 'powered by' we should probably give explicit instructions, like: ibexa_system_info:
system_info:
powered_by:
# major => v4 || minor => v4.6 || none
release: major
# true || false
enabled: true
|
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me (as far my technical knowledge goes here).
One thing regarding "Security headers":
Probably we should review our cloud vcl for varnish and fastly, if we are following our own guidelines?
|
@reithor I and others have held back on the security headers due to the need to adapt them to the site in question. Generally there isn't a "safe setting" that can be applied for everyone. But I have been reconsidering. We could change vcl and vhost templates, they won't affect existing sites. We could set at least Strict-Transport-Security, and X-Content-Type-Options to nosniff. For the admin ui we could set all of them. |
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some smaller nitpicks - the HSTS header with Varnish being the most important one
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
docs/infrastructure_and_maintenance/security/security_checklist.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Tomasz Dąbrowski <[email protected]>
Co-authored-by: Tomasz Dąbrowski <[email protected]>
Co-authored-by: Tomasz Dąbrowski <[email protected]>
Co-authored-by: Tomasz Dąbrowski <[email protected]>
Co-authored-by: Tomasz Dąbrowski <[email protected]>
Co-authored-by: Tomasz Dąbrowski <[email protected]>
Co-authored-by: Tomasz Dąbrowski <[email protected]>
Co-authored-by: Tomasz Dąbrowski <[email protected]>
Co-authored-by: Tomasz Dąbrowski <[email protected]>
Co-authored-by: Adrien Dupuis <[email protected]>
Co-authored-by: Marek Nocoń <[email protected]>
Co-authored-by: Marek Nocoń <[email protected]>
|
Thanks for all the reviews, very useful. I believe I have answered all comments and applied all suggestions now, and it's looking good. Please have another look, if you had concerns earlier. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me now!
--------- Co-authored-by: Tomasz Dąbrowski <[email protected]> Co-authored-by: Adrien Dupuis <[email protected]> Co-authored-by: Marek Nocoń <[email protected]> (cherry picked from commit 270e2e3)
--------- Co-authored-by: Tomasz Dąbrowski <[email protected]> Co-authored-by: Adrien Dupuis <[email protected]> Co-authored-by: Marek Nocoń <[email protected]> (cherry picked from commit 270e2e3)
Reorganised the checklist to make it more intuitive, and added more advice:
Preview: https://ez-systems-developer-documentation--2565.com.readthedocs.build/en/2565/infrastructure_and_maintenance/security/security_checklist/
Checklist
Code samples are working(no changes to code samples)PHP code samples have been fixed with PHP CS fixer(no changes to code samples)Added link to this PR in relevant JIRA ticket or code PR