Sekit CSF · Data Security · Technical

RCF-0099Encryption in transit

Technical controls enforce encryption in transit across all channels

Mapping at a glance

RCF-0099Encryption in transitData Security · Technical

A.5.14Information transferISO/IEC 27001:2022 A.8.20Networks securityISO/IEC 27001:2022 A.8.24Use of cryptographyISO/IEC 27001:2022 PR.DS-02Data-in-transit protectedNIST CSF 2.0 PR.DS-10Data-in-use protectedNIST CSF 2.0

RCF-0099 maps to 5 controls across the published frameworks. Open in the full graph →

Maps to ISO/IEC 27001:2022

Curated mapping with the reasoning, not just the codes.

A.5.14Information transfersupportsSwitching off legacy unencrypted protocols on every service and remote-access path is the technical enforcement A.5.14 needs behind an encryption requirement written on paper.A.8.20Networks securitysupportsEnforcing encrypted protocols everywhere and disabling legacy unencrypted options protects information as it travels across the network, a core objective of A.8.20.A.8.24Use of cryptographysupportsThe technical facet configures every service and remote-access path to enforce encrypted protocols and switch off legacy unencrypted fallbacks.

Maps to NIST CSF 2.0

Curated mapping with the reasoning, not just the codes.

PR.DS-02Data-in-transit protected PR.DS-10Data-in-use protected

Evidence that proves this control

What an auditor, or Sekit's evidence engine, asks for.

Encryption standards evidence

The proof that sensitive data is encrypted when stored (databases, storage) and when transmitted (encrypted connections).

From the Sekit evidence catalog

This topic through the other lenses

All Data Security controls

Ask Sekura: “What evidence proves RCF-0099?”

Also via MCP, free with account