Main menu

Help your organization meet its ISO/IEC 27001 objectives

Centralize credentials, apply least privilege, and record privileged activity to support the access control requirements of ISO/IEC 27001.

Devolutions is ISO/IEC 27001:2022 certified

Certified continuously since 2021 · independently audited

Certificate
19720
Issued by
NQA, USA · ANAB accredited
Certified since
Valid until

Download the certificate (PDF). Also available in the Trust Center. Our certification covers our own ISMS — it does not certify your organization, and no product can.

What ISO/IEC 27001:2022 requires, and what this mapping covers

ISO/IEC 27001:2022 is the international standard for information security management systems. Clauses 4 to 10 set the mandatory ISMS requirements. Annex A adds a catalogue of 93 reference controls across four themes — 37 organizational, 8 people, 14 physical, 34 technological — which you select from your own risk assessment and justify in your Statement of Applicability.

Each card below names an Annex A control, states in plain language what the control asks for, describes the Devolutions capability that supports it, and lists the evidence you can hand an auditor. Use the search box to jump straight to a control number you are working on.

No software can make your organization ISO 27001 certified. Certification is awarded to an organization's management system, never to a product, so no software can make you ISO 27001 compliant. Roughly a third of Annex A — physical site security, HR screening, disciplinary process, supplier contracting, management review — sits outside what any access platform can touch. What tooling does is make a control operate consistently and produce its own evidence.

5.3

Segregation of Duties

Role segregationRBAC

“Conflicting duties and areas of responsibility must be separated.”

How Devolutions Helps

Granular role-based access control separates who requests access, who approves it and who administers the vault, so no one can approve their own privileged access.

What you can show your auditor

Permission assignments and approval chains showing distinct identities.

Products

  • Remote Desktop Manager
  • Devolutions PAM
  • Devolutions Server
  • Devolutions Cloud
5.9

Inventory of Information and Other Associated Assets

Inventory of access, identities and sessions

“An inventory of information assets, with identified owners, must be maintained.”

How Devolutions Helps

Every connection, credential, secret and privileged account is a catalogued entry with an assigned owner, so the access layer of your asset inventory stays current instead of drifting into spreadsheets.

What you can show your auditor

Vault and folder inventory exports with owners and modification dates.

Products

  • Devolutions Server
  • Remote Desktop Manager
  • Devolutions Cloud
5.14

Information Transfer

Expiring encrypted secret sharing

“Rules and procedures must govern information transfer inside and outside the organization.”

How Devolutions Helps

Devolutions Send replaces credentials sent over email, chat or ticketing systems with single-use, expiring, encrypted links, so a transferred secret leaves no permanent copy in an unmanaged system.

What you can show your auditor

Transmission logs with recipient, expiry and view status.

Products

  • Devolutions Send
  • Devolutions Server
  • Devolutions Cloud
5.15

Access Control

Logical access controlPAMfine-grained permissions

“Access rules must be established and implemented from business and security requirements.”

How Devolutions Helps

One logical access layer sits in front of remote systems and credentials, with permissions applied per user, group, vault, folder and entry so access follows the rule set rather than local convention.

What you can show your auditor

Permission reports per user and per resource, plus denied-access logs.

Products

  • Devolutions Server
  • Devolutions Cloud
  • Remote Desktop Manager
  • Devolutions PAM
5.16

Identity Management

Active DirectoryEntra IDSCIMSAML SSO

“The full identity lifecycle must be managed, from creation through change to removal.”

How Devolutions Helps

Identities are sourced from your directory rather than maintained separately, so joiner, mover and leaver events propagate into the access layer instead of being re-entered by hand.

What you can show your auditor

Directory synchronization configuration and provisioning and deprovisioning logs.

Products

  • Devolutions Server
  • Devolutions Cloud
5.17

Authentication Information

Encrypted vaultrotationcredential injection

“Allocation and management of authentication information must follow a defined process.”

How Devolutions Helps

Secrets are generated to policy in an AES-256 vault, rotated on schedule or on demand, and injected into sessions without being displayed, so users never need to know a privileged password to use it.

What you can show your auditor

Rotation history, password policy and injection events showing no disclosure.

Products

  • Remote Desktop Manager
  • Devolutions PAM
  • Devolutions Server
  • Devolutions Cloud
5.18

Access Rights

Access lifecycleentitlement reporting

“Access rights must be provisioned, reviewed, modified and removed per policy.”

How Devolutions Helps

Rights are granted by request and approval, time-boxed where appropriate, and revoked automatically on expiry or directory deprovisioning, with entitlement reports giving you the population to review each cycle.

What you can show your auditor

Entitlement reports, access review sign-offs and grant and revocation timestamps.

Products

  • Devolutions Server
  • Devolutions Cloud
  • Devolutions PAM
5.23

Information Security for Use of Cloud Services

Cloud secrets managementsecure tunneling

“Acquiring, using, managing and exiting cloud services must follow defined security requirements.”

How Devolutions Helps

Cloud credentials, API keys and service secrets are held centrally with rotation and scoped access instead of living in individual consoles, and secure tunnelling reaches cloud workloads without exposing management ports.

What you can show your auditor

Cloud secret inventory, rotation logs and tunnel session records.

Products

  • Devolutions Server
  • Devolutions Cloud
  • Remote Desktop Manager
  • Devolutions Gateway
5.24

Information Security Incident Management Planning and Preparation

Audit trailincident readiness

“Incident management processes, roles and responsibilities must be defined in advance.”

How Devolutions Helps

A complete audit trail of access and privileged activity exists before an incident occurs, which is what makes a response plan executable, and break-glass paths can be pre-staged with their use logged.

What you can show your auditor

Audit log and retention configuration plus documented break-glass procedures.

Products

  • Devolutions Server
  • Devolutions Cloud
5.25

Assessment and Decision on Information Security Events

SIEM forwardingsession telemetry

“Events must be assessed and a decision recorded on whether each is an incident.”

How Devolutions Helps

Access and session logs stream to your SIEM carrying the authentication, authorization and session context a triage team needs to decide whether an event is an incident.

What you can show your auditor

SIEM integration configuration and the event records behind triage decisions.

Products

  • Devolutions Server
  • Devolutions Cloud
5.26

Response to Information Security Incidents

Credential rotationsession termination

“Incidents must be responded to according to documented procedures.”

How Devolutions Helps

Containment actions are available directly in the platform: rotate or revoke a compromised credential, terminate a live privileged session, disable an identity's access, each as an auditable operation.

What you can show your auditor

Timestamped rotation, revocation and termination records tied to the incident ticket.

Products

  • Remote Desktop Manager
  • Devolutions PAM
  • Devolutions Server
  • Devolutions Cloud
5.27

Learning From Information Security Incidents

Retained audit historysession replay

“Knowledge from incidents must be used to strengthen controls.”

How Devolutions Helps

Retained audit history and session recordings let a post-incident review reconstruct what was accessed, by whom and in what order, so corrective actions rest on the record rather than recollection.

What you can show your auditor

Historical audit exports and recordings cited in post-incident reports.

Products

  • Devolutions Server
  • Devolutions Cloud
5.28

Collection of Evidence

Session recordingprotected timestamped logs

“Procedures must cover identifying, collecting, acquiring and preserving evidence.”

How Devolutions Helps

Privileged sessions are recorded and audit entries are timestamped and protected against modification by the operators they describe, which is what makes them evidence rather than logs.

What you can show your auditor

Recordings with integrity controls, timestamped trails and defined retention periods.

Products

  • Devolutions Gateway
  • Remote Desktop Manager
  • Devolutions Server
  • Devolutions Cloud

Control titles are the public reference identifiers used in ISO/IEC 27001:2022 Annex A. The requirement summaries and capability descriptions on this page are Devolutions' own and are not a substitute for the normative text of the standard, which is sold by ISO and national standards bodies at iso.org/standard/27001.

ISO 27001 frequently asked questions

ISO/IEC 27001 is the international standard for information security management systems (ISMS), published jointly by ISO and the IEC. The current edition, ISO/IEC 27001:2022, is the third and was published on 25 October 2022. It specifies what an organization must put in place to identify information security risks, decide how to treat them, and keep improving that system over time.

The standard has two parts. Clauses 4 to 10 are the ISMS requirements and are mandatory. Annex A is a catalogue of 93 reference controls across four themes: 37 organizational, 8 people, 14 physical, and 34 technological. You are not required to implement all 93 — you select them from your risk assessment and justify every inclusion and exclusion in your Statement of Applicability.

Organizations pursue certification to satisfy customer and contractual requirements, to shorten security reviews in regulated sales cycles, and because an audited management system surfaces gaps that ad hoc security work misses.

Yes. Devolutions Inc. is certified to ISO/IEC 27001:2022 under certificate number 19720, issued by NQA, USA, an organization accredited by the ANSI National Accreditation Board (ANAB). Devolutions has held ISO 27001 certification continuously since 1 March 2021 and has transitioned to the 2022 edition; the current certificate is valid until 28 February 2027.

The certified scope covers information security for software development and customer support for Devolutions' password and remote connection products and services, per Statement of Applicability V.2.

The certificate is published in the Devolutions Trust Center.

Devolutions is ISO/IEC 27001:2022 certified, which is the stronger statement. Certification is issued by an accredited body and is verifiable from the certificate, whereas compliant is a claim anyone can make about themselves. Our certificate is number 19720, issued by NQA, USA.

It does not make your organization compliant. Certification covers the certified organization's own management system within a stated scope and does not transfer to customers. What it gives you is a supplier whose security management has been independently audited, which is usable evidence for your own supplier assurance work under Annex A 5.19 to 5.22.

No individual product is certified, and no product from any vendor can be. ISO 27001 certifies an organization's information security management system within a defined scope, not software.

The Devolutions certificate scope covers information security for software development and customer support for our password and remote connection products and services, so every product is built and supported under the certified management system. That is a meaningful statement about how the software is produced. It is not a claim that a given product is certified, and you should treat any vendor making that claim with caution.

Devolutions products map to 34 of the 93 ISO/IEC 27001:2022 Annex A controls. Coverage is concentrated where an access and credential platform does real work:

  • Access control and identity — 5.3, 5.9, 5.15, 5.16, 5.17, 5.18, 8.3: segregation of duties, an owned inventory of access assets, role-based access control, directory-sourced identity lifecycle, encrypted credential vaulting and entitlement reporting
  • Privileged access — 8.2: just-in-time check-out against approval workflows, credential injection without disclosure, and brokered recorded sessions
  • Authentication and cryptography — 8.5, 8.24: FIDO2, TOTP and push MFA, vaulted keys and certificates, AES-256 at rest and TLS 1.2 or above in transit
  • Logging, monitoring and evidence — 5.24 to 5.28, 8.15, 8.16, 8.34: protected timestamped audit trails, session recording, SIEM forwarding, and scoped, expiring access for auditors
  • Remote, network and cloud access — 5.23, 6.7, 8.20, 8.21, 8.22: TLS-brokered access per service instead of exposed management ports, reaching segmented networks and cloud workloads without placing the operator on them
  • Data and endpoint protection — 5.14, 7.7, 8.1, 8.11, 8.12: expiring encrypted links for sharing secrets, automatic lock of idle sessions, secrets masked by default, and permission-controlled reveal, export and clipboard behaviour. Offline access, when enabled, keeps an encrypted local copy
  • Configuration, change, patching and backup — 8.8, 8.9, 8.13, 8.32: patch automation, standardized connection templates, versioned and attributed changes, and protected access to backup systems
  • Development and environments — 8.4, 8.31: separated dev, test and production secrets with runtime retrieval for pipelines

Some mappings cover part of a control: for 8.11, 8.13 and 8.24, Devolutions covers secrets, keys and the access to your systems, while masking of business data, your wider backup programme and your cryptography policy remain with your own processes and tools.

The complete mapping is on this page, with the specific capability and the products that deliver it for each control.

No, and any vendor claiming otherwise is describing something the standard does not allow. ISO 27001 certification assesses an organization's management system: its risk assessment, documented decisions, governance, and the demonstrable operation of its controls over time. A certificate is issued to an ISMS, never to a product.

What tools do is narrower and still valuable. They enforce specific Annex A controls so the control operates the same way every time, and they generate the artifacts an auditor asks to see — approval records, credential rotation history, session recordings, protected audit logs, entitlement reports.

Roughly a third of Annex A sits outside what any access platform can touch: physical site security, HR screening, disciplinary process, supplier contracting, management review. Those remain your work.

No. All ISO/IEC 27001:2013 certificates expired on 31 October 2025, the end of the three-year transition period that began when the 2022 edition was published.

Accredited certification bodies no longer recognize them, and an expired 2013 certificate cannot be reinstated. An organization that did not complete a transition audit before the deadline must pursue initial certification under ISO/IEC 27001:2022 through the full two-stage audit process.

If a supplier presents a 2013 certificate during due diligence, treat it as evidence of no current certification.

Annex A was restructured rather than expanded. The 114 controls across 14 domains were consolidated and deduplicated into 93 controls across four themes, and each control now carries attributes — control type, information security property, security domain — that make filtering and reporting considerably easier.

Eleven controls are genuinely new: 5.7 threat intelligence, 5.23 information security for use of cloud services, 5.30 ICT readiness for business continuity, 7.4 physical security monitoring, 8.9 configuration management, 8.10 information deletion, 8.11 data masking, 8.12 data leakage prevention, 8.16 monitoring activities, 8.23 web filtering, and 8.28 secure coding.

Several of the new controls concern how credentials and privileged sessions are handled, which is why five of them (5.23, 8.9, 8.11, 8.12 and 8.16) appear in the mapping above.

ISO/IEC 27001:2022/Amd 1:2024, published in February 2024, is known as the climate action amendment. It adds two short requirements: under Clause 4.1 you must explicitly determine whether climate change is a relevant issue for your ISMS, and under Clause 4.2 you must consider whether interested parties have climate-related requirements.

The amendment does not mandate that climate change is relevant to every organization. It requires that you consider the question and document your conclusion. Certification bodies have been checking for it during surveillance and recertification audits since 2024, and it is folded into the current standard.

ISO/IEC 27001:2022 does not name product categories. It states outcomes and leaves implementation to your risk assessment. That said, several Annex A controls are difficult to satisfy without the capabilities a PAM platform provides.

  • 8.2 requires that privileged access rights be restricted and actively managed, which is hard to evidence where administrators hold standing credentials
  • 8.15 and 8.16 require that activity be logged and monitored for anomalous behaviour
  • 5.28 requires procedures for identifying, collecting and preserving evidence of security events

Session recording is one of the most direct ways to satisfy the evidence and monitoring requirements for administrative activity, and auditors commonly accept it as such. It is a means, not a requirement.

Commonly cited timelines run from roughly six to twelve months for a first certification, but the number depends heavily on where you start and how narrow your scope is. Treat any specific figure, including this one, as an estimate rather than a commitment — your certification body is the authority on your timeline.

  • Scope: a single product line or business unit certifies faster than an organization-wide ISMS
  • Existing maturity: documented policies, an asset inventory and working access reviews shorten the gap analysis considerably
  • Resourcing: a named owner with dedicated time moves faster than a part-time effort across several teams
  • Evidence history: some controls must be shown operating over a period, so you cannot compress the observation window by adding people

Where tooling helps is the evidence burden rather than the calendar. Controls that produce their own audit trail — access approvals, rotation history, session recordings — remove the scramble to reconstruct evidence before a stage 2 audit.

Devolutions' ISO/IEC 27001:2022 certificate is published in the Devolutions Trust Center, along with legal documentation and pre-completed security questionnaire responses that cover most vendor due diligence requests.