previous: Secure Remote
Signer Alternatives | Contents page | next: Document
Unsecured Channels
Communicate Securely
BSSC Node Operation - Audit Framework
Domain: 4: Security and Access Control |
Level: MUST | Type: Preventive
Statement of Requirement:
Node Operators MUST use appropriately secured communication methods
that adhere to industry-standard encryption protocols.
See it in the specification
Purpose
Protect data from unauthorized access or modification
Audit Procedures
Verify that
the communication policy defines approved methods with encryption
standards for all categories of communication (client, internal, vendor,
incident comms), especially fallback channels
secure communication is enforced via technical controls (TLS 1.2+
required, DLP) as well as policy
no deprecated protocols are in use such as SSL 3.0, TLS 1.0/1.1,
RC4, unencrypted FTP, HTTP-only portals.
Key Evidence
Interviews with personnel
Communication security policy with approved tools and encryption
requirements
Email security configuration (MTA-STS, DMARC, STARTTLS enforcement,
GPG/PGP)
SSL/TLS scan reports confirming no deprecated protocols
DLP or endpoint management policies
All certificates are up to date.
All messaging apps used support end-to-end encryption
Communication Tools policy
Communication channels policy
Device Management settings
Communications policies in Incident Response and Disaster Response
plans.
Success Criteria
All communication methods use industry-standard encryption (e.g. TLS
1.2)
The communication policy exists and is followed; no deprecated
protocols are in use
Failure Criteria
Any of these circumstances is likely to mean the Requirement is not
met.
Unencrypted or deprecated communication methods are in use
(plaintext email, SMS for sensitive data, HTTP-only)
There is no communication policy
Tool selection is ad hoc, with wide discretion left to individuals
who do not have strong knowledge of Operational Security
requirements
Common Failure Patterns
Primary tools secure but ad-hoc fallback channels are not
(SMS/personal email during incidents)
Email servers support TLS but don't enforce it; no MTA-STS
Messaging platform has encryption capability but workspace config
doesn't enable E2EE
Incident response communications bypass secure channels due to
urgency
Other Relevant Standards
A.5.14, A.8.24, A.8.20, A.8.21
CC6.1, CC6.7, CC6.6
4.2.1, 4.2.2, 2.2.7
PR.DS-02, PR.AC-01, PR.PS-01
previous: Secure Remote
Signer Alternatives | Contents page | next: Document
Unsecured Channels