Your GRC dashboard isn't the evidence. Hash-chained proof for SOC 2, HIPAA + 6 more across AWS, Azure & GCP. Runs in your environment. On AWS Marketplace.

USA
Joined December 2009
Your compliance posture moves between audits. Now you see it move. NSAuditor AI Enterprise 2.0: each scan you run writes what moved since the last one, and what it could not measure, with the reason. Nothing watches between scans. Read "Where it stops" first: nsauditor.com/ai/enterprise
1
1
1
22
1/6 A scan that could not read part of your cloud should not read as clean. NSAuditor AI Enterprise 2.1.0 and Community Edition 1.1.0 are out. Enterprise now records GCP, Azure and EC2 instance inventories it could not read in full as evidence gaps. #CyberSecurity #Compliance
1
1
1
25
5/6 Drive scans from Claude? Through the MCP server in Community Edition 1.1.0, a host scan stops at a total time limit by default and names the plugins it did not run. A saved response keeps its request beside it, so verify-call checks both.
1
1
6
1/6 Your compliance posture moves between audits. Now you see it move. NSAuditor AI Enterprise 2.0.0 and Community Edition 1.0.0 are out: know what changed since the last scan, and hear about it in the tools your team already watches.
1
1
1
42
5/6 Weak-key and weak-signature certificate findings now fail the certificate control in SOC 2, HIPAA, NIST CSF 2.0, PCI DSS v4.0.1, ISO 27001 and CIS Controls v8. Eight frameworks, one read-only scan. Your scan data never goes to Nsasoft.
1
1
23
1/6 An SLA clock should only stop when the fix is measured. NSAuditor AI Enterprise 1.3.0 and Community Edition 0.2.57 are out: scan history you can put in front of an auditor, with SLA age and MTTR that keep counting a finding that never went away. What is new:
1
1
1
28
5/6 For compliance owners: a failed CVE lookup is now an evidence gap that fails the controls its CVE rows map to, 14 controls across seven frameworks. And every new, resolved and changed row in the client delta report carries a Basis cell saying what was checked.
1
1
19