What evidence do auditors commonly ask for on STA-09 Service Bill of Material (BOM)?

Documented process for creating and maintaining the service bill of material; Current bill of material listing components, sub-services and suppliers behind the service; Software bill of material files, for example SPDX or CycloneDX, where software components are included; Review records showing annual and change-driven updates; Approval of the process by management.

What is the most common gap auditors find on STA-09?

Bill of material produced once for a customer request and never updated

CSA CCM v4.1 · STA - Supply Chain Management, Transparency, and Accountability

`STA-09` Service Bill of Material (BOM)

The organisation defines, operates and enforces a process for producing a bill of material that describes the supply chain behind its service, and revisits that bill of material every year at minimum or after significant change.

Source: CSA CCM v4.1, STA-09. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CSA CCM v4.1 in the compliance library.

Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.

artefacts

held by a system

at each review

hard

to go live

Document repository

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

Review records showing annual and change-driven updates · Document repository
Approval of the process by management · Document repository

governing documentDocuments that govern the control

Documented process for creating and maintaining the service bill of material · Document repository
Current bill of material listing components, sub-services and suppliers behind the service · Vendor register / contract repository
Software bill of material files, for example SPDX or CycloneDX, where software components are included · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Bill of material produced once for a customer request and never updated
Covers software libraries only and omits hosting and sub-service providers
No enforcement, so new components enter the service without being added

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

STA-08 Supply Chain Inventory · STA-10 Supply Chain Risk Management