Skip to content

How it works

Six steps from a reviewed plan to sustained readiness.

  1. 1

    Start your programme

    Choose a project type when creating a project — ISO/IEC 27001, CMMC, SMLDI, PCI DSS v4.0.1, SOC 1, AI governance or risk assessment. Start from a reusable template or an AI-drafted plan that people review, tailor and approve.

  2. 2

    Know your assets, analyse your risks

    Keep an asset register with C/I/A ratings and CSV import. Add risks, import an existing register or raise risks from projects and control gaps — one risk register per customer. Record threat, vulnerability and impact, with likelihood × impact scoring, threshold and appetite agreed by the customer and approved in Nelogi.

  3. 3

    See your gaps

    Mark each control Met, Partly met, Not met or Not applicable (justification required), see % met per framework, and export a Statement of Applicability (SoA) starting sheet. See evidence counts per control, progress by domain, and a control drawer with tasks, evidence and the applicability justification. Gap status reflects your team's assessment, not an audit opinion.

  4. 4

    Treat

    Choose Reduce, Transfer, Avoid or Accept per risk. Transfer and Avoid record who carries the risk and the supporting documents. Your team reviews suggested controls and AI-drafted treatment tasks. Link existing tasks from any project with suggested matches, reasons and duplicate warnings; work gets owners, dates and dependencies. Each customer’s treatment plan shows risk options, tasks, owners and progress. A risk can't be reassessed, sent for acceptance or closed while its treatment tasks are still open. Completing treatment does not close a risk; reassess residual risk.

  5. 5

    Evidence and sign-off

    Keep each customer's documents and evidence in one register, with versions, approvals and review dates. Link documents to projects, controls, risks and tasks; reuse approved evidence across tasks with the version recorded on each link. Evidence from build pipelines arrives internal until reviewed. Approvals use separation of duties; the risk owner accepts residual risk through a recorded approval with a reason, expiry date and the right approver for the level of risk.

  6. 6

    Stay ready

    Recurring control tasks are created on schedule, residual risk re-score prompts follow treatment, expired acceptances reopen risks, and training, reminders and daily summaries keep work moving.

Recorded work and approvals make governance visible. Completing a plan does not guarantee conformity or certification; advisory work is distinct from an independent certification audit. Deliverable approvals are separate from risk acceptance. Planned: chat alerts and connections to monitoring and security-testing tools.

See Nelogi on your next engagement

Book a demo