Security and resilience — Security management systems — Requirements
ISO 28000 specifies requirements for a security management system relevant to organizations and supply chains.
What the authority record establishes
ISO 28000 specifies requirements for a security management system relevant to organizations and supply chains.
Voluntary unless adopted through certification contract or policy
The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.
Why it matters to this market
Technology can support asset, event, risk, incident, and evidence workflows while security objectives and response remain organizational responsibilities.
Affected operating stages
- Context
- Risk Assessment
- Security Controls
- Incident Response
- Monitoring
- Improvement
Capabilities to examine
Multi-Tier Supplier And Facility Mapping
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for multi-tier supplier and facility mapping.
Event Disruption And Incident Monitoring
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for event disruption and incident monitoring.
Shipment Order And Container Tracking
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for shipment order and container tracking.
Cargo Condition Sensor And Chain-Of-Custody Monitoring
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for cargo condition sensor and chain-of-custody monitoring.
Response Workflow Playbooks And Collaboration
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for response workflow playbooks and collaboration.
Performance Analytics Benchmarks And Scorecards
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for performance analytics benchmarks and scorecards.
Affected buyer audiences
- security leaders
- logistics operators
- cargo-risk teams
- auditors
Implementation questions
- Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
- What is binding, what is guidance, and what is a technical or consensus standard?
- Which publication, adoption, effective, application, transition, and enforcement dates differ?
- Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
- How will a source revision affect open work and historical decisions?
Interpretation boundary
A feature list does not establish conformity, cargo security, incident prevention, or loss reduction.