Blog

Cybersecurity Tools Are Not Enough. Contractors Now Have to Prove Compliance

Cybersecurity compliance is increasingly becoming an evidence problem because federal contractors are expected to demonstrate more than the existence of policies and security tools. The Justice Department’s recent $13 million settlement with defense and aerospace contractors ILC Dover and ILC Astrospace illustrates how significantly those expectations have changed. The settlement involved allegations tied to contracts with the Department of the Army, Missile Defense Agency and NASA, and DOJ described deficiencies spanning cloud infrastructure, documentation, technical controls, remediation planning and cybersecurity assessments. The allegations were resolved through settlement without a determination of liability, but the broader lesson for organizations handling government information is difficult to ignore: cybersecurity representations increasingly need technical evidence behind them.

The allegations were not centered on one spectacular breach or an adversary defeating sophisticated encryption. DOJ alleged that controlled unclassified information was stored through a third-party cloud provider without ensuring the required security conditions were met, that system security plans were not adequately maintained and that required NIST controls had not been fully implemented. The government also alleged deficiencies involving plans of action and milestones and cybersecurity assessments that were not current or properly submitted. Those issues demonstrate how cybersecurity exposure can emerge from the gap between what an organization believes its environment looks like, what its documentation says and what is actually operating inside the infrastructure.

For federal contractors, that distinction increasingly carries legal, financial and operational significance. Cybersecurity requirements are embedded into contracts because the government relies on contractors to protect sensitive information across environments the government does not directly operate. When payment, eligibility or contractual obligations depend on cybersecurity representations, compliance cannot remain isolated within the information technology department. Technical teams, leadership, contracts professionals and legal counsel increasingly need a common understanding of what the infrastructure actually contains and whether it matches the representations being made externally.

The Real Risk Is the Gap Between Policy and Reality

Security programs frequently begin with policies that describe how systems should be configured, which safeguards should be implemented and what standards vendors are expected to meet. Those documents provide an essential framework, but their accuracy can erode as the underlying technology changes. Applications migrate to cloud environments, vendors are added, certificates expire, software is upgraded and temporary configurations become permanent without necessarily being reflected in compliance documentation. Over time, an organization can find itself maintaining policies that accurately describe the environment it intended to build rather than the environment it currently operates.

The DOJ allegations demonstrate why that gap matters. System security plans are expected to describe system boundaries, operating environments, connections and how required safeguards are implemented. If those documents fall behind the technology, leadership may no longer have a reliable picture of whether the organization is operating within its contractual obligations. The resulting risk is not merely poor documentation because the documents themselves may be relied upon to support assessments, contract representations and decisions involving government information.

Continuous visibility therefore becomes increasingly important to cybersecurity governance. Organizations need mechanisms for understanding what systems exist, which vendors interact with them and whether important security configurations remain consistent with established requirements. Point-in-time assessments remain valuable, but they become less reliable when rapidly changing infrastructure is not continuously reconciled against the policies describing it. The objective is not more paperwork; it is greater confidence that the paperwork remains connected to technical reality.

Third-Party Infrastructure Is Still Your Compliance Problem

One of the most consequential allegations involved a third-party cloud provider used to store controlled unclassified information. DOJ alleged that the contractors did not ensure the provider met required security conditions equivalent to the FedRAMP Moderate baseline and applicable Department of Defense requirements. That allegation reflects a broader challenge because modern infrastructure increasingly extends through cloud platforms, managed services, software vendors, identity providers and other technology partners. Organizations may not directly operate those environments, but they can remain responsible for understanding how sensitive information is handled within them.

Outsourcing technology therefore does not automatically outsource the associated security obligation. A contractor needs to understand which information a provider receives, what technical requirements apply and whether the vendor relationship remains consistent with contractual commitments. Vendor certifications and contractual assurances are important pieces of that process, but they have to correspond with how the service is actually configured and used. A provider that is capable of meeting a requirement does not necessarily mean every implementation automatically satisfies it.

The same dependency problem will become more visible during post-quantum migration. Organizations may understand cryptography deployed within internally managed applications while depending on cloud platforms or third-party products that control algorithms, certificates or key-management processes elsewhere in the environment. A contractor’s migration readiness can therefore become constrained by providers whose cryptographic architecture it does not directly control. Vendor visibility will increasingly become part of cryptographic readiness for the same reason it is already part of cybersecurity compliance.

NIST Controls Have to Exist Beyond the Checklist

The settlement also involved allegations that cybersecurity controls required under NIST SP 800-171 and NIST SP 800-53 had not been fully implemented. These frameworks address safeguards spanning access control, authentication, configuration management, incident response and other aspects of system security. Mapping those requirements into policies is necessary, but a documented control does not provide meaningful protection unless it exists and operates in the technical environment. The difference between describing a control and implementing it is increasingly where compliance risk can emerge.

That problem becomes more difficult because infrastructure does not remain static between assessments. A control confirmed during one evaluation can later be affected by a new application, vendor integration, configuration change or infrastructure upgrade. An organization that treats compliance as an annual documentation exercise may therefore miss changes that materially affect the environment described in its assessment. More continuous technical evidence can help organizations understand whether required safeguards remain in place as infrastructure evolves.

This moves cybersecurity compliance closer to continuous assurance. Rather than asking only whether a control existed during the last assessment, organizations increasingly need confidence that their current technical environment still supports the representation being made. Configuration data, vulnerability information, cryptographic inventories, access records and other technical evidence can contribute to that understanding. The stronger the connection between policy and operational data, the less dependent the organization becomes on assumptions about how its infrastructure behaves.

Remediation Has to Be Managed as an Operating Process

DOJ also alleged deficiencies involving plans of action and milestones, commonly known as POA&Ms. These plans document identified deficiencies, corrective actions, responsible owners and timelines for remediation, making them more than administrative paperwork. They represent an organization’s ability to acknowledge security weaknesses and demonstrate that those weaknesses are being addressed through a managed process. A vulnerability that is known but neither tracked nor remediated can become both a technical and governance problem.

Identifying a weakness is only the beginning of remediation because organizations still need to understand what depends on the affected system. A security change can influence applications, vendor integrations, certificates or other infrastructure in ways that are not immediately obvious. Organizations therefore need enough visibility to prioritize remediation without creating avoidable disruption elsewhere. That same principle will become central to post-quantum migration because vulnerable cryptography will not be replaced everywhere simultaneously.

Cryptographic transition plans will require organizations to identify exposure, prioritize systems, coordinate with vendors and demonstrate how remaining risk is being managed while migration continues. Discovery and lifecycle management therefore support more than technical modernization. They can also provide operational structure around the process of identifying weaknesses, understanding dependencies and moving those weaknesses toward remediation. The ability to show progress over time will become increasingly valuable as security requirements continue evolving.

Cybersecurity Assessments Are Becoming Representations

Another key allegation involved assessments that were not current or had not been submitted as required. This reinforces the idea that cybersecurity assessments are no longer merely internal diagnostic exercises because they can become formal representations of an organization’s security posture. When those representations affect eligibility, contractual performance or government decision-making, their accuracy becomes an executive concern rather than an isolated technical issue. Leadership needs confidence that the information submitted externally reflects the environment used to perform federal work.

That requires closer coordination between technical and nontechnical functions. Security teams understand how infrastructure is configured and where important vulnerabilities exist, while contracts and legal teams understand what the organization has committed to provide. Neither perspective is sufficient by itself when technical conditions are being translated into formal government representations. The organization needs a process for reconciling the two before those representations are made.

This challenge becomes even more important as requirements evolve over time. A contractor can accurately document an environment during one assessment and later become inaccurate because vendors, applications or security standards have changed. Compliance therefore cannot be treated as a one-time certification followed by years of assumption. It increasingly has to function as an operating discipline that follows the infrastructure as it changes.

Post-Quantum Migration Will Increase the Evidence Burden

Federal cybersecurity is entering another significant transition as agencies prepare for post-quantum cryptography. NIST has standardized initial post-quantum algorithms and federal migration planning increasingly requires organizations to identify where quantum-vulnerable cryptography exists. That work will create a new evidence challenge because organizations need more than a written statement saying they intend to migrate. They need enough technical visibility to understand which systems, vendors and cryptographic dependencies are actually affected.

Organizations will increasingly need to know which algorithms are deployed, which certificates depend on them, where keys are managed and which applications or third-party products control cryptographic functions. They will also need to understand which systems can transition through software, which require vendor coordination and which may eventually involve hardware changes. Without that inventory, a post-quantum migration plan can become a policy describing an environment the organization has not fully mapped.

This is why cryptographic discovery increasingly belongs in broader cybersecurity governance. Organizations cannot accurately represent migration readiness if they cannot identify the cryptography already operating across their environment. The transition also reinforces the importance of crypto-agility because the first generation of PQC standards will not be the final cryptographic change organizations experience. Security infrastructure needs mechanisms for managing algorithms, keys and policies as requirements continue evolving.

Compliance Is Becoming an Infrastructure Discipline

The larger lesson from the settlement is not that contractors need more paperwork. It is that documentation, technical implementation and government-facing representations increasingly need to describe the same operating environment. Achieving that alignment requires visibility into where sensitive information resides, which vendors participate in the environment and whether implemented controls continue satisfying contractual requirements. It also requires evidence that can support conclusions reflected in assessments and certifications.

This shifts compliance closer to security architecture because technical systems increasingly provide the information needed to support compliance decisions. Organizations that understand their infrastructure continuously are better positioned to detect when a policy, assessment or vendor arrangement no longer reflects reality. That does not eliminate the need for legal analysis or formal compliance processes, but it gives those functions a stronger factual foundation. Technical visibility and governance can therefore become part of the organization’s broader compliance capability.

The strongest cybersecurity programs will increasingly ask two related questions. The first is whether required policies and documentation exist, while the second is whether those documents still accurately describe the infrastructure underneath them. As government security expectations become more sophisticated, organizations that can answer both questions with evidence will be better positioned than those relying primarily on point-in-time representations.

Where QVH Fits

QVH is developing security infrastructure around the visibility and cryptographic governance required as organizations operate increasingly dynamic security environments. Thymos is designed for cryptographic discovery, helping organizations identify vulnerable algorithms, certificates, keys and dependencies across client environments. That visibility can support the broader challenge of understanding what cryptographic infrastructure actually exists before organizations make representations about migration readiness or begin significant security changes. The product does not replace formal compliance assessments, but it can provide technical visibility into a layer of infrastructure that organizations increasingly need to understand.

Enqrypta is designed around key management, cryptographic lifecycle management, policy enforcement, integration, crypto-agility and audit visibility. Those capabilities are intended to provide greater control over how cryptographic security is managed as requirements change across existing infrastructure. As organizations move into environments where conventional and post-quantum cryptography may coexist, lifecycle and policy visibility become increasingly important to understanding what protections are active and how those protections are changing.

Neither Thymos nor Enqrypta replaces the contractual, legal or compliance processes required of federal contractors. Their relevance sits at the technical layer underneath those processes by helping organizations understand and manage cryptographic infrastructure more deliberately. That distinction will matter increasingly as contractors are expected to support cybersecurity representations with evidence derived from the environment itself.

The $13 million settlement reinforces a principle that extends well beyond one case. Policies need to describe what organizations intend to do, implementation needs to reflect those policies and evidence needs to demonstrate what is actually occurring. As cybersecurity and post-quantum requirements continue evolving, the organizations best positioned to manage that transition will be those that can keep those three layers aligned.

Sources

U.S. Department of Justice, “Defense and Aerospace Contractors ILC Dover and ILC Astrospace Agree to Pay $13M to Resolve Cybersecurity Fraud Allegations,” November 3, 2026.
https://www.justice.gov/opa/pr/defense-and-aerospace-contractors-ilc-dover-and-ilc-astrospace-agree-pay-13m-resolve

Steptoe, “The Cost of Cyber Noncompliance: $13 Million Record-Breaking False Claims Act Settlement Highlights Contractors’ Increasing Cybersecurity Risks.”
https://www.steptoe.com/en/news-publications/the-cost-of-cyber-noncompliance-dollar13-million-record-breaking-false-claims-act-settlement-highlights-contractors-increasing-cybersecurity-risks.html

Quantum Vision Holdings, “Technology.”
https://www.qvhinc.com/technology

Forward Looking Statement

This article contains forward-looking information within the meaning of applicable Canadian securities laws, including statements regarding the development of post quantum security infrastructure, anticipated industry migration toward post quantum cryptography, and the potential impact of evolving computational capabilities on cybersecurity frameworks.

Forward-looking information reflects management’s current expectations, estimates, projections, and assumptions as of the date of publication and is subject to known and unknown risks and uncertainties that could cause actual results to differ materially from those expressed or implied. Such risks include, but are not limited to, technological development risks, regulatory developments, adoption timelines for post-quantum standards, competitive factors, supply chain considerations, capital requirements, and general economic conditions.

Readers are cautioned not to place undue reliance on forward-looking information. Quantum Vision Holdings undertakes no obligation to update or revise forward looking information except as required by applicable securities laws.

more news

Quantum technology news you don't want to miss.

Content

Home

Company

Platform

Technology

Industries

News & Insights

Contact

Legal

Privacy Policy

Disclaimer

Terms of Use

Contact

Mail

info@qvhinc.com

Address

Quantum Vision Holdings Inc.

36 Toronto Street, Suite 701,

Toronto, ON M5C 2C5 Canada

Corporate Entities Established in: 

United States

© 2026 Quantum Vision Holdings Inc. All Rights Reserved.

Quantum technology news you don't want to miss.

Content

Home

Company

Platform

Technology

Industries

News & Insights

Contact

Legal

Privacy Policy

Disclaimer

Terms of Use

Contact

Mail

info@qvhinc.com

Address

Quantum Vision Holdings Inc.

36 Toronto Street, Suite 701,

Toronto, ON M5C 2C5 Canada

Corporate Entities Established in:  United States

© 2026 Quantum Vision Holdings Inc. All Rights Reserved.

Quantum technology news you don't want to miss.

Content

Home

Company

Platform

Technology

Industries

News & Insights

Contact

Legal

Privacy Policy

Disclaimer

Terms of Use

Contact

Mail

info@qvhinc.com

Address

Quantum Vision Holdings Inc.

36 Toronto Street, Suite 701,

Toronto, ON M5C 2C5 Canada

Corporate Entities Established in: 

United States

© 2026 Quantum Vision Holdings Inc. All Rights Reserved.