Skip to main content
MuonPartners
Services
Architecture

Solution design and technology roadmapping

Solution AssessmentTechnology RoadmapsIntegration DesignSolution ArchitectureTechnical Design
Cyber Security

Security assessments, IAM, and compliance

AssessmentsIAMComplianceSecurity BaselineCyber Innovation
Network and Platform

Network architecture and cloud platforms

Network DesignCloud StrategyModernisation
Enterprise Architecture

Business-technology alignment

Business AlignmentPortfolio AnalysisGovernance
View all services
ProjectsCase StudiesInsightsToolsAbout
Contact Us

Services

Architecture
Solution AssessmentTechnology RoadmapsIntegration DesignSolution ArchitectureTechnical Design
Cyber Security
AssessmentsIAMComplianceSecurity BaselineCyber Innovation
Network and Platform
Network DesignCloud StrategyModernisation
Enterprise Architecture
Business AlignmentPortfolio AnalysisGovernance
ProjectsCase StudiesInsightsToolsAboutContact
Get in Touch
MuonPartners

Strategic technology consulting for Australian organisations navigating complexity.

Services

  • Architecture
  • Cyber Security
  • Network and Platform
  • Enterprise Architecture

Company

  • About
  • Products
  • Frameworks
  • Cross-Framework Mapping
  • Projects
  • Case Studies
  • Insights
  • Contact

Contact

  • [email protected]
  • Australia
  • LinkedIn

© 2026 Muon Partners. All rights reserved.

ABN 50 669 022 315 · A Muon Group company.

Privacy PolicyTerms of Service
  1. Frameworks
  2. >C2M2
  3. >Cybersecurity Architecture
  4. >Cybersecurity Architecture - Objective 4
  5. >C2M2-ARCHITECTURE-4B
C2M2-ARCHITECTURE-4BActive

The selection of procured software for deployment on higher priority assets includes consideration of the vendor’s secure software development practices

Statement

The selection of procured software for deployment on higher priority assets includes consideration of the vendor’s secure software development practices

Location

Domain
Cybersecurity Architecture
Objective
Cybersecurity Architecture - Objective 4

Practice Details

Identifier
C2M2-ARCHITECTURE-4B
Domain
Cybersecurity Architecture
Objective
Objective 4
Maturity Level
MIL-2

Help Text

The organization may enforce secure software development practices with vendors through various means such as contractual requirements and technical testing of vendor code. The organization may specify secure design and coding practices from vendors such as those identified in established standards including the NIST Secure Software Development Framework (SSDF), Building Security In Maturity Model (BSIMM), and Open Web Application Security Project (OWASP). This can be done by observing the behavior of the application and inferring the vendor’s coding practices, or by running some tests to uncover insecure practices such as buffer overflow, SQL injection, and poor authentication. Beyond that, the cybersecurity architecture can facilitate the integration and interoperability of procured system components (for example, by providing secure interfaces to third-party software). Additional consideration should be given to high priority suppliers (THIRD-PARTIES-1c) because they supply, maintain, or operate critical software components that are essential to the operation of the function. The definition of a critical software component may vary widely depending on industry or critical infrastructure sector, and may be informed by commonly-used frameworks or control sets. For example NIST provides a definition of critical software under Executive Order 14028 that some organizations may be required to adopt. This activity is related to the cybersecurity architecture activities associated with selecting vendors based on their secure software development practices (THIRD-PARTIES-2h and ARCHITECTURE-4e).

Related Practices · Input From: Implementing ASSET-1c provides input that may be useful for implementing this practice. · Progression: This practice is part of a practice progression. Practice progressions are groups of related practices that represent increasingly complete or more advanced implementations of an activity. The practices in this progression include: ARCHITECTURE-4b, ARCHITECTURE-4e, ARCHITECTURE-4g, ARCHITECTURE-4h, ARCHITECTURE-5h.

AESCSF
AESCSF-ARCHITECTURE-4bequivalentvia derived-shared-practice-structure
View in graphReport an issue
← Back to Cybersecurity Architecture - Objective 4
Cybersecurity Architecture - Objective 48 controls
C2M2-ARCHITECTURE-4ASoftware developed in-house for deployment on higher priority assets is developed using secure software development practicesC2M2-ARCHITECTURE-4BThe selection of procured software for deployment on higher priority assets includes consideration of the vendor’s secure software development practicesC2M2-ARCHITECTURE-4CSecure software configurations are required as part of the software deployment process for both procured software and software developed in-houseC2M2-ARCHITECTURE-4DAll software developed in-house is developed using secure software development practicesC2M2-ARCHITECTURE-4EThe selection of all procured software includes consideration of the vendor’s secure software development practicesC2M2-ARCHITECTURE-4FThe architecture review process evaluates the security of new and revised applications prior to deploymentC2M2-ARCHITECTURE-4GThe authenticity of all software and firmware is validated prior to deploymentC2M2-ARCHITECTURE-4HSecurity testing (for example, static testing, dynamic testing, fuzz testing, penetration testing) is performed for in-house-developed and in-house-tailored applications periodically and according to defined triggers, such as system changes and external events