Continuous control monitoring
Continuous control monitoring, with the evidence kept
A control that passed at last year's audit can fail the next week when someone creates an admin account without MFA. Argyx re-tests controls each time your systems sync and tells you when a result changes.
How the tests work
- Tests run on real data
- Argyx builds a snapshot from connected systems: users and MFA status, admin roles, endpoint sensors, cloud findings, open vulnerabilities, repositories, policies and vendors. Tests run against that snapshot.
- One test, many frameworks
- Each test is tied to a common control. When it passes or fails, the matching control in ISO 27001, SOC 2, NIST, CIS, HIPAA, PCI DSS and GDPR is updated in the same run.
- Results are evidence
- A run is stored when the result changes and at least once a day. Each control shows a trend of recent results, with the time and the detail of what was found.
- Manual assessments are respected
- If a person has assessed a control by hand, an automated run does not overwrite it.
- Run on demand
- Tests run after each integration sync. You can also start a run yourself, for example after fixing a gap.
What is tested
The 25 tests include:
- Identity
- All active users enrolled in MFA. Administrators use MFA, with no dormant or excess admins. No legacy sign-ins that bypass MFA.
- Endpoint and logging
- Endpoint protection deployed and sensors healthy. Security logs collected and fresh.
- Cloud
- Configuration against CIS and provider benchmarks. Storage and databases encrypted. TLS enforced. Keys rotated. No resources exposed to the internet.
- Vulnerabilities and code
- Critical findings fixed within 7 days and high within 30. Production branches require review. No leaked secrets left open.
- Governance
- Policies published and acknowledged. Risk register kept, with treatment for high risks. High-risk vendors assessed in the last 12 months.
Questions about Continuous control monitoring
What is continuous control monitoring?
It means testing security controls automatically and repeatedly, instead of checking them by hand before an audit. The aim is to find a failed control when it fails, and to keep dated evidence that it worked the rest of the time.
How often do the tests run?
After each integration sync, and on demand. A result is written to the evidence history when it changes and at least once every 24 hours.
Can we add our own tests?
Not as custom control tests today. You can add custom detections in Sigma on the Pro plan, and you can mark any control as manually assessed with your own evidence.
Which systems does it read from?
Microsoft 365 and Entra ID, Google Workspace, Okta, CrowdStrike, SentinelOne, AWS, Azure, Google Cloud, GitHub, GitLab and others. The integrations page has the full list.
Related pages
- SOC 2 compliance
Test SOC 2 controls from live data, collect evidence and give your auditor a read-only login.
- ISO 27001 compliance
Clauses 4 to 10 and all 93 Annex A controls of ISO/IEC 27001:2022, with tests, policies and a risk register.
- Compliance automation
How the eight frameworks and 949 controls fit together.
- Integrations
The identity, endpoint, cloud and engineering tools Argyx reads from.
- AI SOC
AI triage for every alert, incidents with timelines, and response playbooks that wait for a human approval.
Try it on your own environment.
The trial runs for 14 days and needs no card. Connect one identity provider and you will see real results in about fifteen minutes.