Identity and Access Mgmt

Cybersecurity area

Identity and Access Mgmt

Identity and Access Mgmt manages, verifies, and audits digital identities and access for users, administrators, services, applications, and cloud roles.

Thematic hero image for the Identity and Access Mgmt area

Acronym Glossary

This glossary explains acronyms used in this part so the intended security function is clear.

IAM
Identity and Access ManagementManagement of digital identities, authentication, authorization, and access policies.
MFA
Multi-Factor AuthenticationUser verification with multiple factors such as password plus app, token, or biometric factor.
PAM
Privileged Access ManagementControl and protection of privileged accounts, administrator access, and sensitive operations.
PIM
Privileged Identity ManagementManagement of privileged identities, entitlements, roles, and temporary access to sensitive systems.
IGA
Identity Governance and AdministrationGovernance of identities, roles, entitlements, recertifications, and auditable access lifecycle.
SSO
Single Sign-OnA sign-on model that allows users to access multiple applications through one controlled identity point.
SCIM
System for Cross-domain Identity ManagementA standard for automated provisioning, updating, and deprovisioning of user accounts in applications.
RBAC
Role-Based Access ControlAccess control based on roles where permissions follow the user's job function or responsibility.
ABAC
Attribute-Based Access ControlDynamic access decisions based on attributes of the identity, device, resource, environment, and requested action.
PBAC
Policy-Based Access ControlAccess control through central policies combining identity, resource, action, conditions, and approval.
ReBAC
Relationship-Based Access ControlAccess control based on the identity's relationship to a specific object, team, owner, or managed service.
JIT
Just-in-Time AccessTemporary access granted only when justified and automatically removed after the task or approved time window ends.
JEA
Just Enough AdministrationDelegation of only the necessary administrative tasks, commands, and targets without granting full privileges.

What This Area Covers

Identity and Access Mgmt defines who or what can access systems, applications, data, and administrative functions. Identity today is not only a username in a directory. It includes employees, contractors, administrators, service accounts, cloud roles, API access, devices, and application identities.

Why It Matters

Because many attacks begin with a compromised identity or abused privilege, IAM is one of the most important areas of security architecture. MFA reduces password misuse risk, SSO centralizes access, PAM protects privileged accounts, PIM reduces standing administrative privileges, and IGA governs access and certifications. RBAC, ABAC, PBAC, and ReBAC define the basis for authorization, while JIT and JEA limit its duration and scope.

How To Navigate This Area

Identity is now a primary security control point. When choosing technologies, it is necessary to separate authentication, authorization, identity lifecycle, governance, privileged access, privileged identities, technical secrets, and integrations with directories, SaaS applications, and cloud platforms. Authorization may be based on roles, attributes, policies, or relationships and should be reinforced by least privilege, just-in-time, and just-enough access. Phishing-resistant MFA, IGA, and continuous access risk evaluation are also increasingly important.

IAM solutions should be selected by separating authentication, authorization, governance, privileged identities, technical secrets, and lifecycle management. An organization may have strong MFA but weak access removal processes or overly broad roles. RBAC alone may be insufficient in dynamic environments where context, attributes, or a relationship to the protected object matters. Privileged access should combine policies, approvals, JIT, JEA, session audit, and reliable removal of elevated privileges.

The technology list below works as a map of the Identity and Access Mgmt area. The practical sequence is to name the security problem first, select the closest technology category second, and only then compare relevant vendors. This helps separate similar-sounding solutions and reduces the risk of adding another tool without a clear architectural role.

Technical Section Schema

Technical schema for the Identity and Access Mgmt area
The schema shows the main inputs, security layers, and outputs of the Identity and Access Mgmt area.

Questions To Ask When Selecting A Solution

  • Which identities are the riskiest: regular users, administrators, contractors, or service accounts?
  • Is the problem authentication, permission assignment, recertification, or access removal?
  • Does the environment require integration with HR, AD, Entra ID, SaaS apps, or cloud roles?
  • Are critical accesses protected with phishing-resistant MFA or only by passwords and push approval?
  • Are privileged accounts, cloud roles, and technical secrets managed separately and auditably?

How To Use This Section

Each technology page expands one category, explains its architectural role, and lists SecTec portfolio vendors related to that area. The section page is therefore the orientation layer, while the detail pages support concrete mapping to solutions.

Vendors From The SecTec Portfolio

Attack coverage and defensive context

MITRE ATT&CK® Enterprise version 19.1 is used as a reference model. The mapping is a SecTec expert interpretation and does not imply endorsement by MITRE.

Practical attack scenarios

Relevant ATT&CK techniques