Cyber Field Assessment
Campaigns that feed the risk register
A field response can propose a risk directly into the register, so assessment findings become tracked risk rather than terminating in a report nobody reopens.
- Questionnaire templates with versioned revisions
- Campaigns with recurrence patterns
- Assignments with delegation where the respondent is not the owner
- Risk proposals raised from responses
In the application · Assure
- Field assessment overview
- Campaigns
- Templates
- Assignments
- Risk proposals
- 1Questionnaire templateVersioned revisions, sections, question types
- 2CampaignRecurrence pattern set by the programme owner
- 3AssignmentsPer respondent, delegation permitted
- 4ResponsesEvidence attached per question
- 5Risk proposalFindings promoted into the risk register
Campaigns
Recurring by design
Campaigns carry a recurrence pattern and a status, so a quarterly field assessment is a standing programme rather than something recreated by hand each cycle.
- Template revisions preserved so historical responses stay interpretable
- Sections and typed questions within each revision
- Assignment status tracked per respondent
- Evidence attached per question response
Level 3: Well Defined
A standard process is defined and followed across the organisation.
Every question in the control library carries its own written descriptor at each level.
Framework alignment
Works with your control frameworks
This module shares the platform control library. International standards, sector regulations and your own internal standard are loaded the same way and mapped to one another, wherever you operate.
Solutions by role
Built for your team
See cyber field assessment in your environment
A walkthrough scoped to your entities, your frameworks, and the way your programme is actually run.