Enterprise Security Maturity Program

Cybersecurity Maturity Model Certification (CMMC) Level 1 Implementation

Status: ACTIVE PROGRAM

Classification: CONFIDENTIAL

Prepared: June 25, 2026 Audience: C-Suite / Board Scope: Federal Contract Information (FCI)
17 Required Practices 6 Control Domains Annual Compliance Cycle Legal Attestation Required
CRITICAL HIGH RECOMMENDED

Domains

6

Practice families

Practices

17

All must be MET

Cadence

Annual

Self-assessment

Submission

SPRS

+ Senior Official

What is CMMC Level 1?

CMMC Level 1 certification protects Federal Contract Information (FCI) — basic business data shared under DoD contracts. It requires implementing 17 security practices across 6 domains. The assessment is a self-certification submitted annually to suppliers.gov (SPRS).

Phase 1 enforcement window: November 10, 2025–November 10, 2026. New FCI contracts require Level 1 certification. Existing contracts have a 6-month grace period.

Key commitment: Your Senior Official (typically CEO/Owner) personally affirms to the DoD that all 17 practices are met. This is a legal attestation. Non-compliance or false certification has civil and criminal consequences.

Program Goals

Critical Success Criteria: All 17 practices must show MET status with documented evidence before SPRS submission. Any "NOT MET" or missing evidence will result in failed certification. Senior Official attestation is only valid when all practices are demonstrably in place.
  • Achieve certified CMMC Level 1 status within 6–8 weeks
  • Implement ALL 17 practices with documented evidence — zero "NOT MET" items at submission
  • Establish centralized evidence repository and annual self-assessment governance process
  • Build compliance foundation aligned with SOC 2 Type II and ISO 27001 controls for future readiness
  • Enable organizational resilience and reduce breach risk across email, endpoints, and data assets
Total estimated effort: ~62–80 hours across all phases. Spread over 6–8 weeks for a small org (under 50 users). Larger orgs add ~15% per 25 additional users.

6-Week Implementation Timeline

Phase 1  Foundation — Week 1–2 ~18–22 hrs

Tenant assessment, MFA, Conditional Access, admin hardening, audit logging

Phase 2  Email & Data Controls — Week 2–3 ~12–16 hrs

Defender for Office, anti-phishing, DLP policies, SharePoint/OneDrive restrictions

Phase 3  Endpoints & Intune — Week 3–5 ~18–24 hrs

Device enrollment, compliance policies, Defender for Endpoint, BitLocker, patching

Phase 4  Evidence & Attestation — Week 6 ~10–14 hrs

Screenshot evidence collection, SSP documentation, SPRS submission support

Phase 1  Foundation (Week 1–2) — ~18–22 hrs

Tenant baseline assessment

Run Microsoft Secure Score review, export current config, document gaps vs. CMMC L1 17 practices

2–3 hrs

Entra ID / Azure AD user audit

Identify all accounts, remove stale/shared accounts, confirm no orphaned admin accounts

2–3 hrs

MFA enforcement rollout

Enable Security Defaults or Conditional Access MFA for ALL users. Communicate to staff, handle exceptions

3–4 hrs

Conditional Access policies

Block legacy auth, require MFA for all apps, block risky sign-ins, set compliant device policy

3–4 hrs

Admin role hardening

Reduce Global Admin count to 2 max, enable PIM if licensed, no admin on daily-use accounts

2 hrs

Audit logging enablement

Turn on Unified Audit Log, confirm mailbox auditing, set retention to 90 days minimum

1–2 hrs

Password policy hardening

Set 12-char minimum, enable Entra ID Password Protection, disable password expiration with MFA

1 hr

Break-glass accounts

Create 2 emergency admin accounts, store securely, exclude from CA policies, monitor for use

1 hr

Phase 2  Email & Data Controls (Week 2–3) — ~12–16 hrs

Defender for Office 365 baseline

Enable Safe Links, Safe Attachments, anti-phishing policies (Standard or Strict). Via Security portal.

2–3 hrs

Anti-spam & anti-malware tuning

Review and harden default policies, enable auto-purge (ZAP), quarantine review setup

1–2 hrs

Email authentication (SPF/DKIM/DMARC)

Verify SPF records, enable DKIM signing, set DMARC to p=quarantine minimum

2 hrs

DLP policy for FCI

Create DLP policy to detect/block FCI leaving org via email or SharePoint. Start in audit mode.

2–3 hrs

SharePoint/OneDrive sharing lockdown

Set external sharing to Disabled or specific-people only. Restrict anonymous links.

2 hrs

Evidence repo setup

Create dedicated private SharePoint site for CMMC evidence. Configure permissions and folder structure.

1–2 hrs

Phase 3  Endpoints & Intune (Week 3–5) — ~18–24 hrs

💻 Intune Scoping for Level 1: Enroll ALL corporate-issued devices that access FCI — laptops, desktops, and mobile devices used for work email, file access, or contract-related communications. Document your scope boundaries in the SSP. Personal devices, break-room kiosks, and printers are out of scope unless they access FCI.

Intune tenant setup & licensing check

Confirm MDM authority set to Intune, verify M365 Business Premium or Intune Plan 1 licenses assigned

1–2 hrs

Windows device enrollment

Enroll Windows devices via Autopilot, bulk enrollment, or manual Entra join. Build enrollment comms.

4–6 hrs

Device compliance policies

Require: OS min version, BitLocker on, Defender enabled, no jailbreak, max 3-day sign-in inactivity. Tie to Conditional Access.

2–3 hrs

BitLocker encryption enforcement

Deploy BitLocker config profile via Intune, enforce full disk encryption, escrow recovery keys to Entra ID.

2–3 hrs

Microsoft Defender for Endpoint

Onboard devices to MDE via Intune policy, confirm real-time protection ON, configure tamper protection

2–3 hrs

Windows Update / patch baseline

Create Update Ring policy: quality updates within 7 days, feature updates within 30 days.

1–2 hrs

Application control / approved apps

Deploy required apps (M365 Apps, Defender, VPN if used) via Intune. Block unauthorized software installs.

2 hrs

USB/removable media policy

Deploy policy to block or audit USB storage devices on FCI endpoints. Covers MP.1.118 media protection.

1 hr

Screen lock & idle timeout

Enforce 15-min screen lock via Intune config profile. Require password/PIN to unlock.

1 hr

Phase 4  Evidence & Attestation (Week 6) — ~10–14 hrs

Evidence screenshot collection

Screenshot every control: Conditional Access policies, MFA report, Defender status, BitLocker compliance, DLP policies, audit log settings

3–4 hrs

SSP (System Security Plan) writeup

Document the in-scope environment, all 17 practices and how they're met, evidence location references.

3–4 hrs

POA&M for any gaps

Document any remaining NOT MET items with remediation owner, timeline, and interim compensating controls

1–2 hrs

Senior Official review session

Walk the affirming officer through evidence package. Answer questions. Get sign-off on accuracy before SPRS submission.

1–2 hrs

SPRS score entry

Senior Official logs into SPRS, enters score (target: 110), affirms submission.

1 hr

The DoD doesn't mandate a specific tool — but they DO require evidence to be secure, controlled-access, and retrievable for the annual affirmation cycle. Here's the tiered approach by maturity:

🏆 Recommended — GCC High SharePoint / OneDrive

M365 Business Premium minimum

Best Fit
  • ITAR/FCI-appropriate environment — GCC meets the bar for Level 1
  • Role-based access controls, audit logging built-in
  • Version history on every document (critical for annual reviews)
  • Administrative access for managing permissions and structure
  • Easy to share view-only links for auditor review if needed

Strong Alternative — Google Workspace (Gov) or AWS GovCloud S3

If organization is already on Google or AWS ecosystem

  • Google Workspace for Government — FedRAMP authorized
  • Strict folder-level sharing, audit logs in Admin Console
  • S3 with bucket policies + CloudTrail audit logging

Avoid — Personal Dropbox, non-GCC OneDrive, or local shared drive

Consumer-grade storage is not appropriate for FCI evidence. Fails access control and audit log requirements.

Recommended Folder Structure (SharePoint / GCC)

📁 CMMC-L1-Evidence/

📁 00_Governance/

→ System Security Plan (SSP), Scope Statement, Asset Inventory

📁 01_Access-Control (AC)/

→ AD/Entra screenshots, MFA policy, user account list

📁 02_Identification-Authentication (IA)/

→ Password policy, MFA enrollment proof

📁 03_Media-Protection (MP)/

→ Sanitization policy, disposal records

📁 04_Physical-Protection (PE)/

→ Access logs, facility control documentation

📁 05_System-Comms-Protection (SC)/

→ Firewall rules, network diagram, encryption configs

📁 06_System-Info-Integrity (SI)/

→ AV/EDR proof, patch management records, update logs

📁 07_Annual-Assessment-Records/

→ Signed checklist, SPRS submission screenshot, affirmation record

Access Control (AC) — 4 practices

  • AC.1.001 — Limit system access to authorized users
  • AC.1.002 — Limit access to authorized transaction types
  • AC.1.003 — Control external system connections
  • AC.1.004 — Control CUI/FCI on publicly accessible systems

Identification & Authentication (IA) — 2 practices

  • IA.1.076 — Identify all system users and processes
  • IA.1.077 — Authenticate users before allowing access

Media Protection (MP) — 1 practice

  • MP.1.118 — Sanitize or destroy media before disposal/reuse

Physical Protection (PE) — 4 practices

  • PE.1.131 — Limit physical access to authorized individuals
  • PE.1.132 — Escort visitors and monitor activity
  • PE.1.133 — Maintain audit logs of physical access
  • PE.1.134 — Control and manage physical access devices

System & Comms Protection (SC) — 2 practices

  • SC.1.175 — Monitor, control, and protect comms at boundaries
  • SC.1.176 — Implement subnetworks for publicly accessible systems

System & Info Integrity (SI) — 4 practices

  • SI.1.210 — Identify, report, and correct system flaws
  • SI.1.211 — Provide malicious code protection (AV/EDR)
  • SI.1.212 — Perform periodic scans and real-time monitoring
  • SI.1.213 — Update malicious-code protection mechanisms

Pre-Meeting Preparation

  • Confirm the contract has FCI — not CUI (scope check)
  • Identify the Senior Official who will sign the SPRS affirmation (typically CEO/Owner)
  • Create the evidence folder structure in GCC SharePoint or chosen repo
  • Download the official DoD CMMC Level 1 Assessment Guide (v2.0)
  • Prepare a 17-row tracker spreadsheet with columns: Practice ID | Description | Owner | Status | Evidence Location | Notes
  • Draft a simple System Security Plan (SSP) template — even a 2-pager works at L1

Meeting Agenda (90 min suggested)

0:00–0:10

Welcome + Context Setting

  • Explain what CMMC Level 1 actually is — protect FCI, not CUI
  • Confirm scope: which systems, people, and locations handle FCI?
  • Clarify roles and responsibilities for this initiative
  • Remind: the Senior Official personally affirms to the DoD — legal attestation
0:10–0:25

Walk the 17 Practices — High Level

  • Walk through each of the 6 domains briefly
  • Ask for a show of hands / gut check: "Do we think we're doing this today?"
  • Note obvious wins (likely already have AV, MFA, locked doors)
  • Flag areas of concern immediately — physical access logs often surprise
0:25–0:50

Assign Owners + Set Status (Live Tracker Walk)

  • Open the 17-row tracker on screen — fill in owner and initial status together
  • For each practice: who owns it? What evidence exists? What's missing?
  • Mark each as MET / NOT MET / UNKNOWN — honesty is critical
  • Every NOT MET becomes a task
0:50–1:05

Evidence Repo Setup + Document Roles

  • Introduce the SharePoint/GCC folder structure — show the live setup
  • Assign who uploads evidence for each domain
  • Set expectations: "Document and organize evidence systematically for each practice."
  • Walk through what acceptable evidence looks like for 2–3 sample practices
1:05–1:20

Project Plan + Timeline

  • Set a realistic target date for SPRS submission (most small orgs: 4–8 weeks)
  • Establish weekly check-in cadence — 30-min standing call works well
  • Assign remediation tasks with deadlines from the NOT MET list
  • Define what "done" looks like: all 17 MET + evidence uploaded + SSP signed + SPRS submitted
1:20–1:30

SPRS + Affirmation — Explain the End State

  • Walk through the SPRS portal (suppliers.gov) — show them what they'll submit
  • Explain the Senior Official affirmation — they must do this personally
  • Remind: SPRS scores are visible to contracting officers
  • Annual reassessment date should go on the calendar before leaving this call
Multi-Factor Authentication (MFA)
CRITICAL

Enable MFA for ALL users — no exceptions

Entra ID → Security → MFA → Enable per-user or via Conditional Access. Security Defaults is minimum; Conditional Access is better.

CRITICAL

Require MFA for all admin accounts

Create a Conditional Access policy: All admins → Require MFA → Always (no exclusions, no trusted IPs).

HIGH

Use Microsoft Authenticator app, not SMS

SMS is SIM-swap vulnerable. Push notification + number matching is minimum. Passkeys/FIDO2 keys ideal for admins.

HIGH

Block legacy authentication protocols

Conditional Access → Conditions → Client Apps → Legacy Auth → Block. Kills IMAP/POP/SMTP basic auth.

Conditional Access Policies
CRITICAL

Require MFA for all users accessing cloud apps

CA Policy: All users → All cloud apps → Grant: Require MFA. This is your baseline.

HIGH

Require compliant device for access to FCI data

CA Policy: Grant → Require device to be marked compliant (needs Intune). Enforces endpoint controls before data access.

HIGH

Sign-in risk policy — block high-risk sign-ins

Requires Entra ID P2. CA Policy: Sign-in risk = High → Block. Medium → Require MFA.

User & Password Policies
CRITICAL

No shared accounts — every user has their own login

Shared accounts kill auditability. If they exist, eliminate them before assessment.

CRITICAL

Enforce strong password policy

Min 12 characters. Enable Entra ID Password Protection to block common passwords + custom banned list.

HIGH

Disable accounts immediately upon termination

Document offboarding checklist: disable Entra account → revoke sessions → remove licenses → forward email → backup data.

Role & Privilege Management
CRITICAL

Limit Global Admin accounts to 2–3 max

Entra ID → Roles → Global Administrator. Break-glass accounts only. Day-to-day admins use scoped roles.

CRITICAL

Admins use separate admin accounts

Never use a Global Admin account for daily email/browsing. Separate user@company.com from admin.user@company.com.

HIGH

Enable Privileged Identity Management (PIM)

Requires Entra ID P2. Admins request elevation just-in-time. Global Admin is never always-on.

Anti-Phishing & Malware
CRITICAL

Enable Defender for Office 365 — Safe Attachments + Safe Links

Security & Compliance Center → Threat policies → Safe Attachments (Block on malware) + Safe Links (Rewrite all URLs, block known bad).

CRITICAL

Configure anti-phishing policy with impersonation protection

Threat policies → Anti-phishing → Enable mailbox intelligence, impersonation protection for key users and domain.

CRITICAL

Set up SPF, DKIM, and DMARC on the domain

SPF: v=spf1 include:spf.protection.outlook.com -all. Enable DKIM. DMARC: start with p=none, move to p=reject within 30 days.

HIGH

Block auto-forwarding to external addresses

Exchange Admin → Remote domains → uncheck "Allow automatic forwarding." Create mail flow rule to block forwarding.

Email Data Protection
HIGH

Enable Purview Information Protection (sensitivity labels)

Create labels: Internal, FCI — Confidential, FCI — Restricted. Train users to apply. Labels can enforce encryption.

HIGH

Create DLP policy to detect and block FCI data leaving

Purview → Data Loss Prevention → Policy for contract numbers, CAGE codes, or sensitive keywords. Alert or block sending externally.

SharePoint & OneDrive Controls
CRITICAL

Disable "Anyone with a link" sharing tenant-wide

SharePoint Admin Center → Policies → Sharing → Set to "Only people in your organization" or "Specific people." No anonymous links.

CRITICAL

Create a dedicated FCI SharePoint site — restricted membership

Separate site from general company SharePoint. Only users needing FCI access are members. Evidence repo lives here. Private site.

HIGH

Enable versioning on all document libraries

Library Settings → Versioning → Enable major versions, keep at least 50. Provides ransomware recovery and change history.

HIGH

Restrict OneDrive sync to managed devices only

SharePoint Admin → Settings → Sync → Allow sync on PCs joined to specific domain or Intune-compliant. Stops syncing FCI to personal laptops.

Microsoft Teams Controls
CRITICAL

Disable or restrict external/guest access in Teams

Teams Admin Center → Org-wide settings → External access and Guest access. If guests needed, restrict to specific domains. FCI never passes through guest channels.

HIGH

Disable third-party app installs in Teams

Teams Admin → Teams apps → Permission policies → Block all third-party and custom apps unless specifically approved.

Intune Device Management (MDM)
CRITICAL

Enroll ALL corporate-issued devices into Intune

Windows: Autopilot or manual Entra Join + Intune enrollment. Mac: ADE enrollment via Apple Business Manager. No unmanaged device accesses FCI.

CRITICAL

Create compliance policies — enforce them via Conditional Access

Intune → Compliance → Windows policy: require BitLocker, require AV, min OS version, no jailbreak. Mark non-compliant devices as blocked.

CRITICAL

Deploy Windows Update for Business — enforce patching

Intune → Update rings: security updates within 7 days, feature updates within 30. No device older than 30 days behind on patches.

CRITICAL

Enable BitLocker encryption on all Windows devices

Intune → Endpoint security → Disk encryption → BitLocker policy. Full disk encryption on OS and fixed drives. Store recovery keys in Entra ID.

HIGH

Configure device lock / screen timeout policy

Intune → Configuration profile: screen lock after 5–15 min idle, require PIN/password to unlock.

HIGH

Enable remote wipe capability

Intune enrolled devices can be wiped remotely. Document the process. Apply when device lost/stolen or employee terminated.

Antivirus & Endpoint Protection
CRITICAL

Deploy Microsoft Defender Antivirus via Intune

Intune → Endpoint security → Antivirus → Windows Defender policy. Enable real-time protection, cloud-delivered protection, auto sample submission.

CRITICAL

Verify AV definitions update automatically — daily minimum

Policy: signature update interval every 4–8 hours. Verify via Intune compliance report. Screenshot definition version report for evidence.

CRITICAL

Enable scheduled scans + real-time scan on file download

Defender policy: weekly full scan, real-time protection always on, scan USB/removable drives, scan email attachments.

HIGH

Enable Microsoft Defender for Endpoint (MDE)

Included in M365 Business Premium. Provides EDR, threat & vulnerability management, attack surface reduction. Critical for CMMC posture.

HIGH

Block USB / removable storage on FCI-handling devices

Intune → Configuration profile → Device restrictions → Block removable storage. Or use MDE Device Control. No FCI leaving on thumb drive.

Endpoint Configuration Hardening
CRITICAL

Deploy security baseline via Intune

Intune → Endpoint security → Security baselines → Windows 365 Security Baseline. Microsoft-curated 200+ settings. Apply to all managed devices.

HIGH

Disable local administrator accounts on endpoints

Enable LAPS (Local Administrator Password Solution) via Intune. Randomizes local admin passwords per machine.

HIGH

Enable Windows Firewall — all profiles

Intune → Endpoint security → Firewall → Windows Firewall policy. Block inbound by default, allow outbound. Log dropped packets.

Boundary Protection (SC.1.175)
CRITICAL

Business-grade firewall — not a consumer router

Meraki MX, Fortinet, Palo Alto, or equivalent. Must have stateful inspection, application awareness, and logging.

CRITICAL

Block inbound traffic by default — allowlist only what's needed

Firewall rules: default deny inbound, explicit allow for business services only. Document every open inbound port.

CRITICAL

DNS filtering / protective DNS

Deploy Cisco Umbrella, Cloudflare Gateway, or MS Defender for DNS. Blocks malicious domains, C2 traffic before connection made.

HIGH

Separate guest Wi-Fi from corporate network

Guest SSID must be on separate VLAN with no access to internal resources. Visitors and personal devices on guest only.

HIGH

Remote access via VPN or Zero Trust (not open RDP)

Never expose RDP directly to internet. Use MFA-protected VPN or Azure AD Application Proxy / ZTNA solution.

MED

Enable firewall logging — retain 90 days minimum

Forward firewall logs to syslog or SIEM. Log denied inbound, allowed inbound, and VPN connections.

M365 Audit Logging
CRITICAL

Confirm Unified Audit Log (UAL) is turned ON

Purview → Audit → Verify audit logging is active. Should be on by default. Captures sign-ins, file access, admin actions, mail events.

CRITICAL

Set audit log retention to 1 year minimum

Default UAL retention is 90 days (E3) or 1 year (E5/Business Premium). If on lower plan, export logs monthly to evidence SharePoint.

HIGH

Enable Entra ID sign-in and audit logs

Entra ID → Monitoring → Sign-in logs + Audit logs. Export to Log Analytics or storage account for long-term retention.

HIGH

Set up alerts for suspicious activity

Purview → Alert policies: mass file download, impossible travel sign-in, new admin role assigned, mail forwarding rule created.

HIGH

Review Microsoft Secure Score monthly

security.microsoft.com → Secure Score. Track score over time. Screenshot monthly score for evidence of ongoing monitoring.

Incident Response Basics
CRITICAL

Document a written Incident Response plan

1–2 pages: what counts as an incident, who to call (legal, DoD POC if FCI involved), steps to contain, steps to document. Store in evidence repo.

HIGH

Know your DoD incident reporting obligation

If FCI is compromised, may have reporting obligations to contracting agency. Check contract language. Some require reporting within 72 hours.

Tenant-Level Admin Settings
CRITICAL

Disable Microsoft 365 app self-service purchases

M365 Admin → Settings → Org settings → Self-service purchases → Block. Prevents users from buying unapproved apps.

CRITICAL

Control which third-party apps can connect to M365

Entra ID → Enterprise Applications → User consent settings → Disable user consent. Require admin approval. Review existing connected apps.

HIGH

Conduct security awareness training annually (minimum)

Use Microsoft Attack Simulator (included in Business Premium) for phishing simulations. Keep completion records in evidence repo.

MED

Backup M365 data with a third-party backup tool

Microsoft's recycle bin is NOT a backup. Use Veeam, Datto SaaS Protection, or Acronis. Test restore quarterly. Document the test.

MED

Document everything — system inventory + network diagram

Maintain a list of all systems, devices, and users in scope. Your SSP needs this. Update whenever things change.

M365 License Recommendation for CMMC L1

✅ Microsoft 365 Business Premium

Includes Intune, Defender for Business (EDR), Entra ID P1, Defender for Office 365 P1, CA, Purview basics. ~$22/user/mo. Sweet spot for CMMC L1 SMBs.

⚠️ M365 Business Standard or E3

Missing Defender for Business EDR and some CA features. Gaps in SI.1.211–213. Need third-party EDR (SentinelOne, CrowdStrike).

What is ITAR?

International Traffic in Arms Regulations — U.S. government regulations controlling export and import of defense-related articles and technical data on the U.S. Munitions List (USML).

  • Administered by the State Department (DDTC)
  • Applies to defense articles, military aircraft specs, satellite tech, night vision, certain encryption
  • Sharing ITAR data with a foreign national — even inside U.S. — is considered an export
  • Violations: civil fines up to $1.3M per violation, criminal up to $1M + 20 years prison

ITAR / EAR vs. CMMC — How They Interact

CMMC Level 1 (FCI only)

ITAR/EAR are generally NOT triggered at this level. Basic contract delivery data (schedules, invoices, logistics) is FCI, not ITAR-controlled technical data.

CMMC Level 2 (CUI)

ITAR/EAR becomes very relevant. CUI often includes ITAR-controlled technical data. Requires GCC High, strict access controls, potentially DDTC registration.

Does Your Organization Handle ITAR-Controlled Data?

If you manufacture, handle, or discuss technical drawings, specs, or data related to weapons, military platforms, or export-controlled technology, consult a legal/compliance attorney familiar with ITAR before processing that data. Do NOT store ITAR data in commercial M365 without proper controls — Level 2+ conversation required.

Quick Reference

ITAR

State Dept · USML · Defense articles

→ GCC High required

EAR

Commerce Dept · CCL · Dual-use tech

→ GCC or GCC High

FCI (L1)

DoD contract data · Non-classified

→ Commercial M365 ✅

Document ID

CMMC-L1-2026-Q2

Version

1.0 — Final

Classification

CONFIDENTIAL

Prepared By

Security Operations

Implementation Framework

This program aligns with CMMC Level 1 requirements, incorporates SOC 2 Type II and ISO 27001 best practices, and follows NIST Cybersecurity Framework (CSF) controls. All recommendations are based on DoD-provided guidance and industry standards for protecting Federal Contract Information (FCI).

LEGAL NOTICE

This document contains proprietary and confidential information. Unauthorized access, disclosure, reproduction, or distribution is strictly prohibited. All information is provided for authorized personnel only. Violation of these terms may result in legal action. The Senior Official affirming this certification assumes full legal responsibility for the accuracy and completeness of all statements. Falsification or misrepresentation of compliance may result in civil penalties, contract termination, and criminal prosecution.

For Distribution To: Executive Leadership, Security Teams, Legal/Compliance

© 2026 — All Rights Reserved