Update Vulnerability Management Policy to specify 'Data Migrators' in place of '[Company Name]' and improve clarity in the scope section.

Author: johnmckeever

src/pages/policies/vulnerability_management_policy.md

@@ -28,6 +28,7 @@ The purpose of this policy is to establish a systematic process for identifying,
 
 ## 2. Scope
 This policy applies to all technical assets owned or managed by Data Migrators, including:
+
 * **Production Infrastructure:** Cloud environments (e.g., AWS, Azure, GCP).
 * **Application Code:** Proprietary source code and build artifacts.
 * **Third-Party Dependencies:** Open-source libraries, APIs, and sub-processors.
@@ -52,7 +53,7 @@ We utilize a multi-layered detection strategy to ensure no single point of failu
 Vulnerabilities are initially ranked using the **Common Vulnerability Scoring System (CVSS)**. Final prioritization is determined by the Security Team based on the **exploitability** and **business impact** of the affected asset.
 
 ### 4.1 Remediation Service Level Objectives (SLOs)
-Once a vulnerability is confirmed (not a false positive), **[Company Name]** aims to remediate according to the following timelines:
+Once a vulnerability is confirmed (not a false positive), Data Migrators aims to remediate according to the following timelines:
 
 | Severity | CVSS Score | Remediation Target |
 | :--- | :--- | :--- |
@@ -64,7 +65,7 @@ Once a vulnerability is confirmed (not a false positive), **[Company Name]** aim
 ---
 
 ## 5. Remediation and Treatment Options
-**[Company Name]** recognizes that not all CVEs are immediately "patchable." One of the following four actions must be taken for every identified vulnerability:
+Data Migrators recognizes that not all CVEs are immediately "patchable." One of the following four actions must be taken for every identified vulnerability:
 
 1.  **Remediation:** Full patching or code change to remove the vulnerability.
 2.  **Mitigation:** Implementing compensating controls (e.g., WAF rules, IP whitelisting) that prevent exploitation even if a patch is unavailable.
@@ -82,7 +83,7 @@ If a **Critical** or **High** vulnerability cannot be remediated within the defi
 
 ## 7. Reporting and Audit
 * **Vulnerability Registry:** All findings are tracked in [e.g., GitHub Security/Jira/Snyk].
-* **Evidence of Compliance:** **[Company Name]** maintains logs of scan results and remediation actions for audit purposes (e.g., SOC 2, ISO 27001).
+* **Evidence of Compliance:** Data Migrators maintains logs of scan results and remediation actions for audit purposes (e.g., SOC 2, ISO 27001).
 * **Customer Disclosure:** Summary reports regarding our vulnerability posture are available to customers under NDA upon request.
 
 ---