The acquisition process is the formal method an organisation uses to buy or obtain software, hardware, or services. In security practice, it includes requirements definition, supplier due diligence, contract terms, approval gates, and acceptance criteria that reduce introduced risk before deployment.
What the acquisition process covers
The acquisition process is broader than procurement administration. For security teams, it is the stage where an organisation decides what it will buy, what security requirements must be met before purchase, and which risks are unacceptable before the product or service enters the environment.
That makes the process part of the control plane around third-party and in-house delivery. It is where security requirements are translated into supplier obligations, contract language, evidence requests, and acceptance criteria that can be checked before deployment rather than after incidents or audits.
Why acquisition decisions shape security outcomes
Acquisition is often the first point where risk can be reduced cheaply. If security, privacy, resilience, logging, supportability, and update expectations are not written into the purchase decision, they usually become expensive retrofit work later, or remain unresolved entirely.
Good acquisition decisions also prevent ambiguous ownership. They clarify who is responsible for patching, support, incident notification, secure configuration, data handling, and end-of-life handling, which matters when the purchased product becomes part of a production service chain.
How security requirements fit into acquisition
In practice, the strongest acquisition processes turn security expectations into testable conditions. That can include due diligence on the supplier, review of shared-responsibility boundaries, contractual commitments for vulnerability handling, and acceptance criteria that a system must satisfy before go-live.
For security-aware organisations, acquisition should also account for downstream control compatibility. A purchased system may be technically usable but still create friction with logging, access control, monitoring, patch governance, or resilience targets if those requirements were never defined up front.
That is why the NIST SP 800-53 SA System and Services Acquisition family guide is useful here, because it maps the acquisition stage to concrete security expectations such as contract terms, provider controls, and acceptance evidence.
What good acquisition governance looks like
A mature acquisition process does not treat security as a late-stage review. It establishes security and assurance checkpoints before award, before contract signature, before onboarding, and before acceptance, so that risk decisions are visible and accountable.
It also distinguishes between what the supplier promises and what the organisation can actually verify. A strong process asks for evidence, not just assurances, and requires a clear acceptance decision when a product or service does not meet mandatory requirements.
That discipline aligns well with NIST SP 800-53 Rev 5 Security and Privacy Controls, which gives organisations a control catalogue for acquisition, supplier oversight, and related security responsibilities.
Risk and Threat Considerations
Acquisition is a security choke point because weak supplier selection or weak contract terms can import vulnerabilities, unsupported components, poor logging, or unbounded access paths into the environment. The risk is not only that a product is unsafe, but that the organisation may inherit hidden obligations and weak recovery options after deployment.
Failure mechanism: Security requirements are not written into procurement, supplier due diligence is superficial, or acceptance is based on functionality alone, allowing insecure products, services, or dependencies to enter production with unresolved control gaps.
Impact: Organisations can end up with preventable exposure, slower incident response, weak accountability for remediation, and higher blast radius when a vendor issue, configuration flaw, or service failure affects business operations.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | SA-4 — Acquisition Process | Directly governs security requirements in procurement and supplier selection. |
| SA-9 — External System Services | Covers supplier-provided services and inherited security responsibilities. | |
| SA-3 — System Development Life Cycle | Links acquisition decisions to lifecycle security requirements and assurance gates. | |
| Recommendation — Define security requirements and acceptance criteria before awarding or onboarding the system or service. Specify provider security obligations, monitoring rights, and incident notification terms in the service contract. Embed security checkpoints into the lifecycle so acquisition decisions are verified before deployment. | ||
| CIS Controls v8 | CIS-15 — Service Provider Management | Addresses third-party oversight and contractual security expectations for acquired services. |
| Recommendation — Assess suppliers, formalize security requirements, and track service-provider obligations throughout the relationship. | ||
| ISO/IEC 27001:2022 | A.5.19 — Information security in supplier relationships | Requires security controls for suppliers involved in purchased products and services. |
| Recommendation — Apply supplier security requirements and review them before contracts are approved. | ||
Practitioner Guidance
Why practitioners should care: Acquisition is where many control failures become permanent. If the buying decision does not encode security requirements, later teams inherit the risk with fewer options and less leverage.
Governance implication: Give security, legal, procurement, and the service owner a shared decision point for required controls, mandatory evidence, and go or no-go acceptance criteria before the organisation commits.
Practitioner takeaway: Treat acquisition as an enforceable control gate, not a commercial formality, because the cheapest time to reduce third-party risk is before the contract is signed.
Related resources from NHI Mgmt Group
- What is the impact of connecting fraud prevention to the customer acquisition process instead of treating it as a post-sale control?
- What does the Cisco acquisition of Astrix Security mean for NHI tooling?
- Should IAM teams re-evaluate their NHI tooling choices after a major acquisition?
- Why do NHI programmes need stronger process ownership than many human identity programmes?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org