Cloud Security Platform · Compliance Scan & Ayurak Trust
Framework scores that show how many controls were assessed
Aribot maps findings to the controls in each framework you report on, and every framework score states how many controls were actually assessed.
The problem
Our framework has a long list of controls, we hold evidence for a fraction of them, and the dashboard shows one percentage. When the CISO asks if we are compliant, the honest answer is 'for the controls we tested'. When the auditor asks for evidence, some controls marked compliant turn out to have been ticked and never tested.
How Aribot handles it
- 1
Choose your frameworks
Select the frameworks that apply to you, such as ISO 27001, SOC 2, PCI DSS or NIST CSF.
- 2
Assess what you can
Connected evidence sources mark each control met, failed or not assessed.
- 3
Attach the evidence
Each met control names the resource and the date it was tested.
- 4
Read the score with its count
Every framework score shows how many controls it was computed over.
What you get
- Met, failed and not-assessed counts on every framework
- Evidence for each control, with the resource and the test date
- One control mapping reused across every framework that shares it
- An answer for the auditor that separates tested controls from assumed ones
Related use cases
An audit trail the auditor can verify
Every live remediation is written to an append-only ledger, hash-chained and signed, and anyone with access can verify the chain on demand.
A posture score that shows which accounts it covers
Scan results across connected accounts, where the headline score states how many accounts it was computed over and unscanned accounts stay on the list.
Code findings tied to the line that caused them
Paste code and get findings mapped to STRIDE and MITRE ATT&CK, each tied to the line that produced it and paired with a recommended fix.