Strong Authentication

[ALL Actors - AICM - CSP]
1. Authentication Management: 
i. A centralized authentication system that can manage identities, authentication credentials, and access control permissions across all AI service components should be implemented 
ii. Users that require privileged access (e.g.,administrators and IT staff) should be identified to establish stricter authentication measures 
iii. Specific authentication factors and technical measures should be defined and implemented for each access level, including MF A for privileged identities and sensitive data access 

2. MFA Usage Scope: 
i. Sensitive Data Access: Strong authentication should be enforced at all user accounts, requiring a combination of something the user: Knows (such as a password); Has (such as a mobile device or token); Is (such as biometrics); MFA for all users should be enabled, including non-privileged users who access sensitive data. 
ii. Administrative Access: MFA should be enforced for all administrative access (e.g., access to management consoles, AI lifecycle components, and other critical AI infrastructure elements). If MFA cannot be implemented in a particular situation, the risk should be formally registered 
iii. Third-Party Access: MFA should be enforced for third-party access, such as through APIs or AI services, to protect against unauthorized access by external entities.

3. Second Factor Authentication: Second factor authentication should be leveraged in addition to passwords to add an extra layer of security by requiring a second factor of: 
i. Time-Based One-Time Passwords (TOTPs) to allow users to generate temporary codes via email or a smartphone app synchronized with an authentication server. 
ii. Hardware tokens or USB keys that generate unique codes for authentication. 

4. Passwordless Authentication: Passwordless authentication solutions should be implemented that replace traditional passwords with secure alternatives such as phishing-resistant MFA and FIDO2-compliant security keys or biometrics. 

5. Authentication Credentials Protection: All authentication credentials should be transmitted through secure channels (e.g., TLS/HTTPS) and never stored in plaintext but rendered unreadable in storage on all system components using strong cryptography. 

6. Authentication Credentials Change Approval: Requests to change or modify authentication credentials (i.e., performing password resets, provisioning new tokens, generating new keys) should be approved only after verification of the user’s identity. 

7. Continuous User Authentication (CUA): CUA should be leveraged as a method of maintaining user authentication throughout their session, requiring periodic reauthentication to ensure that the user is still authorized and has not been compromised. 

8. Single Sign-On (SSO): SSO should be implemented for accessing multiple services and applications with a single login credential to simplify the authentication process for users. 

9. Digital Certificates: Digital certificates should be utilized for authentication and authorization purposes, especially for system identities. 

10. CRL and OCSP Checks: Certificate Revocation Lists (CRLs) and Online Certificate Status Protocol (OCSP) checks should be implemented to verify the validity and revocation status of digital certificates. 

11. Certificate Lifecycle: The lifecycle of digital certificates should be securely managed including issuance, renewal, and revocation. 

12. Certificate Storage: Digital certificates should be stored securely, using encryption and access control mechanisms. 

13. Authentication Usage Monitoring: 
i. All authentication mechanisms and enabled features should be properly installed, configured, and authentication logs monitored for the desired and expected results. 
ii. MFA, credentials, and digital certificate usage patterns should be continuously monitored and reviewed to proactively identify potential vulnerabilities or compromises. 

[All Actors]
1. Implement risk-based authentication controls that evaluate host and user risk (examples: IP reputation and requesting device posture).

2. Enforce the use of phish-resistant MFA (Hardware Key, Certificate Based) for high-risk systems where possible.

3. Provide self-service MFA enrollment for AI service users, supporting FIDO2 security keys, TOTP apps, biometrics, and more.

[OSP & AP]
1. Support secure machine and Agent-Based system authentication such as certificate and token based.

2. Support integration of AIC federated authentication methods (OIDC/OAuth).

3. Disable the usage of insecure protocols and methods by default.

1. Verify cloud console and management APIs enforce MFA and hardware-backed credentials.

2. Confirm authentication enforcement across all IAM roles with model/data access privileges.

3. Ensure that service-to-service authentication (e.g., between AI pipeline components) uses workload identity federation or OIDC tokens.

4. Validate logging of all authentication events and support for anomaly-based detection.

5. Confirm alignment of authentication mechanisms with regulatory compliance standards (e.g., NIST SP 800-63B).

From CCM:
1. Determine if processes, procedures, and technical measures for authenticating access to systems, applications and sensitive data are defined and maintained.
2. Determine if processes, procedures, and technical measures for authenticating access to systems, applications and sensitive data include organization-defined requirements for specific use cases of multifactor authentication, digital certificates and/or alternative security measures.
3. Determine if processes, procedures, and technical measures for authenticating access to systems, applications and sensitive data are implemented and consistently followed in practice.