Knowledge is Power

Sitewide Search

Search Bare Metal Cyber

Search exact control and technique identifiers, Cyber Wiki articles, framework records, playbooks, books, podcasts, Academy courses, and individual lessons.

Cross-Framework Defense Map

SC-17 — Public Key Infrastructure Certificates

Trace this SP 800-53 control to NIST CSF outcomes, CUI requirements, D3FEND defensive techniques, ATT&CK relationships, and related learning resources.

SC — System and Communications Protection · NIST SP 800-53 Release 5.2.0

Open the complete control page →
NIST SP 800-53 control context

SC-17 — Public Key Infrastructure Certificates

Public key infrastructure (PKI) certificates are certificates with visibility external to organizational systems and certificates related to the internal operations of systems, such as application-specific time services. In cryptographic systems with a hierarchical structure, a trust anchor is an authoritative source (i.e., a certificate authority) for which trust is assumed and not derived. A root certificate for a PKI system is an example of a trust anchor. A trust store or certificate store maintains a list of trusted root certificates.

Read the official statement, discussion, parameters, enhancements, and assessment methods →

Outcome layer

NIST CSF 2.0 informative references

These CSF Subcategories list this base control or one of its enhancements in the imported NIST informative reference.

No relationship is present in the currently imported source datasets.
CUI protection layer

NIST SP 800-171 and SP 800-172

SP 800-171 requirements sourcing this control

No relationship is present in the currently imported source datasets.

SP 800-172 enhanced requirements sourcing this control

No relationship is present in the currently imported source datasets.
Defensive engineering layer

MITRE D3FEND techniques

No relationship is present in the currently imported source datasets.
Adversary layer

MITRE ATT&CK relationships

Curated mitigation mappings

No relationship is present in the currently imported source datasets.

Inferred behavior relationships

Experimental: These relationships are inferred through D3FEND and must be validated against architecture, telemetry, and threat context.

No relationship is present in the currently imported source datasets.
Relationship boundaries

Use the map without overclaiming.

A CSF informative reference is not an equivalence statement. A source-control relationship is not proof of implementation. A D3FEND semantic relationship is not a product claim. An inferred ATT&CK link is a hypothesis for engineering analysis.

Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST or MITRE. Informative references and cross-framework relationships support navigation and analysis; they do not establish compliance, applicability, equivalence, control inheritance, or guaranteed mitigation effectiveness.