7.3.3 The access control system(s) is set to “deny all” by default
The access control system(s) is set to “deny all” by default.
5
artefacts
1
held by a system
2
at each review
hard
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Configuration evidence for each in scope access control system, not only the primary one · Identity provider / directory
periodic reviewEvidence produced at each review
- Test evidence that an identity with no assigned permission is refused · Identity provider / directory
- Evidence that default or built-in permissive entries have been removed or restricted · Identity provider / directory
governing documentDocuments that govern the control
- Vendor documentation and system settings showing the access control system is set to deny all by default · Policy repository / GRC workspace
- Change control preventing the default from being relaxed · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Identity provider / directory on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Default deny at the application while the database or file share underneath grants broad read
- Built-in groups such as everyone or authenticated users left with permissions, defeating the default
- Deny all asserted from product documentation with no test on the actual deployment
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet7.3.2 The access control system(s) is configured to enforce permissions assigned to individuals, applications, and systems based on job classification and function · 8.1.1 All security policies and operational procedures that are identified in Requirement 8 are: • Documented. • Kept up to date. • In use. • Known to all affected parties