PEAKDEFENCEWINGMAN · Use cases

Security operations control

Run security work through plans and tasks, with briefs, reminders and escalations, and ask "what needs to be done" against everything the model knows.

Typical requirementsISO 27001NIS2 Art. 21

Screens for this stage · Stage 1: Plans

Plans: recurring and one-off programmes
Plans Plans: recurring and one-off programmes Each plan groups the tasks it generates (asset, access, policy and risk reviews, internal audit) with its activities, owner and progress. Propose a plan asks WINGMAN to draft one.

Screens for this stage · Stage 2: Daily work

The Brief: state of the programme
The Brief The Brief: state of the programme Every morning WINGMAN writes the state of the programme from the records: where risk concentrates, coverage and control, a watch list and the tensions between groups of records.
My tasks
Tasks My tasks Tasks filtered to one person, with recurring markers, priority chips, status and due dates. Quick views for this week, this month and overdue.

Screens for this stage · Stage 3: Briefs and reminders

The Brief: state of the programme
The Brief The Brief: state of the programme Every morning WINGMAN writes the state of the programme from the records: where risk concentrates, coverage and control, a watch list and the tensions between groups of records.
The email the owner receives
Email notification The email the owner receives A signal routed to you: the record id and title, and what to do: open it beside the AI classification, then accept a suggestion or mark it a false positive.

Screens for this stage · Stage 4: Escalation

Overdue tasks across the organisation
Tasks Overdue tasks across the organisation The Overdue quick view lists late work with its assignee, so delays surface as people's names, not as a number.

Screens for this stage · Stage 5: Signals into work

The signals inbox
Signals The signals inbox Human-reported observations arrive as cards. WINGMAN classifies each one with a confidence score and proposes a risk or an incident; the owner accepts or rejects.
Remediation tasks accepted
Ask Wingman · step 4 Remediation tasks accepted Out-of-band verification for payment-detail changes, SPF/DKIM/DMARC reject policy, phishing-resistant MFA and more become tasks linked to the incident and its assets. One duplicate with a wrong id is rejected.

Sector angles

What this use case looks like under specific regulations.

ISO 27001 / SOC 2

Operational controls such as backups, logging and patching produce evidence every time they run.

Other use cases

Incident handling

Support every stage of an incident, from the first signal to the risk review it should trigger.

Supplier evaluation

Evaluate a supplier for feasibility before onboarding, and keep watching it afterwards.

Change management

Assess a planned change for impact, decide the controls needed before and after it, and keep one set of records as the result.

Regular reviews

Run the reviews good practice expects (assets, documents, risks, incidents, access) on a calendar instead of from memory.

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