Assurance & Risk

Risk Assessment

Inherent risk, control assessment and residual risk are kept distinct, because a register that reports only one of the three cannot support a treatment decision.

Methodology

01
Identify
Identify the assets, processes, threats and weaknesses in scope.
02
Analyse
Analyse impact and likelihood.
03
Evaluate
Evaluate inherent risk, then residual risk after controls.
04
Treat
Determine treatment for each evaluated risk.
05
Monitor
Keep the register under review.

Approach to testing

Requirement — what does the applicable standard, regulation or framework require?
Control — what control has the organisation established?
Implementation — how is the control actually implemented?
Evidence — what evidence demonstrates that the control operates?
Risk — what happens if the control is ineffective or absent?
Action — what needs to be changed?
Validation — has the corrective action actually addressed the issue?

Types of assessment

Black-Box

Assessment begins with limited organisational information, to provide an independent perspective of the governance environment.

Grey-Box

Selected organisational documentation, process information and evidence are provided for structured assessment.

White-Box

Full documentation, evidence, stakeholder and process access is provided for detailed control validation.

Hybrid

Combines independent assessment techniques with detailed evidence and stakeholder validation.

Frameworks and standards

CSS Risk Assessment Methodology: The methodology the assessment is run to.
Risk Register: Where the assessed risks are held.
Risk Scoring Matrix: How impact and likelihood are scored.
ISO/IEC 27001 Risk Principles: The risk principles the methodology aligns to.

Tools used

Tooling is where testing starts, not where it ends. Every automated result is reproduced by hand before it reaches a report.

CSS Risk Assessment Methodology and Risk Register

Identification, scoring, treatment and acceptance, repeatable by the client's own people.

Risk Scoring Matrix

Consistent impact and likelihood scoring across assessments.

PlyoGRC

Where appropriate, the toolkits are supported through PlyoGRC for control, evidence, risk and compliance management.

Checklist approach

The checklist is the floor, not the ceiling. It guarantees coverage so nothing standard is missed; the findings that matter usually come from what a tester does after it is complete.

Identification

Asset / process identification
Threat identification
Vulnerability / weakness identification

Analysis

Impact assessment
Likelihood assessment
Inherent risk

Evaluation and treatment

Control assessment
Residual risk
Risk treatment
Risk acceptance

How CSS tests

A unified swarm of agents, for blind spot detection

AI agents drive several testing tracks against the same target at once, then cross-check each other. A single tester works one hypothesis at a time; parallel agents cover the space a sequential pass leaves behind.

Framework Mapping Agent — maps requirements and controls across applicable frameworks.
Policy Analysis Agent — identifies potential missing, inconsistent or outdated requirements.
Evidence Analysis Agent — associates evidence with applicable controls and identifies evidence gaps.
Risk Analysis Agent — identifies recurring risk themes and potential control weaknesses.
Blind-Spot Detection Agent — looks for issues that may not be immediately visible through conventional checklist assessment.
Executive Reporting Agent — helps transform detailed assessment information into concise management reporting.

AI-assisted analysis supports the assessment team but does not replace professional judgement. Material findings, risk conclusions and recommendations are reviewed and validated by CyberSmithSECURE professionals.

Why this differs

What CSS does that most vendors do not

Every one of these is checkable. Ask any vendor for the same and compare the answers.

Beyond the checklist

Structured checklists and framework mappings establish coverage, but the assessment continues through implementation, evidence, risk, action and validation.

Inherent and residual kept apart

Control assessment sits between the two, so the register shows what the controls are actually worth.

Operating control, not documentation only

Evidence is validated across five stages: Designed — is it appropriately designed? Implemented — has it been implemented? Operating — is it actually performed? Evidenced — can operation be shown? Effective — is it achieving its goal?

Human-in-the-loop AI assistance

What you receive

A working management system, not a folder of documents

The target state is that owners know what they must do, management knows what decisions are pending, and evidence exists to demonstrate that controls operate. Outputs are grouped by who uses them.

Executive layer

Scope, risk posture, roadmap, management decisions, KPI/KRI, readiness summary

GRC layer

Risk register, Statement of Applicability, policies, procedures, ownership, evidence map, action tracker

Assurance layer

Internal audit, findings, CAPA, management review, certification-readiness assessment

Operational layer

Control records, recurring reviews, awareness, supplier / access / incident / continuity evidence as applicable

Governance cadence established

Monthly: Risk / action review, evidence status, control exceptions, material incidents
Quarterly: Risk trend, supplier / control reviews, KPI/KRI, management action tracking
Annual: Internal audit programme, management review, ISMS objectives, risk refresh, improvement plan

For this engagement specifically

Control owners
IT teams
Security teams
Compliance teams
Process owners
Auditors
Key risks
Significant gaps
Business impact
Priority actions
Ownership
Target timelines

Scope this assessment

Most scopes are settled in one call. Tell us what the application does and who uses it, and we will tell you what testing it properly involves.

Start a conversation All Assurance & Risk capabilities