Build an ISMS aligned with ISO 27001.

Start from the Information Security (ISMS) project template in Manager: risk register, Annex A controls, Statement of Applicability and audits, run by your agent. Built around ISO/IEC 27001, as an independent template.

Why run your ISMS in Manager?

Risks decide the controls

Each risk gets a score, an owner and a treatment, which decides the controls.

Evidence where the work is

Each control runs to Verified with its evidence attached, ready for the audit.

Audits that close the loop

Every finding runs through root cause and corrective action until the fix holds.

ISO/IEC 27001 in brief.

ISO/IEC 27001 sets the requirements for an information security management system (ISMS). Clauses 4 to 10 run from context and leadership through planning and operation to evaluation and improvement. At the center: assessing risks against your own criteria and treating them.

Annex A lists reference controls, 93 in four themes in the 2022 edition. The Statement of Applicability records which apply and why. Audits, corrective action and reviews keep the ISMS improving.

  1. Scope
  2. Risk assessment
  3. Risk treatment
  4. Statement of Applicability
  5. Controls
  6. Audit
  7. Review

ISO/IEC 27001 in Manager.

Where each part of the standard lives in your project.

ISO/IEC 27001In Manager
Scope and risk criteria (clauses 4-6)A wiki page from the isms-context skill that every other skill checks against.
Risk assessment and treatmentRisk items with Likelihood, Impact, Risk Score, Risk Owner and Treatment.
Annex A and Statement of ApplicabilityOne Control per control with Control Family and Applicability; the SoA as a wiki page.
Internal audit (clause 9.2)An Audit item; each gap becomes a Finding.
Corrective action (clause 10.2)The Finding runs from Root Cause to Closed; fixes are child Action Items.
Management review (clause 9.3)A dated wiki page per review; decisions become Action Items.

The workflow.

  1. Create the project

    Connect your AI agent over MCP; it creates the project from the template.

    Say to your agentManager: Create a project from the Information Security (ISMS) template.

  2. Set the scope and assess risks

    Fix the scope and when a risk is acceptable. Then score each risk, name an owner and pick a treatment.

    Say to your agentManager: Use the isms-context skill to set our scope and risk acceptance criteria with me, then run risk-assessment.

  3. Publish the Statement of Applicability

    The agent creates a Control per Annex A control. You decide which apply and why.

    Say to your agentManager: Run the statement-of-applicability skill against our risk register.

  4. Implement and verify controls

    Take each applicable control to Verified. Open work runs as Action Items; evidence goes onto the Control.

    Say to your agentManager: Run the control-implementation skill for the applicable controls that are not verified yet.

  5. Audit, review, improve

    Audits raise Findings, corrective action closes them, and the management review sets what changes.

    Say to your agentManager: Run the next internal audit with the internal-audit skill.

What the template sets up.

A project created from the Information Security (ISMS) template starts with these work item types and statuses. You can adapt all of them to your team later.

Control

An Annex A reference control, assessed for applicability, driven to Verified.

  1. Not Implemented
  2. Partially Implemented
  3. Implemented
  4. Verified
  5. Not Applicable

Risk

An information security risk, scored, then treated or accepted.

  1. Identified
  2. Assessed
  3. Treating
  4. Monitored
  5. Risk Accepted

Finding

An audit nonconformity, worked through corrective action to closure.

  1. Open
  2. Root Cause
  3. Corrective Action
  4. Verifying
  5. Closed

Audit

An internal ISMS audit (clause 9.2).

  1. Planned
  2. Fieldwork
  3. Reporting
  4. Closed

Action Item

The default type: a task under a control, risk or finding.

  1. Open
  2. In Progress
  3. Done

Skills

These skills come with the template in Manager:

  • isms-context

    Scope, risk method, acceptance criteria. Run it first.

  • risk-assessment

    Identify, score and treat risks.

  • statement-of-applicability

    Seed Annex A controls, mark applicability, publish the SoA.

  • control-implementation

    Drive controls to Verified, with evidence.

  • internal-audit

    Plan an audit, sample controls, raise Findings.

  • corrective-action

    Root cause, fix, verify, close.

  • management-review

    Periodic review; decisions become Action Items.

Good to know.

Certification and the standard

Certification comes from an accredited certification body; Manager gets you ready for the audit. The standard itself is licensed by ISO, so check the seeded controls against your own copy.

Evidence with a trail

Attach policies and screenshots to the Control they prove. Item Activity, wiki revisions and the audit log show who changed what, when.

A breach is also a GDPR matter

Track personal data breaches in a Privacy & Data Protection project; in the app, a link connects them to the Risk here.

Your whole ISMS stays current.

Open Findings and Controls In Place show where you stand, and every change is on record for the next audit.

Get early access