Skip to main content

PAM Gap Analysis

The PAM Gap Analysis module assesses the maturity of your Privileged Access Management programme against industry frameworks. It walks you through a structured questionnaire and produces a findings report — showing which controls are compliant, partially implemented, or have gaps — together with a signed PDF export suitable for auditors or management review.

Requires Pro or Enterprise edition — not available on Community.

Gap Analysis

Supported Frameworks​

Each assessment evaluates your PAM posture against the following frameworks simultaneously:

FrameworkDescription
NIST SP 800-53 Rev 5US federal controls for access management and audit
NIST SP 800-63BDigital identity guidelines focusing on authentication assurance
ISO/IEC 27001:2022International information security management standard
BS EN ISO/IEC 29146:2026Access management framework covering privileged access controls, entitlement lifecycle, role management, and access governance
ISO/IEC 24760Identity management framework covering identity lifecycle, proofing, non-human identities, and governance
SOx IT General ControlsSarbanes-Oxley ITGC requirements for financial systems (in-scope assessments only)
GxP (21 CFR 11 / EU Annex 11)Regulatory requirements for life sciences and pharmaceutical environments (in-scope assessments only)
Cyber EssentialsUK NCSC-backed baseline certification, scoped to the privileged-access dimension of its five technical themes (in-scope assessments only)
HIPAAUS Security Rule technical and administrative safeguards for systems handling electronic protected health information (in-scope assessments only)
SOC 2The CC6 logical access criteria of the AICPA Trust Services Criteria, Security category, as a readiness view (in-scope assessments only)
PCI DSSPCI DSS v4.0 Requirements 7 and 8: restricting access by need to know, identifying users and authenticating access (in-scope assessments only)
NIS2The access control and privileged access measures of the EU NIS2 Directive, Article 21(2) (in-scope assessments only)
DORAThe ICT access management and privileged access requirements of the EU Digital Operational Resilience Act and its ICT risk management technical standards (in-scope assessments only)

SOx, GxP, Cyber Essentials, HIPAA, DORA, NIS2, PCI DSS, and SOC 2 controls are included only when you indicate those areas are in scope during the questionnaire. All other frameworks are evaluated for every assessment.

note

Cyber Essentials Plus is not supported. Cyber Essentials Plus certification requires independent technical verification (an external vulnerability scan and an internal authenticated sample test) carried out by a certifying body — evidence a self-assessment questionnaire tool cannot itself produce. Only the self-assessed Cyber Essentials framework is offered.

Assessment Lifecycle​

DRAFT → IN_PROGRESS → COMPLETE
StatusDescription
DRAFTAssessment created but the questionnaire has not been started
IN_PROGRESSQuestionnaire is being completed; responses can still be edited
COMPLETEAssessment has been finalised; responses and findings are locked

Once an assessment is marked Complete it cannot be modified. A PDF export can be downloaded at any time after completion.

Creating an Assessment​

  1. Navigate to Reports > PAM Gap Analysis
  2. Click New Assessment
  3. Fill in the details:
FieldRequiredDescription
TitleYesA name for this assessment (e.g., "Q1 2026 PAM Maturity Review")
DescriptionNoAdditional context or scope notes
  1. Click Create

The new assessment opens directly in the questionnaire wizard.

note

When you create a new assessment, OrbisID pre-populates the questionnaire with responses from the most recently completed assessment. This saves time on repeat assessments and lets you focus on what has changed.

Completing the Questionnaire​

The questionnaire is divided into sections presented as a wizard. Navigate between sections using the step bar at the top of the page, or use Back and Next.

Sections​

SectionDescription
1. Scope & ContextOrganisation size, industry, and which frameworks apply — this is where you toggle SOx, GxP, Cyber Essentials, HIPAA, DORA, NIS2, PCI DSS, and SOC 2 in or out of scope
2. PAM ToolingWhether a PAM tool is in use, which product, deployment maturity, and — if Cyber Essentials is in scope — patch cadence, unsupported software, and malware protection for your privileged access infrastructure (PAM vault/gateway, jump hosts, privileged access workstations)
3. Technology Stack SelectionWhich technology areas are in scope for this assessment
3a–3g. Stack sub-sectionsPer-stack questions for AD, Windows, Linux, Network, Databases, Cloud, and Other (shown only for selected stacks)
4. Access GovernanceLifecycle management, access reviews, separation of duties, role management approach, privileged access elevation process, and — when in scope — SOx ITGC, GxP, Cyber Essentials, and HIPAA governance questions
5. Identity ManagementIdentity proofing, non-human identity lifecycle, identity ownership, federated identity, identity reconciliation, and — if HIPAA is in scope — unique user identification
6. AuthenticationMFA, password policies, credential strength, and — if Cyber Essentials is in scope — firewall/gateway administrative access hygiene
7. Session ManagementSession recording, monitoring, and just-in-time access
8. Audit & MonitoringLogging, alerting, SIEM integration, and — when in scope — GxP audit trail and HIPAA transmission-security/incident-response questions
note

SOx, GxP, Cyber Essentials, HIPAA, DORA, NIS2, PCI DSS, and SOC 2 do not have their own wizard step. Once you mark a framework in scope in Scope & Context, its questions appear inline within whichever section above they naturally belong to, so the questionnaire reads as one continuous flow rather than a separate checklist per framework toggle. Findings and scores are still reported completely separately per framework in the Findings tab and PDF export — only the questionnaire's grouping works this way.

note

The Identity Management section (step 5) was added to support the BS EN ISO/IEC 29146:2026 and ISO/IEC 24760 frameworks. If you have existing assessments, these questions will be blank and the corresponding controls will be evaluated on available OrbisID product data alone until you complete a new assessment.

Question Types​

TypeHow to Answer
Yes / NoClick the Yes or No button
SelectChoose one option from the dropdown
Multi-selectChoose all applicable options
TextFree-text response

Some questions are conditional and only appear based on earlier answers (for example, stack-specific questions only appear for stacks you selected).

Saving Progress​

Click Save Responses at the bottom of each section to save your current answers. Responses are saved per-section. You can return to any section at any time while the assessment is IN_PROGRESS.

Completing the Assessment​

When all sections are answered to your satisfaction:

  1. Navigate to the final section
  2. Click Complete Assessment
  3. Confirm the prompt

OrbisID processes all responses, evaluates each framework control, and generates the findings. The assessment status changes to COMPLETE and the questionnaire becomes read-only.

note

Completing an assessment is irreversible. Ensure all responses are accurate before proceeding.

Delegating Sections to Subject Matter Experts​

Requires Enterprise edition.

If parts of the questionnaire cover technology areas managed by other teams, you can delegate those sections to external contributors without giving them an OrbisID login.

  1. Open an IN_PROGRESS assessment
  2. Click Delegate
  3. Fill in the delegation details:
FieldRequiredDescription
Technology AreaNoFree-text label for the area being delegated (e.g., "Network Infrastructure")
Stack(s)NoSpecific stacks this delegation covers (for reference only)
Recipient EmailNoEmail address to send the link to
DescriptionNoInstructions or context for the recipient
Link ExpiryYesHow many days the link remains valid (default: 14)
  1. Click Create Delegation

A unique link is generated. If you supplied an email address, OrbisID sends the link automatically. You can also copy the link and share it manually.

What the Recipient Sees​

The recipient opens the link in any browser — no account required. They see a standalone questionnaire page showing only the questions relevant to their delegation. At the bottom of the page they must:

  1. Enter their full name
  2. Tick the acknowledgment checkbox confirming their responses are accurate
  3. Click Submit & Sign

Submission is a one-time action. Once submitted, the link is consumed and responses are stored against the assessment.

Managing Delegations​

The delegations panel on the assessment page shows all tokens created for the assessment:

ColumnDescription
EmailRecipient email (if provided)
Technology AreaLabel given at creation
CreatedDate the token was created
ExpiresDate the link expires
StatusPending, Submitted, or Expired
SignatoryName entered by the recipient on submission

You can:

  • Copy link — copy the URL to share manually
  • Edit email — update the recipient address and resend
  • Resend — send the link again to the current email address

Findings​

After an assessment is completed, navigate to Findings (the default view) to see the control-by-control evaluation.

Framework Summary​

At the top of the findings page, each framework shows:

ElementDescription
CompliantControls fully satisfied
PartialControls partially satisfied
GapControls with identified gaps
N/AControls not applicable to this assessment
ScoreOverall compliance percentage for the framework

Finding Detail​

Each row in the findings table represents a single framework control:

ColumnDescription
Control IDFramework reference (e.g., AC-2, A.9.2.3)
Control NameShort name of the control
StatusCompliant, Partial, Gap, or Not Applicable
RiskCritical, High, Medium, Low, or Informational
Evidence / Gap / RecommendationDetail of what was found and what action is needed

Controls are grouped by framework. Click a framework panel header to collapse or expand it.

Overriding a Finding​

If a finding does not accurately reflect your environment, an administrator can override it:

  1. Click the override icon on a finding row
  2. Select the corrected status
  3. Enter a justification
  4. Click Save Override

Overrides are recorded with the justification and are visible in the PDF export.

Responses​

Click Responses to see a read-only view of all questionnaire answers, grouped by section.

This view shows:

  • Assessor responses — answers entered directly in OrbisID
  • Delegatee responses — one panel per submitted delegation, showing the signatory name, submission date, and their answers

Downloading the PDF Report​

Click Download PDF to generate a full assessment report. The PDF includes:

SectionContent
Cover pageAssessment title, date, licensed organisation, and edition
Executive SummaryOverall maturity score (CMMI level), framework scores, and key risk indicators
AI-Generated Risk SummaryShort plain-English narrative of the findings, generated when the assessment completes (see AI Assistant) — omitted entirely if the feature is off
Framework FindingsControl-by-control results for each applicable framework
Risk SummaryFindings grouped by risk level
Remediation RoadmapPrioritised list of recommended actions
Appendix A — MethodologyExplanation of the scoring approach
Appendix B.1 — Assessor ResponsesFull questionnaire Q&A from the primary assessor
Appendix B.2+ — Delegatee ResponsesOne appendix section per submitted delegation, including signatory name and submission date

The PDF is generated on demand and reflects the assessment state at the time of download. If the AI Risk Narrative is enabled, a Regenerate button on the assessment page refreshes the cached narrative before your next download — it does not rewrite PDFs you've already exported.

Threat Detections and Gap Analysis​

If you have deployed Endpoint Sensors, OrbisID automatically incorporates your Threat Detection activity as evidence when evaluating monitoring controls. No extra configuration is required. Sensors are optional: where a monitoring control is not met, the recommendation is to connect an identity threat product (Microsoft Defender for Identity or CrowdStrike, under Identity Alerts) and, if you have none, to deploy Endpoint Sensors.

How it works​

When you complete an assessment, OrbisID takes a snapshot of your current Threat Detection state:

Data pointUsed for
Active Endpoint Sensors (online count)Evidence that real-time Windows endpoint monitoring is in place
Connected identity alert sources (count)A Defender for Identity or CrowdStrike source that is turned on and has fetched alerts successfully within the last 7 days. Counts as real-time alerting evidence in the same controls as Endpoint Sensors (AU-2, A.8.15, 29146-8.1, ITGC-OP-1, HIPAA audit controls and incident procedures, DORA-10(1), NIS2-21(2)(b)). It is not evidence that anyone reviewed an alert: that still needs confirmed Threat Detections or your questionnaire answers
Open Threat DetectionsShows the engine is actively generating detections
Confirmed Threat DetectionsAnalyst review evidence — demonstrates detections are being triaged

This data is factored into the following controls:

ControlFrameworkEffect
AU-2 Event Logging — Audit EventsNIST 800-53Active sensors + SIEM = Compliant. Active sensors without SIEM = Partial (with recommendation to forward via CEF syslog)
AC-6(9) Log Use of Privileged FunctionsNIST 800-53Active sensors count as partial logging coverage for Windows endpoints
A.8.15 LoggingISO/IEC 27001Active sensors count toward the alerting dimension
29146-8.1 Access Event MonitoringBS EN ISO/IEC 29146:2026Active sensors count as real-time alerting evidence. Active sensors + SIEM = Compliant
ITGC-OP-1 Monitoring of Privileged ActivitySOx ITGCActive sensors + confirmed detections = Compliant. Active sensors without SIEM = Partial (SOx requires 7-year log retention via a SIEM)
HIPAA-164.312(b) Audit ControlsHIPAAActive sensors count toward the real-time alerting requirement alongside SIEM integration and immutable logs
HIPAA-164.308(a)(6) Security Incident ProceduresHIPAAConfirmed Threat Detections demonstrate active incident triage; active sensors alone provide partial credit

Answering "No" to monitoring questions​

If you answer No to "Is there real-time alerting configured for anomalous privileged activity?" or "Are privileged access events forwarded to a SIEM?", the recommendation for affected controls will include guidance on how OrbisID Endpoint Sensors can help close the gap — including using the built-in CEF syslog integration to forward detections to a SIEM.

Building SOx evidence with Threat Detections​

For SOx in-scope assessments, the ITGC-OP-1 control requires evidence that privileged activity is both monitored and reviewed. To satisfy both:

  1. Deploy at least one Endpoint Sensor (provides the monitoring evidence; optional if your monitoring evidence comes from a SIEM or identity threat product that you describe in the questionnaire)
  2. Confirm at least one genuine Threat Detection in the Threat Detections page (provides the analyst-review evidence)
  3. Enable CEF syslog forwarding to a SIEM for log retention (Administration → Settings)

BS EN ISO/IEC 29146:2026 — Access Management Framework​

BS EN ISO/IEC 29146:2026 is the British Standard adoption of the international access management framework. It focuses specifically on how organisations govern, control, and monitor access rights — making it a natural fit for PAM programmes.

Controls Evaluated​

Control IDControl NameKey Evidence Sources
29146-5.2Access Management PolicyFormal Access Management Policy documented; formal definition of privileged access in place
29146-6.1Entitlement Lifecycle ManagementJML process covering privileged access; inactive identity remediation SLA; OrbisID detected inactive identities with active accounts
29146-6.2Privileged Access ControlsPAM tool deployed; JIT/JEA in use; privileged elevation process (PAM-managed preferred); PAM coverage percentage from OrbisID
29146-6.3Access CertificationReview frequency; risk-based stratification (high-risk accounts certified more frequently)
29146-7.1Separation of DutiesSoD enforced at system access level
29146-7.2Role and Entitlement ManagementRole management approach (formal RBAC or entitlement catalogue); formal change management for access changes
29146-7.3Emergency Access ManagementDocumented and tested break-glass procedure
29146-8.1Access Event MonitoringSIEM integration; real-time alerting; OrbisID Endpoint Sensors count as alerting evidence

Key Questions (Section 4 — Access Governance)​

Three questions were added to the Access Governance section specifically to support this framework:

QuestionPurpose
Does your organisation have a formally documented and approved Access Management Policy?Drives 29146-5.2
How are roles and access permissions managed?Drives 29146-7.2 (RBAC Formal, Entitlement Catalogue, etc.)
How is temporary privileged access elevation requested and approved?Drives 29146-6.2 (PAM-managed elevation is the strongest control)

ISO/IEC 24760 — Identity Management Framework​

ISO/IEC 24760 is a multi-part international standard that defines the framework for managing identities throughout their lifecycle — from proofing and provisioning through to de-provisioning and reconciliation. It applies to both human and non-human identities.

Controls Evaluated​

Control IDControl NameKey Evidence Sources
24760-3.1Identity Lifecycle ManagementJML process; identity proofing before provisioning; OrbisID detected inactive identities with active accounts
24760-3.2Identity Proofing and BindingIdentity proofing process in place; account-to-identity linkage percentage from OrbisID
24760-3.3Orphaned Identity DetectionOrphaned account tracking approach; OrbisID unlinked account count
24760-3.4Identity Information QualityNamed identity owners defined; account-to-identity linkage percentage; total identity count from OrbisID
24760-3.5Non-Human Identity ManagementNHI lifecycle management approach; OrbisID non-human account count
24760-4.2Identity GovernanceNamed identity owners defined; Access Management Policy in place
24760-5.1Federated Identity ManagementFederation model (fully/partially/not federated); SSO deployed
24760-5.2Identity ReconciliationIdentity reconciliation frequency across systems

Key Questions (Section 5 — Identity Management)​

A dedicated Identity Management section (step 5 in the wizard) was added for this framework:

QuestionPurpose
Is there a formal identity proofing process before accounts are provisioned?Drives 24760-3.1 and 24760-3.2
How are non-human identity lifecycles managed?Drives 24760-3.5 (automated lifecycle is highest maturity)
Is a named owner formally defined for every identity?Drives 24760-3.4 and 24760-4.2
Does the organisation use federated identity management?Drives 24760-5.1
How frequently is identity data reconciled across systems?Drives 24760-5.2

OrbisID Data Used​

Both frameworks make extensive use of live OrbisID metrics captured at assessment completion:

MetricControls
Account-to-identity linkage %24760-3.2, 24760-3.4
Unlinked (orphaned) account count24760-3.3
Non-human account count24760-3.5
Inactive identities with active accounts24760-3.1, 29146-6.1
PAM-managed account %29146-6.2

Cyber Essentials​

Cyber Essentials is the UK NCSC-backed baseline cyber security certification, covering firewalls, secure configuration, security update management, user access control, and malware protection. Because OrbisID is a PAM-focused product, each theme is scoped specifically to the privileged-access dimension rather than general estate-wide security hygiene — for example, patch management is assessed for your PAM vault/gateway and jump hosts, not your whole server estate.

Controls Evaluated​

Control IDControl NameKey Evidence Sources
CE-1FirewallsAdmin interfaces for boundary firewalls/gateways not exposed to the Internet (or MFA-protected); default credentials changed
CE-2Secure Configuration of Privileged AccountsDefault/unnecessary administrative accounts removed; default credentials changed; OrbisID unclassified-entitlement count
CE-3Security Update Management for Privileged Access InfrastructurePatch cadence for the PAM vault/gateway, jump hosts, and privileged access workstations; unsupported software removed; OrbisID scan failure rate
CE-4User Access ControlAdministrative accounts kept separate from standard-use accounts; PAM tool deployed; MFA coverage; OrbisID standing/shared privileged account counts
CE-5Malware Protection on Privileged Access PathwaysAnti-malware (or allow-listing/sandboxing) deployed on PAM jump servers, bastion hosts, and privileged access workstations

Key Questions​

Cyber Essentials questions are embedded across the PAM Tooling, Access Governance, and Authentication sections, shown only once you mark Cyber Essentials in scope:

QuestionSectionPurpose
Are admin interfaces for firewalls/gateways protected from the Internet?AuthenticationDrives CE-1
Are default credentials changed on firewalls, network devices, and privileged accounts?AuthenticationDrives CE-1, CE-2
Are default/unnecessary privileged accounts removed?Access GovernanceDrives CE-2
Are administrative accounts kept separate from standard accounts?Access GovernanceDrives CE-4
How quickly are patches applied to your privileged access infrastructure?PAM ToolingDrives CE-3
Is unsupported software removed from your privileged access infrastructure?PAM ToolingDrives CE-3
Is malware protection deployed on PAM jump servers/privileged access workstations?PAM ToolingDrives CE-5

HIPAA​

HIPAA controls map to the Security Rule's technical safeguards (§164.312) and administrative safeguards (§164.308) as they relate to privileged access to systems handling electronic protected health information (ePHI).

Controls Evaluated​

Control IDControl NameKey Evidence Sources
HIPAA-164.312(a)(2)(i)Unique User IdentificationUnique user IDs confirmed for ePHI system access; OrbisID shared privileged account count
HIPAA-164.312(a)(2)(iii)Automatic LogoffSession timeout / automatic logoff policy enforcement
HIPAA-164.312(a)(2)(iv)/(e)(1)Encryption and Decryption / Transmission SecurityEncryption at rest; encryption in transit for privileged/administrative access
HIPAA-164.312(b)Audit ControlsSIEM integration; immutable audit logs; real-time alerting; OrbisID Endpoint Sensors count as alerting evidence
HIPAA-164.312(d)Person or Entity AuthenticationMFA coverage for privileged access to ePHI systems
HIPAA-164.308(a)(4)Information Access Management — Minimum NecessaryMinimum-necessary access provisioning standard; OrbisID standing privileges count
HIPAA-164.308(a)(3)Workforce Security — Termination ProceduresInactive-identity remediation process and SLA; OrbisID inactive-identity-with-active-account count
HIPAA-164.308(b)Business Associate ContractsBusiness Associate Agreements tracked for third parties with privileged access
HIPAA-164.308(a)(6)Security Incident ProceduresDocumented breach-notification procedure; OrbisID Threat Detection activity as evidence of active triage

Key Questions​

Embedded across Identity Management, Access Governance, and Audit & Monitoring, shown only once HIPAA is marked in scope:

QuestionSectionPurpose
Does every workforce member use a unique user identifier, with no shared or generic logins?Identity ManagementDrives HIPAA-164.312(a)(2)(i)
Is access provisioned on a minimum-necessary basis?Access GovernanceDrives HIPAA-164.308(a)(4)
Are Business Associate Agreements tracked for third parties with privileged access?Access GovernanceDrives HIPAA-164.308(b)
Is ePHI encrypted in transit for privileged/administrative sessions?Audit & MonitoringDrives HIPAA-164.312(a)(2)(iv)/(e)(1)
Is there a documented security incident/breach notification procedure?Audit & MonitoringDrives HIPAA-164.308(a)(6)

DORA​

The Digital Operational Resilience Act (Regulation (EU) 2022/2554) applies to EU financial entities and to the ICT third-party providers that serve them. DORA controls here cover only its ICT access management and privileged access requirements, taken from the Act and from its ICT risk management technical standards (Commission Delegated Regulation (EU) 2024/1774, "RTS"). They do not assess DORA as a whole, and they are included only when you mark DORA in scope.

ControlRequirementWhat is assessed
DORA-9(4)(c)Art. 9(4)(c) — Access limited to legitimate, approved functionsDocumented access control policy (need-to-know, least privilege); OrbisID standing privileges and privileged accounts without an owner
DORA-9(4)(d)Art. 9(4)(d) — Strong authenticationMFA coverage for privileged access
DORA-RTS-20RTS Art. 20 — Identity managementAccounts linked to an identity; shared privileged accounts; a documented identity and account lifecycle
DORA-RTS-21-REVIEWRTS Art. 21 — Access control: account management and access reviewAccess review frequency; OrbisID accounts still active for inactive identities
DORA-RTS-21-PAMRTS Art. 21 — Access control: privileged access management and dedicated administrator accountsDedicated administrator accounts; share of privileged accounts managed in the PAM tool
DORA-10(1)Art. 10(1) — Detection of anomalous activitiesDetection mechanisms with alert thresholds and responsible staff; real-time alerting, including OrbisID Endpoint Sensors

DORA questionnaire questions​

Embedded across Access Governance, Identity Management and Audit & Monitoring, shown only once DORA is marked in scope. They are answered by the assessor and cannot be delegated:

QuestionSectionDrives
Is there a documented ICT access control policy limiting access to approved functions?Access GovernanceDORA-9(4)(c)
Do administrators use dedicated accounts for administrative tasks?Access GovernanceDORA-RTS-21-PAM
Is there a documented lifecycle process for identities and accounts?Identity ManagementDORA-RTS-20
Are mechanisms in place to detect anomalous activity, with alert thresholds and responsible staff?Audit & MonitoringDORA-10(1)

These controls also appear in Control Monitoring, where the ones backed by KRI data show a live status between assessments.

NIS2​

NIS2 (Directive (EU) 2022/2555) applies to essential and important entities in many sectors, including energy, transport, banking, health, digital infrastructure, ICT service management and public administration. NIS2 controls here cover only the access control and privileged access measures of Article 21(2), and only when you mark NIS2 in scope. They do not assess NIS2 as a whole. Commission Implementing Regulation (EU) 2024/2690, which sets out access control measures in section 11 of its Annex for the digital infrastructure and ICT service management entities it applies to, is used as the reference for what the expected measures look like.

ControlRequirementWhat is assessed
NIS2-21(2)(i)-POLICYArt. 21(2)(i) — Access control policyDocumented access control policy; OrbisID standing privileges and privileged accounts without an owner
NIS2-21(2)(i)-RIGHTSArt. 21(2)(i) — Management of access rightsAccess review frequency; process for removing accounts of people who have left; OrbisID accounts still active for inactive identities
NIS2-21(2)(i)-PRIVArt. 21(2)(i) — Privileged and system administration accountsAdministrator accounts kept separate and used only for administration; shared privileged accounts; share of privileged accounts managed in the PAM tool
NIS2-21(2)(i)-IDArt. 21(2)(i) — Identification of users and accountsAccounts linked to an identity; shared privileged accounts
NIS2-21(2)(j)Art. 21(2)(j) — Multi-factor or continuous authenticationMFA coverage for privileged access
NIS2-21(2)(b)Art. 21(2)(b) — Incident handlingIncident handling process for privileged account misuse; real-time alerting, including OrbisID Endpoint Sensors

NIS2 questionnaire questions​

Embedded across Access Governance and Audit & Monitoring, shown only once NIS2 is marked in scope. They are answered by the assessor and cannot be delegated:

QuestionSectionDrives
Is there a documented access control policy?Access GovernanceNIS2-21(2)(i)-POLICY
Are privileged and system administration accounts restricted to administration and kept separate from day-to-day accounts?Access GovernanceNIS2-21(2)(i)-PRIV
Is there an incident handling process covering suspected misuse of privileged accounts?Audit & MonitoringNIS2-21(2)(b)

The controls that a KRI can measure also appear in Control Monitoring, with a live status between assessments.

PCI DSS​

PCI DSS v4.0 applies to entities that store, process or transmit payment card account data, or that can affect the security of the cardholder data environment. PCI DSS controls here cover only Requirement 7 (restrict access to system components and cardholder data by business need to know) and Requirement 8 (identify users and authenticate access), including 8.6 for application and system accounts, and only when you mark PCI DSS in scope. They do not assess PCI DSS as a whole. Settings OrbisID cannot see, such as password length, lockout and idle session timeout, are not assessed.

ControlRequirementWhat is assessed
PCI-7.2.27.2.2 — Access assigned by job function, least privilegeAccess model by job function with approval; OrbisID standing privileges and privileged accounts without an owner
PCI-7.2.47.2.4 — Review of user accounts and access privileges at least every six monthsPrivileged access review frequency
PCI-7.2.57.2.5 — Application and system account privilegesApplication and system accounts assigned least privilege and reviewed; non-human accounts OrbisID has discovered
PCI-7.37.3 — Access control system enforcing permissions, default denyAccess control system covering all system components with a default "deny all"; PAM tool deployed
PCI-8.2.18.2.1 — Unique ID for every userAccounts linked to an identity
PCI-8.2.28.2.2 — Group, shared and generic accounts only by exceptionShared privileged accounts OrbisID has found; exception process
PCI-8.2.58.2.5 and 8.2.6 — Terminated and inactive usersAccounts still active for people who have left; dormant privileged accounts; removal process
PCI-8.3.98.3.9 — Password change every 90 days where passwords are the only factorPrivileged accounts with old passwords; MFA coverage
PCI-8.48.4 — Multi-factor authenticationMFA coverage for privileged and remote access
PCI-8.68.6 — Application and system account credentialsCredential protection for application and system accounts; share of privileged accounts managed in the PAM tool

PCI DSS questionnaire questions​

Embedded across Access Governance and Identity Management, shown only once PCI DSS is marked in scope. They are answered by the assessor and cannot be delegated:

QuestionSectionDrives
Is access assigned by job function, at least privilege, and approved?Access GovernancePCI-7.2.2
Are application and system accounts assigned least privilege and reviewed periodically?Access GovernancePCI-7.2.5
Is access managed by an access control system with a default "deny all"?Access GovernancePCI-7.3
Are application and system account credentials protected?Access GovernancePCI-8.6
Are shared or generic accounts used only by exception?Identity ManagementPCI-8.2.2

The controls that a KRI can measure also appear in Control Monitoring, with a live status between assessments. The 90-day password and inactivity checks use the default threshold of the Stale Passwords and Dormant Privileged Accounts KRIs; if you change those thresholds, the evidence changes with them.

SOC 2​

SOC 2 reports are issued by a licensed CPA firm on a service organisation's controls against the AICPA Trust Services Criteria. SOC 2 controls here are a readiness view, not an examination. They cover only the logical access criteria of the Security category, CC6, and only when you mark SOC 2 in scope. The criteria for physical access (CC6.4), disposal (CC6.5), transmission (CC6.7) and malicious software (CC6.8) are not assessed.

ControlCriterionWhat is assessed
SOC2-CC6.1CC6.1 — Logical access security: identification and authenticationAccounts linked to an identity; shared privileged accounts; MFA coverage
SOC2-CC6.1-PRIVCC6.1 — Privileged credentials and infrastructure accessPAM tool deployed; share of privileged accounts managed in it; OrbisID privileged accounts with stale passwords
SOC2-CC6.2CC6.2 — Registration, authorisation and removal of usersUsers authorised before access is granted; accounts still active for people who have left; removal process
SOC2-CC6.3CC6.3 — Role-based access, least privilege and segregation of dutiesRole-based access; segregation of duties; OrbisID standing privileges; access review frequency
SOC2-CC6.6CC6.6 — Protection against threats from outside the system boundariesRemote administrative access through controlled, authenticated and logged pathways; MFA coverage

SOC 2 questionnaire questions​

Embedded in Access Governance, shown only once SOC 2 is marked in scope. They are answered by the assessor and cannot be delegated:

QuestionSectionDrives
Are users registered and authorised before access is granted, and credentials removed when access ends?Access GovernanceSOC2-CC6.2
Is access based on roles and responsibilities with least privilege?Access GovernanceSOC2-CC6.3
Is remote administrative access restricted to controlled, authenticated and logged pathways?Access GovernanceSOC2-CC6.6

The controls that a KRI can measure also appear in Control Monitoring, with a live status between assessments. SOC2-CC6.6 is attested, because no KRI measures remote access.

Assessment List​

Navigate to Reports > PAM Gap Analysis to see all assessments.

ColumnDescription
TitleAssessment name
StatusDRAFT, IN_PROGRESS, or COMPLETE
FrameworksWhich frameworks were evaluated, including SOx, GxP, Cyber Essentials, HIPAA, DORA, NIS2, PCI DSS, and SOC 2 when in scope
CMMI LevelMaturity level (1–5) calculated at completion
CreatedDate the assessment was created
CompletedDate the assessment was finalised

Click an assessment row to open it.

Deleting an Assessment​

  1. Click the delete icon on an assessment row
  2. Confirm the prompt

Deletion is permanent and removes all responses and findings. It is recorded in the Audit Log.