PEAKDEFENCEWINGMAN · Use cases

New requirements

Implement a new regulation or standard by reusing and linking what already exists, then drive the rest with tasks and plans.

Typical requirementsNIS2DORACRAISO 27001

Screens for this stage · Stage 1: Import

A contractual requirement mapped to standard clauses
Requirements A contractual requirement mapped to standard clauses A customer contract clause (report incidents within 72 h) is met by one control and mapped to ISO 27001 A.5.26 and NIS2 Article 21, so one control satisfies three sources.

Screens for this stage · Stage 2: Gap analysis

Gaps to close and the organisation's temperature
The Brief Gaps to close and the organisation's temperature Eleven register checks run on every record: risks without an owner or score, requirements without a control, tasks overdue by more than 30 days, vulnerabilities past the patching SLA, unapproved documents. Each gap links to the records behind it.

Screens for this stage · Stage 3: Context

The whole model, clustered
Graph The whole model, clustered 228 nodes and 310 edges: risks, requirements, controls, assets and tasks as clusters, with the links between them. Start from any entity type, choose the depth, find a node, save a view.
A control, the policy behind it and the clauses it meets
Controls A control, the policy behind it and the clauses it meets Enforced MFA on all Google Workspace accounts: fully compliant, documented in the technical security policy, applied to two assets, meeting ISO 27001 A.8.5 and A.5.17.

Sector angles

What this use case looks like under specific regulations.

Videos

ISMS implementation with WINGMAN AI Building an information security management system in WINGMAN, from requirements and scope to risks, controls, owners and the review cycle.

Plays from youtube-nocookie.com. YouTube sets no cookies until you press play.

Other use cases

All use cases

See WINGMAN on your own data

We can walk through any of these use cases with your requirements, risks and controls.

Contact Peak Defence