Scope
Enumerate covered assets and environments (on-premises, cloud, containers, OT). Specify exclusions and interfaces with third parties.
A formal policy ensures consistent discovery, prioritization, and remediation of vulnerabilities, reduces mean time to remediation, and documents governance for auditors and regulators. It also clarifies roles and escalation paths so security, IT operations, and business owners can act quickly and track results.
Common users include security and IT operations teams, compliance staff, and application owners who implement and follow the policy.
The Chief Information Security Officer approves the policy, sets risk tolerance, and certifies compliance to senior leadership and external auditors. The CISO signs to confirm that program resources and SLAs are adequate and that reporting will be produced as required.
An IT Director or VP of Infrastructure signs to accept operational responsibilities for scanning schedules, patch windows, and remediation workflows, and to commit resources for corrective action and verification testing.
Enumerate covered assets and environments (on-premises, cloud, containers, OT). Specify exclusions and interfaces with third parties.
Require a maintained inventory with owner, classification, and criticality to enable prioritized scanning and response workflows.
List authorized scanning tools, authenticated vs unauthenticated scans, and threat intelligence sources used for discovery and validation.
Define risk calculation (CVSS baseline, compensating controls, asset criticality) and how scores drive remediation priority.
Set target timelines by severity (e.g., critical, high, medium, low), patch windows, and exception approval processes for deferred fixes.
Specify required dashboards, monthly metrics (MTTR, open vulnerabilities), exception logs, and executive reporting cadence.
| Field | Configuration |
|---|---|
| Scan Frequency | Weekly authenticated scans for critical assets |
| Ticketing Integration | Auto-create tickets in ITSM with severity tags |
| Exception Process | Formal waiver with risk acceptance and expiration |
| Verification | Post-remediation re-scan and verifier sign-off |
Define how the approved policy and remediation approvals will be signed, archived, and linked to tooling.
Retain raw and summarized scan data (timestamps, tool used, CVE references) in PDF and native report formats for validation.
Preserve ticket IDs, assignees, evidence of fix, and verification notes; store as PDF and link to ITSM records.
Document residual risk decisions and exception approvals; maintain signed approvals and expiry dates in the record.
Export signed policy and approval certificates in PDF/A with embedded metadata for long-term archival.
Xerox integrated signing into their ERP to centralize approvals and reduce delays in evidence collection.
BIS standardized remediation SLAs and captured electronic approvals for exceptions.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes (BAA required) | Varies | Varies | Varies | Varies |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies | Varies | Varies |