Trust Center Sign in
Sign inContact us
Human-led security service

Software Supply Chain Security

Evaluate integrity and evidence across source, dependencies, build, release, and response.

What we evaluate

Scope the decision before testing the control.

Evaluate integrity and evidence across source, dependencies, build, release, and response. Scope, access, evidence sources, and safety conditions are agreed before work begins.

01

Authorize

Confirm objectives, owners, scope, access, and stop conditions in writing.

02

Evaluate

Gather and test evidence using practices appropriate to the agreed environment.

03

Validate

Review observations, uncertainty, business context, and practical remediation priorities.

04

Brief

Deliver decision-ready findings, owners, dependencies, and recommended next actions.

What you receive

Evidence your team can act on.

Deliverable

Repository and pipeline evidence

Documented for decision-making, ownership, and follow-through.

Deliverable

dependency and SBOM practices

Documented for decision-making, ownership, and follow-through.

Deliverable

provenance

Documented for decision-making, ownership, and follow-through.

Deliverable

signing

Documented for decision-making, ownership, and follow-through.

Deliverable

access and incident readiness

Documented for decision-making, ownership, and follow-through.

Standards-informed approach

Recognized practices, applied to the engagement.

References guide the method and evidence boundary. They do not make this engagement an accredited audit, certification, legal opinion, or formal PCI validation.

Reference

NIST SP 800-218 and SP 800-161

Used to structure applicable scope, evidence, and recommendations—not to assert certification or compliance.

Reference

OWASP SAMM and SCVS guidance

Used to structure applicable scope, evidence, and recommendations—not to assert certification or compliance.

Reference

SLSA and OpenSSF as supporting practices

Used to structure applicable scope, evidence, and recommendations—not to assert certification or compliance.

Reference

PCI Secure Software conditionally

Used to structure applicable scope, evidence, and recommendations—not to assert certification or compliance.

Reference

ISO/IEC 27034

Used to structure applicable scope, evidence, and recommendations—not to assert certification or compliance.

Customer-authorized by design

Start with the outcome and scope.

Our services are human-led, customer-authorized engagements. The Spacetime platform remains purely defensive.

Assess the software supply chain