Complies

RISK ASSESSMENT · SOC 2 CC3 · ISO 27001 6.1.2 · HIPAA · PCI DSS 12.3.1

Cyber security risk assessment tool for the yearly assessment your auditor reads

Run the assessment once with a fixed scale, record who scored each risk and when, and keep the result as evidence. Next year you reassess the same register instead of starting another spreadsheet.

See pricing

From $47/mo · Prices published · No sales call · Monthly billing

SOC 2 · TRUST SERVICES CRITERIA

Audit readiness

0 %

Your auditor makes the final call

Built for teams of 5 to 200

AWS GitHub Google Workspace Slack Jira Azure Okta
CRA

What a cyber security risk assessment tool should produce

A cyber security risk assessment identifies what could harm your systems and data, estimates how likely each event is and how bad it would be, and decides what to do about it. The output auditors and customers ask for is short and specific. A list of risks inside a defined scope, a score for each on a scale you wrote down in advance, an owner, a treatment decision and a date. NIST SP 800-30 describes the method in detail, and ISO/IEC 27005:2022 gives the ISO 27001 version of it.

Different rules ask for the same assessment in different words. SOC 2 tests it under CC3.2, ISO 27001:2022 under clause 6.1.2, HIPAA under the Security Rule risk analysis at 164.308(a)(1)(ii)(A), and PCI DSS 4.0 under 12.3.1 targeted risk analysis. Most teams do it once a year in a spreadsheet, and the spreadsheet is out of date by the following quarter.

Complies runs the assessment on its risk register. Each risk is scored on a five by five likelihood and impact scale, assigned to an owner and given a treatment, and a whole-register reassessment records who assessed what and when. The register is in the Growth plan at $119 a month billed yearly ($239 monthly). It is an assessment of risk, not a technical scan, and it does not test your systems for vulnerabilities.

Complies assists with compliance workflows. It is not legal advice, and it does not certify you or guarantee audit outcomes. Your auditor decides; Complies gets you ready.

SCOPE · SCORE · DECIDE

The three parts of an assessment that survives an audit

1

A scope and a method written first

State which systems, data and vendors are in scope and how risks are scored before scoring anything. Clause 6.1.2 of ISO 27001 asks for criteria set in advance so results are consistent and comparable.

obligation tracking
2

Scores a person stands behind

Each risk is scored by a named person on the same five step scales, with the date. Starting risks in the register never count as assessed until someone has scored them.

risk register
3

A decision for every risk

Mitigate with linked controls, accept with a reason, transfer or avoid. A high risk with no decision is the gap the assessment is supposed to close.

control mapping
COMPARE

Cyber risk assessment tools compared by what they produce

Tools sold as risk assessment tools produce very different things. Some are questionnaires, some are technical scanners, some are registers. Pick by the output the person asking for the assessment expects.

Tool What it produces Pricing Best fit
Complies A scored, owned and dated risk register tied to controls Published. From $119 a month billed yearly for the register Audit and customer evidence for SOC 2, ISO 27001, HIPAA and PCI DSS
Government templates (NIST SP 800-30 worksheets, HHS SRA Tool) A one-time assessment document No licence cost A first assessment by someone with time to fill it in
Vulnerability scanners A list of technical findings on hosts and applications Per asset, check each vendor page Finding exploitable weaknesses, which feeds an assessment
Integrated risk suites Enterprise risk assessments across business units Quote only Large organisations with a risk team

A scan is an input to a risk assessment, not the assessment itself. Auditors ask for the decisions you made about risk, and a scan report alone does not show them. For a comparison against the quote-only suites, see Archer alternatives, LogicGate alternatives and MetricStream alternatives.

CAPABILITIES

What changes when the assessment lives in a register

Next year starts from this year

The reassessment opens the existing register, so you rescore what changed instead of rebuilding the list.

Who and when are recorded

Each score and treatment carries its author and date, which is the evidence an auditor samples.

Gaps are named

Unowned risks, unscored risks and high risks without a treatment are listed, so you fix them before the audit.

Controls prove the mitigation

A mitigated risk links to controls with current evidence, not to a sentence in a document.

One assessment, several rules

The same assessment answers SOC 2, ISO 27001, HIPAA and PCI DSS questions through cross-mapped controls.

Published price, no demo

See the cost before a sales call and pay monthly if you only need one assessment cycle.

ONE ASSESSMENT

How the yearly assessment runs in four steps

01

Set the scope

Choose the frameworks and the systems in scope. The register opens with risks common to that setup.

02

Score every risk

Owners score likelihood and impact on the five step scales. Add the risks specific to your business.

03

Decide the treatment

Link mitigating controls, or record acceptance with a reason. High risks without a decision stay flagged.

04

Close and schedule

Complete the reassessment and set the next review date. The dated record stays on file as evidence for the auditor.

FIT

Who this is for, and who it is not

A GOOD FIT WHEN

  • An auditor, customer or regulator asks for your current cyber risk assessment.
  • You need a HIPAA Security Rule risk analysis or a PCI DSS targeted risk analysis kept on file.
  • Last year's assessment is a spreadsheet nobody has opened since.
  • You want to see the price before a sales call.

LOOK ELSEWHERE WHEN

  • You need a technical scan of hosts, cloud accounts or web applications.
  • You need a consultant to perform the assessment for you. Complies is the tool your team or consultant works in.
  • You need risk quantified in dollars.
  • You need a FedRAMP environment or CMMC support.
QUESTIONS

Questions about cyber security risk assessment tools

It is software that structures a cyber risk assessment. It defines the scope, lists risks, scores them by likelihood and impact, records owners and treatments and keeps the result as evidence. Some products use the same name for technical scanners, which find vulnerabilities but do not make risk decisions.

Define the scope and the scoring method, identify threats to the systems and data in scope, score each risk for likelihood and impact, decide a treatment for each and get the owners to accept residual risk. NIST SP 800-30 and ISO/IEC 27005 both describe this process.

No. A scan lists technical weaknesses. A risk assessment decides how likely and how damaging an event would be across people, processes, vendors and technology, and what you will do about it. Scan results are one input.

Most frameworks expect at least once a year and after significant change. ISO 27001 clause 8.2 requires planned intervals, HIPAA expects the risk analysis to be reviewed and updated as the environment changes, and PCI DSS 12.3.1 sets a review at least every 12 months for each targeted risk analysis.

Any scale works if it is defined before scoring and used consistently. A five by five matrix of likelihood and impact is common. Complies uses it, with scores from 1 to 25 banded as low, medium and high.

Yes, for a first assessment. Templates such as the NIST SP 800-30 worksheets work well once. The cost appears in year two, when the template has to be rebuilt and nobody can show who changed which score.

Complies publishes its prices. The risk register is in Growth at $119 and Scale at $299 a month billed yearly. Enterprise suites quote by scope.

Yes. Growth is $239 and Scale is $599 billed monthly, or roughly half that on yearly billing.

GO DEEPER

Frameworks and guides

Run this year's risk assessment in a register you keep

Prices published, $47 to $299 a month. Monthly billing. Start today, no sales call.