Skip to content
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.

Sign up for GitHub

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

Jump to bottom

extend the explanation why ANSSI R52 requirement is manual #11629

Merged
merged 1 commit into from
Feb 27, 2024
Merged

extend the explanation why ANSSI R52 requirement is manual #11629

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion controls/anssi.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1120,7 +1120,15 @@ controls:
title: Securing access for named sockets and pipes
levels:
- intermediary
notes: We cannot easily automate securing of named sockets and pipes in a general way.
notes: |-
The requirement states that all sockets and named pipes within all mounted
file systems should be checked. The check should look at the permissions
of the socket / pipe and compare them with permissions of the directory
which contains the particular socket. In case permissions of the directory
are less stricter than permissions of the socket, this should be
considered a finding. Since different use cases can require different
permissions for named pipes / sockets, it is not possible to perform this
check automatically.
status: manual

- id: R53
Expand Down
Loading