MOSA and Cybersecurity: How Elastic Supports the DoD's Open Modular Approach
Analysis of open interfaces and modularity in the management of defensive data

KEY TAKEAWAYS
- MOSA requires modularity, open interfaces, and separable components for defense acquisition programs.
- Elastic supports MOSA with interfaces based on open standards and easily removable components.
- Elastic's interfaces use open standards such as OpenTelemetry, OCSF, STIX, TAXII, REST, JSON, SAML, OIDC, PKI, and Kubernetes.
- Elastic ensures competitiveness and freedom of exit with open source licenses and public APIs.
- MOSA evaluates five tenets: modularity, openness, scalability, flexibility, and reusability.
The U.S. Department of Defense's Modular and Open Approach
Since 2019, U.S. federal law requires that major defense acquisition programs be designed following the Modular Open Systems Approach (MOSA). This regulation, extended in 2021 to all defense acquisition programs ([10 U.S.C. 4401 through 4403](https://www.cto.mil/sea/mosa/)), mandates the adoption of modular designs, interfaces based on widely supported standards, and separable components that can be added, removed, or replaced during the system's lifecycle.
The Essence of MOSA
It is important to clarify that there is currently no MOSA certification for products. The Department of Defense evaluates MOSA at the program level, and the MOSA Implementation Guidebook advises conducting a business case analysis when applying MOSA requirements to commercial components. If a vendor claims that its product "is MOSA-compliant," it is likely an unfounded statement. It is better to ask if the component will allow the program to meet the principles measured by the Department of Defense, including modularity, openness, scalability, flexibility, and reusability.
The Importance of Removability
The most difficult test of MOSA is also the simplest: can the component be removed? Elastic enters a program as a data and analytics module that integrates with the existing estate and demonstrates its effectiveness on live workloads before any system is retired. Since the instrumentation is based on OpenTelemetry (the CNCF standard), it is possible to replace Elastic later without modifying the systems that produce the data. We are so confident in stating this because easy removal is the true test of openness.
Interfaces Based on Open Standards
the integration points that the program office would designate as primary system interfaces, one by one. Each interface is based on an open standard not controlled by a single vendor:
- Ingest: OpenTelemetry wire protocols with the Elastic Common Schema contributed to OpenTelemetry Semantic Conventions
- Security content: OCSF, STIX, and TAXII interoperability
- Query and management: REST and JSON with published, versioned, and machine-readable API specifications
- Identity: SAML, OIDC, and PKI, including smart card workflows
- Storage: S3 object storage APIs for snapshots and low-cost data tiers
- Orchestration: Kubernetes via Elastic Cloud on Kubernetes
This is what the law means by consensus-based standards. And it can be verified because the specifications are public.
Competition Should Not End With Contract Award
The MOSA exists to keep competition alive throughout the program. For vendors, this means designing products with modularity and interoperability in mind from the start. This can require changes in software engineering processes and architecture strategies.
For end users, MOSA offers greater flexibility and risk reduction. The ability to swap or upgrade components without replacing the entire system allows for greater adaptability to evolving operational needs. Additionally, the use of open standards reduces dependence on specific vendors, improving security and long-term sustainability.
Challenges and Practical Considerations
Despite the benefits, implementing MOSA presents some challenges. One of these is the need for detailed and accurate documentation of system interfaces. This requires a significant investment in time and resources but is essential to ensure that components are truly interchangeable.
Another challenge is managing data rights, particularly when using commercial software components. MOSA requires a thorough data rights analysis (10 U.S.C. 3771), which can be complex and require collaboration between the program and the vendor.
Finally, adopting MOSA may involve a learning curve for the personnel involved. Engineers and analysts need to be trained on MOSA principles and how to apply them in practice. However, once these challenges are overcome, the benefits in terms of flexibility, sustainability, and interoperability are significant.
The Future of MOSA
As MOSA becomes more widespread, new best practices and tools are likely to emerge to facilitate its implementation. For example, more detailed reference architecture models or automated analysis tools may be developed to assess compliance with MOSA principles.
Additionally, MOSA adoption could extend beyond the defense sector, influencing other industries that require complex and sustainable systems. The modular and open approach could become a standard for the acquisition of critical systems in sectors such as aerospace, energy, and infrastructure.
For programs just beginning to explore MOSA, it is advisable to collaborate with experienced vendors and Elastic's public sector team. Together, it is possible to navigate the complexities of MOSA and ensure that systems are designed for long-term success.
Editorial Note and Disclaimer
The guides and content published on GoYou are the result of independent research and analysis activities, for informational, educational, and in-depth purposes.
GoYou does not constitute a journalistic publication or an editorial product pursuant to Law No. 62/2001 and does not provide real-time information.
The GoYou project does not provide professional, technical, legal, or financial advice and disclaims all liability for the misuse of the information published.
In the Crypto sector, every investment involves risks: readers are invited to always inform themselves autonomously before making any decision.
The Broader Context of MOSA
The Department of Defense's Modular Open Systems (MOSA) approach does not operate in a vacuum. It fits into a broader ecosystem of government initiatives aimed at improving the interoperability and sustainability of military systems. Frameworks like FACE (Future Airborne Capability Environment), SOSA (Sensor Open Systems Architecture), and CMOSS (C4ISR/EW Modular Open Suite of Standards) have demonstrated the value of openness in embedded domains, but MOSA extends these principles to data and analytics layers.
For programs working with multiple frameworks, it is essential to understand how MOSA integrates with other standards. For example, while FACE and SOSA focus on avionics and sensors, Elastic's MOSA applies to the data layer and command and control software, offering a complementary solution for analysis and information management.
Implications for Vendors and End Users
The adoption of MOSA has significant implications for software solution vendors and end users in the armed forces. For vendors, it means that products must be designed with a particular focus on modularity and interoperability from the start of the development cycle. This can require changes in software engineering processes and architecture strategies.
For end users, MOSA offers greater flexibility and risk reduction. The ability to replace or upgrade components without having to replace the entire system allows for greater adaptability to evolving operational needs. Additionally, the use of open standards reduces dependence on specific vendors, improving security and long-term sustainability.
Challenges and Practical Considerations
Despite the benefits, implementing MOSA presents some challenges. One of these is the need for detailed and accurate documentation of system interfaces. This requires a significant investment in time and resources but is essential to ensure that components are truly interchangeable.
Another challenge is managing data rights, particularly when using commercial software components. MOSA requires a thorough data rights analysis (10 U.S.C. 3771), which can be complex and require collaboration between the program and the vendor.
Finally, adopting MOSA may involve a learning curve for the personnel involved. Engineers and analysts need to be trained on MOSA principles and how to apply them in practice. However, once these challenges are overcome, the benefits in terms of flexibility, sustainability, and interoperability are significant.
The Future of MOSA
As MOSA becomes more widespread, new best practices and tools are likely to emerge to facilitate its implementation. For example, more detailed reference architecture models or automated analysis tools may be developed to assess compliance with MOSA principles.
Additionally, MOSA adoption could extend beyond the defense sector, influencing other industries that require complex and sustainable systems. The modular and open approach could become a standard for the acquisition of critical systems in sectors such as aerospace, energy, and infrastructure.
For programs that are just beginning to explore MOSA, it is advisable to collaborate with experienced vendors and Elastic's public sector team. Together, it is possible to navigate the complexities of MOSA and ensure that systems are designed for long-term success.
Editorial Note and Disclaimer
The guides and content published on GoYou are the result of independent research and analysis activities, for informational, educational, and in-depth purposes.
GoYou does not constitute a journalistic publication or an editorial product pursuant to Law No. 62/2001 and does not provide real-time information.
The GoYou project does not provide professional, technical, legal, or financial advice and disclaims all liability for the misuse of the information published.
In the Crypto sector, every investment involves risks: readers are invited to always inform themselves autonomously before making any decision.
Source: elastic.co · GoYou.it is not a registered news outlet; all content is for informational and educational purposes.