Limit Privileged Roles
BSSC Token Integration Standard version 2
Domain: 3. Security Posture |
Level: MUST
Statement of Requirement:
Privileged
Roles MUST be strictly limited to those necessary for proper
performance of the Token
Contract.
See
it in the specification
Purpose
Any unnecessary Privileged
Role is a potential attack vector, and potential cause of
undesired and unexpected behaviour.
Audit procedures
- Verify all Privileged
Roles through source-code analysis, and check that each one
identified is necessary
- Check that Security Audits identified every Privileged
Role
Success Criteria
Best Practice
Failure Criteria
- A Privileged Role is unnecessary.
Common Failures
- Code copied from another source includes Privileged Roles by default
that are unnecessary
- An unnecessary Privileged Role's security is not properly
maintained
Key Evidence