PEAKDEFENCEWINGMAN · Use cases

Risk review and treatment

Review risks with all the context gathered since last time, plan their treatment, and keep several levels of risk consistent.

Typical requirementsISO 27001 6.1, 8.2NIS2 Art. 21DORA Art. 6

Screens for this stage · Stage 1: Scheduled review

Activities: what the plan generates and how often
Plans Activities: what the plan generates and how often Activity definitions name the target entity, the cadence (monthly, quarterly, semi-annual, annual) and whether tasks are generated per entity. Author with Wingman drafts the activities from the plan's instruction.
A plan with its generated review tasks
Plans A plan with its generated review tasks The Risk review plan: brief, task progress (7 of 12, 2 overdue), the next run date, and the review tasks it created per risk.
A review task with its prepared brief
Tasks A review task with its prepared brief WINGMAN prepares the review when the task is created: what changed since the last review, any suggested changes, and one button to confirm that the risk still stands.
The review calendar
Tasks The review calendar Calendar view of all tasks for November 2026: the monthly and high-risk reviews the plans generated, plus the quarterly management review meeting.

Screens for this stage · Stage 2: Context since last time

The review brief with a suggested rating change
Tasks The review brief with a suggested rating change After Start review, the brief proposes likelihood 3 → 4 with its reasoning: the system is in active use and no accuracy monitoring is deployed yet. Accept or Skip, then Complete review.
Help me complete this task GIF
Ask Wingman Help me complete this task Start review on a quarterly risk review task, ask Wingman for help, read its findings against the task checklist, accept the likelihood change, and complete the review with the outcome Monitored. The task closes as Done.
Findings against the task checklist
Ask Wingman · step 1 Findings against the task checklist The skill walks the task's own checklist: likelihood and impact need a decision, the definition is fine, the treatment plan needs updating, three overlapping review tasks should be consolidated. It offers to propose each change.

Screens for this stage · Stage 3: Several levels

A risk and everything linked to it
Risks A risk and everything linked to it Related tasks, the incident that realised the risk, the control that reduces it, the parent risk, and the risk position with the appetite line.

Screens for this stage · Stage 4: Treatment plan

Suggested change: likelihood 4 → 2
Risks · step 1 Suggested change: likelihood 4 → 2 A single incident in July and no recent successful breaches suggest the likelihood is overstated.
Accepted, with Undo
Risks · step 2 Accepted, with Undo The suggestion is marked Accepted and the button becomes Apply 1 change & complete. Nothing is written until the review is completed.
Review completed: score 16 → 8, Monitored
Risks · step 3 Review completed: score 16 → 8, Monitored The score drops from 16 to 8, severity from Critical to High, status moves to Monitored, the position on the matrix shifts, and the brief regenerates.
Review completed, task done
Tasks · step 2 Review completed, task done After Complete review the risk shows Monitored and Last reviewed today, and the task status is Done.

Screens for this stage · Stage 5: Register check

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.
Impact × likelihood matrix
Risks Impact × likelihood matrix The same register as a 5 × 5 matrix with counts per cell, beside the ranked list.

Sector angles

What this use case looks like under specific regulations.

NIS2

An all-hazards risk assessment per service, with treatments the management body can approve.

Financial sector

Risk and control self-assessment with second-line challenge, scheduled and tracked as a plan.

ISO 27001 / SOC 2

Risk assessment and treatment on a set cycle. A treatment decision changes the live Statement of Applicability straight away.

Videos

WINGMAN AI GRC – risk management use case Regular risk reviews and new risk identification, plus incidents, signals and vulnerability changes between reviews.
WINGMAN AI GRC – financial sector (DORA, MiCA, ECB) Live signals on critical functions, ICT and supply-chain risk, major incidents decided by people, and supervisor reports drafted for submission.

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

Other use cases

Vulnerability impact

Assess each vulnerability by the risk it raises, and fix first what matters most.

Risk identification

Find new risks without duplicates, link them to everything relevant, and let signals start identification or a re-review.

Business impact analysis

Assess how long each service can be down and what recovery it needs, from the services, risks and controls already recorded.

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