Access control principles
Access to systems and information should be granted according to business need, least privilege and separation of duties where practical. Access should be attributable to an individual or an approved service identity; shared human accounts should be avoided.
Identity lifecycle
- Joiner: verify authorisation, assign a named identity, grant only approved access and communicate acceptable-use requirements.
- Mover: review existing permissions when responsibilities change and remove access no longer required.
- Leaver: revoke interactive access, tokens, keys and sessions promptly in accordance with the approved offboarding process; recover company assets.
Authentication
Multi-factor authentication should be required for privileged access and remote access to sensitive administrative interfaces wherever supported. Strong unique passwords or approved identity-provider authentication should be used. Credentials, API keys and tokens must not be embedded in source code, committed to repositories or shared through unapproved channels.
Privileged and service access
Administrative privileges should be limited to authorised operators, used through separate privileged identities where feasible, and reviewed periodically. Service accounts should have a defined owner, purpose, minimum permissions, controlled credentials and a process for rotation and retirement. Long-lived keys should be avoided when a safer identity mechanism is available.
Access reviews
System owners should review access periodically and after material role changes, incidents or environment changes. Reviews should cover user identities, administrator roles, service accounts, external collaborators and access to production data. Decisions and remediation should be recorded.
Evidence to retain
Examples include approved access requests, identity-provider settings, IAM role exports, privileged-account inventories, access review sign-offs, offboarding records and service-account ownership records. Configuration screenshots or exports should be dated and redacted before customer sharing.
Verification status
Apps Intellect's actual MFA coverage, identity provider, access-review cadence and privileged account inventory have not yet been confirmed for every product and environment. These details will be published only after review.
