Evidence Automation Roadmap

Last modified by Lee Pedley on 2026/09/22 13:00

Integration Roadmap
The ISMS is now ready to receive recurring evidence. The records below are an implementation roadmap, not active integrations yet. Collectors should create immutable dated collection records and update the Evidence Source health/status.
PriorityPlatformPlanned evidence
1N-ableEstate inventory, managed-device coverage, patch compliance, missing/failed critical patches, inactive devices and endpoint health.
1Microsoft 365 / EntraIdentity inventory, privileged accounts, MFA/security configuration, stale/disabled accounts and selected Microsoft 365 assurance metrics.
1Arctic Wolf MDROpen security issues, severity, ageing and remediation/closure evidence.
1Arctic Wolf Managed RiskExposure/vulnerability position, high-risk items, ageing and remediation progress.
1Arctic Wolf Security AwarenessCampaign completion, overdue users and available awareness/testing metrics.
1ManageEngine Service Desk & ChangeSecurity/service incidents, SLA/ageing metrics, approved/emergency/failed changes and review evidence.
1ArcserveBackup coverage, job success/failure and restore-test evidence.
1BitdefenderEndpoint coverage, protection health, outdated/unmanaged agents and notable protection exceptions.
2NutanixCluster/host/VM inventory and platform health evidence.
2Cambium NetworksNetwork-device inventory, health and firmware/configuration assurance where available.
3Paxton, Hikvision and business applicationsPeriodic access/configuration reviews and selected health evidence where direct automation adds value.

Collection pattern

Collect → normalise → create Evidence Collection → attach/export snapshot → record hash where useful → update Evidence Source health → surface exceptions on the dashboard.

For technical assets, N-able can become the primary external inventory source. The ISMS retains governance attributes such as business owner, criticality, classification, risks and controls.