@@ -12,6 +12,11 @@ and use the list below as suggestions for a checklist that has been tailored for
12123 . Deny by default; if a request is not specifically allowed then it is denied
13134 . Apply least privilege, providing the least access as is necessary
14145 . Log all authorization events
15+ 6 . Create unit and integration test to document and verify an application's business rules, data types and access
16+ authorization criteria and/or processes so that access can be properly provisioned and controlled for restricting
17+ function-level, data-specific, and field-level access based on consumer permissions and resource attributes
18+ 7 . Access Control criteria and/or processes not testable through automated tests should be documented so that they
19+ can be manually tested
1520
1621#### 2. Access control
1722
@@ -26,6 +31,17 @@ and use the list below as suggestions for a checklist that has been tailored for
26318 . If long authenticated sessions are allowed, periodically re-validate a user's authorization
27329 . Implement account auditing and enforce the disabling of unused accounts
283310 . The application must support termination of sessions when authorization ceases
34+ 11 . Restrict function-level access to consumers with explicit permissions
35+ 12 . Restrict direct object references to only authorized users with explicit permissions to specific data items
36+ to mitigate insecure direct object reference (IDOR) and broken object level authorization (BOLA)
37+ 13 . Restrict access to user and data attributes to consumers with explicit permissions to specific fields to mitigate broken
38+ object property level authorization (BOPLA)
39+ 14 . Restrict access security-relevant configuration information to only authorized users who have been allowed access through
40+ multiple layers of security, including continuous consumer identity verification, device security posture assessment, and
41+ contextual risk analysis
42+ 15 . Server side implementation and presentation layer representations of access control rules should not differ in such a way
43+ that they allow for business functionality and rules to be compromised
44+ 16 . Enforce application logic flows to comply with business rules
2945
3046#### References
3147
0 commit comments