ASVS V4 Access Control

Jump to: navigation, search

V4: Access Control Verification Requirements

Control Objective

Authorization is the concept of allowing access to resources only to those permitted to use them. Ensure that a verified application satisfies the following high level requirements:

  • Persons accessing resources holds valid credentials to do so.
  • Users are associated with a well-defined set of roles and privileges.
  • Role and permission metadata is protected from replay or tampering.

Security Verification Requirements

# Description L1 L2 L3 Since
4.1 Verify that the principle of least privilege exists - users should only be able to access functions, data files, URLs, controllers, services, and other resources, for which they possess specific authorization. This implies protection against spoofing and elevation of privilege. 1.0
4.4 Verify that access to sensitive records is protected, such that only authorized objects or data is accessible to each user (for example, protect against users tampering with a parameter to see or alter another user's account). 1.0
4.5 Verify that directory browsing is disabled unless deliberately desired. Additionally, applications should not allow discovery or disclosure of file or directory metadata, such as Thumbs.db, .DS_Store, .git or .svn folders. 1.0
4.8 Verify that access controls fail securely. 1.0
4.9 Verify that the same access control rules implied by the presentation layer are enforced on the server side. 1.0
4.10 Verify that all user and data attributes and policy information used by access controls cannot be manipulated by end users unless specifically authorized. 1.0
4.11 Verify that there is a centralized mechanism (including libraries that call external authorization services) for protecting access to each type of protected resource. 1.0
4.12 Verify that all access control decisions can be logged and all failed decisions are logged. 2.0
4.13 Verify that the application or framework uses strong random anti-CSRF tokens or has another transaction protection mechanism. 2.0
4.14 Verify the system can protect against aggregate or continuous access of secured functions, resources, or data. For example, consider the use of a resource governor to limit the number of edits per hour or to prevent the entire database from being scraped by an individual user. 2.0
4.15 Verify the application has additional authorization (such as step up or adaptive authentication) for lower value systems, and / or segregation of duties for high value applications to enforce anti-fraud controls as per the risk of application and past fraud. 3.0
4.16 Verify that the application correctly enforces context-sensitive authorisation so as to not allow unauthorised manipulation by means of parameter tampering. 3.0


For more information, see also: