
Why federal cybersecurity requirements deserve attention long before project handoff
Imagine completing years of successful building automation projects at military installations, only to receive a new request from a prime contractor: Provide documentation demonstrating that your systems meet the project’s cybersecurity requirements.
At first glance, it might look like another questionnaire. But the information requested could involve security plans, control assessments, documented procedures, and evidence that specific protections have been implemented. Suddenly, a routine administrative request becomes a much larger conversation about contractual responsibility.
For systems integrators working on federal facilities, that distinction matters. A recent $13 million settlement involving a defense and an aerospace contractor illustrates why cybersecurity commitments must be supported by more than assurances.
What Happened in the $13 Million Cybersecurity Settlement?
On November 3, 2026, the U.S. Department of Justice announced that ILC Dover LP and ILC Astrospace LLC had agreed to pay $13 million to resolve allegations under the False Claims Act involving cybersecurity requirements in federal contracts.
The contracts involved the Department of the Army, the Missile Defense Agency, and NASA. According to the DOJ, the allegations covered activities between January 2018 and October 2024 and included several areas of cybersecurity compliance:
- Incomplete cybersecurity controls: Alleged failures to fully implement applicable requirements from NIST Special Publications 800-171 and 800-53.
- Insufficient security documentation: Alleged failures to develop, maintain, and update required system security plans.
- Unresolved deficiencies: Alleged failures to maintain appropriate plans of action and milestones for correcting security weaknesses.
- Assessment shortcomings: Alleged failures to submit current or properly supported cybersecurity assessments.
- Third-party cloud security concerns: Allegations involving the handling of controlled unclassified information through a cloud service provider without ensuring applicable security requirements were met.
The settlement resolved allegations rather than establishing liability. The DOJ explicitly stated that there had been no determination of liability.
Although this case concerned defense and aerospace contractors rather than a building automation installation, the underlying lesson is relevant to organizations that perform work under federal contracts: cybersecurity obligations must be understood, implemented, and documented according to the requirements that apply.
Why Building Automation Integrators Should Pay Attention
Building automation systems are increasingly connected to broader networks and operational infrastructure. Controllers, supervisory systems, workstations, remote connections, and the people who configure and maintain them can all become part of a project’s cybersecurity discussion.
For an integrator, the challenge is not necessarily a lack of concern for security. It may be that cybersecurity responsibilities have historically been handled informally or divided among several organizations.
The facility owner may establish security requirements. A prime contractor may be responsible for contractual compliance. The systems integrator may install and configure equipment, while another organization manages network infrastructure or ongoing security operations.
These arrangements can work, but they also create opportunities for confusion. Who is responsible for documenting a particular control? Who verifies that it was implemented? Who maintains the evidence after commissioning?
Those questions are especially important when a new project introduces requirements that were not requested on previous jobs.
Fred Gordy on What Integrators Need to Know
Fred Gordy, Senior Vice President of Secure Connected Solutions at KMC Controls, offers this perspective:
If you’ve worked on military bases for years without being asked to provide cybersecurity documentation, you may be wondering, “Why now? I’ve never had to do this before.” The requirements depend on the contract, but government agencies and prime contractors are paying closer attention to cybersecurity obligations and the evidence supporting compliance. The recent $13 million settlement involving ILC Dover and ILC Astrospace is a reminder of the potential consequences when contractual requirements are not met. The settlement resolved allegations without a determination of liability.
For systems integrators, this is a reality now, even if it has never come up on a previous project. What looks like a questionnaire may actually be a request for a series of documents and evidence showing how the applicable requirements were implemented. It takes more than checking boxes or stating that the system is secure.
My advice is to review the contract requirements early, understand who is responsible for each deliverable, document deficiencies, and verify the controls before handoff. If you commit to delivering cybersecurity, be prepared to show the evidence.
Fred’s advice points to a practical distinction: implementing cybersecurity measures and demonstrating contractual compliance are related responsibilities, but they are not interchangeable.
Cybersecurity Documentation Is Part of the Work
A secure configuration is important, but a contractor may also need records that establish what was required, what was implemented, and how compliance was assessed.
Depending on the contract and the systems involved, that evidence might include security plans, configuration records, control assessments, documented deficiencies, corrective-action plans, or acceptance documentation.
Not every federal project requires the same materials. Applicability depends on the contract, the type of information and systems involved, and the responsibilities assigned to each organization.
This is why reviewing cybersecurity requirements at the beginning of a project is considerably more useful than discovering them during final commissioning.
It also helps protect working relationships. When owners, prime contractors, IT teams, and integrators agree on responsibilities early, they are better positioned to address gaps before those gaps become disputes over deliverables.
Five Questions to Ask Before Your Next Federal BAS Project
-
-
- Which cybersecurity requirements apply? Review the contract, referenced standards, and applicable flow-down requirements rather than assuming the obligations match previous projects.
- Who owns each responsibility? Clarify which organization will implement, assess, document, approve, and maintain each required control.
- What evidence will be requested? Determine which plans, assessments, records, and other deliverables are expected, and in what format.
- How will deficiencies be handled? Establish a process for recording gaps, assigning corrective actions, and communicating unresolved items.
- What must be verified before handoff? Include required cybersecurity verification and documentation in the commissioning and acceptance process.
-
These questions do not replace a formal compliance assessment. They do, however, help project teams recognize where cybersecurity expectations intersect with their actual scope of work.
Building Security Into the Project Lifecycle
For building automation professionals, cybersecurity should be part of the conversation from design and procurement through installation, commissioning, and ongoing maintenance.
That includes understanding how building controls connect to other systems, identifying who can access them, coordinating with IT and security stakeholders, and maintaining the documentation required by the project.
At KMC Controls, we recognize that systems integrators are being asked to navigate increasingly complex technical and contractual expectations. Our approach to secure connected solutions emphasizes practical coordination among the people, systems, and processes responsible for building operations.
The ILC Dover and ILC Astrospace settlement is not evidence that building automation integrators face identical requirements or liability. It is a useful reminder that federal cybersecurity commitments carry responsibilities that deserve careful attention.
For integrators, the most productive response is not to assume every project requires the same level of documentation. It is to ask the right questions early, establish clear accountability, and ensure that cybersecurity claims are supported by verifiable work.
Because when someone asks whether a system meets its cybersecurity requirements, the answer may need to come with evidence.
Source: U.S. Department of Justice announcement, November 3, 2026
This article provides general cybersecurity and contractual awareness information, not legal advice. Requirements vary by contract and system scope.
