Free compliance framework explorer — browse controls, evidence, and implementation guidance.Subscribe for updates →
SOC 247
ITSP.10.17198
ISO 42001soon
ISO 27001soon

Browse

98 controls

03.11.02Vulnerability monitoring and scanningITSP.10.171Risk assessment

Official Requirement

A. Monitor and scan for vulnerabilities in the system [Assignment: organization-defined frequency] and when new vulnerabilities affecting the system are identified. B. Remediate system vulnerabilities within [Assignment: organization-defined response times]. C. Update system vulnerabilities to be scanned [Assignment: organization-defined frequency] and when new vulnerabilities are identified and reported.

Source: Canadian Centre for Cyber Security ITSP.10.171 (2025), adapted from NIST SP 800-171 Rev. 3

In Plain English

Your organization must regularly scan systems and applications for vulnerabilities, and also scan whenever new vulnerabilities are disclosed. Vulnerabilities must be remediated within defined timeframes based on risk severity. Your vulnerability scanning tools and signatures must be kept up to date.

Help us build what matters.

Vote for the next framework, subscribe for updates, and let us know if you'd contribute.

The Trust Services Criteria referenced in this tool are published by the American Institute of Certified Public Accountants (AICPA) and incorporate principles from the Committee of Sponsoring Organizations of the Treadway Commission (COSO). Criteria descriptions are reproduced for reference purposes. All implementation guidance, evidence recommendations, and control language are original work by Truvo Cyber. ISO 27001 and ISO 42001 are standards published by the International Organization for Standardization (ISO). Framework and standard names are the property of their respective owners. This tool is not affiliated with, endorsed by, or certified by AICPA, COSO, or ISO.

© 2026 Truvo Cyber. All rights reserved.

On-premises implementation and evidence

Vulnerability scanning and remediation

Implementation steps

  1. Deploy network and host-based vulnerability scanners across all systems; schedule authenticated scans at the defined frequency
  2. Subscribe to vulnerability advisories (CERT, NVD, vendor bulletins) and initiate ad-hoc scans when critical vulnerabilities are announced
  3. Define remediation timelines based on risk severity and track progress in a vulnerability management system
  4. Update vulnerability scanner plugins and signatures at the defined frequency to ensure detection of the latest vulnerabilities

Tools / systems

Evidence artifacts

Evidence frequency: Scans at defined frequency (weekly/monthly); continuous remediation tracking; per-event ad-hoc scans