Identity and Access Control
How people and build machines sign in to CodeSign Secure, and how their access is limited.
Signing in to the portal
-
Azure AD (Microsoft Entra ID): users sign in with their organization account once an identity store is configured. See Identity Store.
-
Local accounts: a System Admin registers users with an email and password. See User.
-
Sessions: each account can have one active session. Signing in again revokes the account’s earlier sessions.
Roles and permissions
CodeSign Secure has five default roles: System Admin, Project Manager, Security Officer, Auditor, and Developer. Every role other than System Admin starts with no permissions, so a System Admin enables the permissions each role needs. See Roles and Permissions.
Who can sign with which certificate
-
Teams: in App Management, certificates are mapped to teams. Only members of a mapped team can sign with a certificate. See App Management.
-
Approval policies: the environment of a certificate decides whether a signing request needs approval (Certificate Owner, Quorum, or No Approval), and whether approvers must enter an MFA code. See Environment and Designing Signing Policies.
-
Approvers: approvers must hold the System Admin or Project Manager role.
Build machines and scripts
Build machines authenticate with an authentication certificate and API user credentials, and API scripts send a short-lived Bearer token. See Client Authentication and Authorizing Requests.
Reviewing access
The Audit Trail records crypto operations, application operations, user management, and system settings changes, and Logs keep the full system log. Review users and role assignments regularly; see the Security Hardening Checklist.
