BSSC Node Operation Standard version 3

BSSC Specification

This Version
https://specs.blockchainssc.org/nos/v3.html
Audit Framework for this version
https://specs.blockchainssc.org/nos/audit-03/
Checklist for this version
https://specs.blockchainssc.org/nos/audit-03/checklist.html
Date
2026-11-17
Editor
Max Courchesne-Mackie (Figment)
Former Editor
John Kemp (BSSC)
Contributors
Joaquim Pedro Antunes (Halborn), Britton Ballard (Figment), Logan Ballinger (Figment), Joe D'Annolfo (Coinbase), Son Dinh (OpenZeppelin), Justing Fang (Halborn), Fly (FlyYouFools), Robert Gallagher (Mastercard), Opal Graham (Coinbase), Sky Gul (Kraken), Joel Kerr (Coinbase), Eric Lau (OpenZeppelin), Eric Meng (Coinbase), Mark Nesbitt (Turnkey), Chaals Nevile (BSSC), Matan Nevo (Fireblocks), Akshar Rawal (Coinbase), Dustin Ray (Anchorage Digital), Noama Samreen (Coinbase), Kishore Suri (Coinbase), Paddy Walsh (Mastercard)
Latest Version URL
https://specs.blockchainssc.org/nos/
Previous Version
https://specs.blockchainssc.org/nos/v2.html

Copyright ©2024-6 Blockchain Security Standards Council (BSSC) Inc. All Rights Reserved.

Summary

Node operation failures can be very expensive and very visible. As well as node operators losing their stakes, they can cause significant loss of customer funds, as well as serious problems or even failure for the network as a whole.

The Node Operation Standard (NOS) is a set of requirements that defines the baseline security criteria expected of a blockchain node operator with the goal of enabling clients and third-parties to perform safe and confident integrations. Certification against the NOS signifies that a node operator adheres to industry best practices and has had their security practices rigorously tested and measured.

The goals of the NOS are as follows:

  1. Present a clear set of security requirements for node operators that ensure a robust level of safety in fulfilling node responsibilities.
  2. Establish a set of requirements that are common across multiple blockchain ecosystems and protocols.
  3. Boost the confidence of consumer and business clients in engaging with node operators for blockchain-related services.
  4. Establish a certification process for the Node Operation Standard that is consistent with many existing network and security audit practices.
  5. Define a process for recurring re-certification which can be achieved through self-attestation as long as certain conditions did not change.

Table of Contents

Conformance

The key terms "MUST", "MUST NOT", "SHOULD", and "MAY" in this document MUST be interpreted as described in [RFC2119] as modified by [RFC8174] when they appear in all capitals, as shown here.

Where a requirement refers to document, the relevant documentation MUST be available to all customers of the Nde Operator and SHOULD be available publicly without restriction.

Where a requirement refers to maintain documentation, (in version 2 this was called "provide documentation") auditors MUST review the relevant documentation. Attesting conformance to this specification is an endorsement of the accuracy of such documentation.

Where a requirement refers to equivalent standards or guidelines, attestation of conformance is an explicit endorsement that the relevant specification is an appropriate alternative in the circumstances.

Scope

The controls in this specification have been written broadly to cover a wide variety of different node types.

Some nodes, in particular those that host Oracles and Bridges, can be used by other on-chain nodes, while having additional connections outside the blockchain. Such nodes can face additional threats of manipulation and other vulnerabilities, as they are not governed by the same set of incentives.

Some, but not all, of the additional seecurity requirements that are important for such nodes are covered by the BSSC Smart Contract Security Standard [SCSS].

Future versions of this specification or other work from the BSSC MAY provide additional more specific guidance for these node types.

Taxonomy of Node Types

A full taxonomy of node types is beyond the scope of this document. However, for informational purposes, we offer a categorization of node types as follows:

Consensus Nodes

Nodes that actively participate in the blockchain’s consensus mechanism to propose, validate, or finalize blocks.

This includes:

Full, and Verification Nodes

Nodes that maintain the state of the blockchain by storing either the full or partial blockchain ledger and verifying transactions and blocks.

This includes:

Interoperability and Communication Nodes

Nodes that enable interaction between multiple blockchains or provide off-chain data to the blockchain.

This includes:

Utility Nodes

Nodes that provide auxiliary services such as decentralized storage, data indexing, or serving as gateways to the blockchain network.

This includes:

Requirement Domains

The Node Operation Standard covers the following requirement domains:

Currently these domains only outline the outcomes of the standard, not the specifics of how each requirement would be audited.

0. Basic Security

Security failures that allow malicious actors to compromise a node or a Node Operator pose a financial risk to the users or customers of such nodes, and thus to the reputation of the Node Operator.

This is why Node Operators need basic security hygiene processes in place, as well as meeting requirements more specific to their role as Node Operators.

Manage Key Security
A Node Operator MUST securely manage Keys and Key material in accordance with the requirements in the BSSC Key Management Standard or equivalent standards. [KMS]

Purpose: Provide resilience against key compromise by malicious actors

Key compromise is a common and attack vector for malicious actors, with multiple extremely damaging incidents occurring.

Audit Guidance

Implement Standard Security Practices
A Node Operator MUST follow the guidance in the BSSC General Security and Privacy Guidelines [GSP] or an equivalent standard.

Purpose: Ensure Node Operators understand and implement basic security practices common to IT industry

Audit Guidance

1. Protocol Onboarding

Each Protocol is subtly different, even where the underlying systems are the same (such as for EVM-based blockchains). Failure to account for the individual characteristics of a specific blockchain protocol can introduce exploitable vulnerabilities, or lead to operational errors.

Meeting the requirements in this domain ensures that node operators possess comprehensive technical expertise in any new protocol, including a clear understanding of the operational responsibilities, security considerations, and associated risks involved. Additionally, it ensures that operators understand the maturity of the blockchain project and implement appropriate risk mitigation strategies to ensure a secure and stable deployment.

Risk Assessment

Document Protocol Analysis
Node Operators MUST document their process for protocol selection and risk analysis of a new protocol

Purpose: Demonstrate the Node Operator's risk management approach for Protocols.

Audit Guidance

Monitor Protocol Changes
Node Operators MUST implement a process that continuously monitors changes to the network and adjusts risk accordingly

Purpose: Mitigate the risks entailed by not reacting rapidly to any protocol changes

Audit Guidance

Software Supply Chain

Document Supply Chains
Node Operators MUST maintain documentation of their Software Bill Of Materials, including risk analysis and management for all node-related components.

Purpose: Ensure the Node Operator has sufficient information to effectively monitor the security of their full Software Supply Chain

This requirement includes all autonomous agents the node operator uses.

While the minimum requirement is to document the actual Software the Node Operator uses, best practices include

This helps understand, and thus enables mitigation of, the risk of a supply-chain attack. Extending the documentation to cover dependencies enables independent risk mitigation, beyond that provided by the software supplier directly.

Audit Guidance

Protocol Assessment

Document Protocol Responsibilities
Node Operators MUST document the protocol's operation, the responsibilities they have with respect to the protocol, and MUST maintain documentation identifying the responsible parties for managing those responsibilities

Purpose: Demonstrate the Node Operator understands a Protocol

This is important to demonstrate that the Node Operator actually understands the Protocol, specific risks, and details that are unique to a given protocol, and is aware of and fulfilling their specific responsibilities with respect to each Protocol

Audit Guidance

Test in Controlled Environments
Node Operator MUST conduct pilot testing in a controlled test network environment to validate a protocol's performance, interoperability, and security posture, prior to mainnet deployment

Purpose: Ensure sufficient testing takes place safely before deployment

Best practice is to use official protocol testnets where available and up to date with the protocol.

Audit Guidance

Compliance

Comply with Applicable Regulation
The node operator MUST adhere to applicable anti-money laundering and national security address blacklists, or locally established equivalent standards or guidelines, whenever such measures are available

Purpose: Demonstrate the Node Operator's integrity and understanding of the regulatory environment where they and their customers operate.

Audit Guidance

Cryptographic Agility

Document Protocol Cryptography Algorithms
Node Operators MUST document the cryptographic algorithms employed by the protocol, including signature schemes, hash functions, and key exchange mechanisms.

Purpose: Demonstrate that Operators correctly identify and understand the range of cryptographic tools the Protocol relies on

Audit Guidance

Evaluate Protocol Crypto-agility and Post-quantum plans
Node Operators SHOULD evaluate the protocol's roadmap or capability for transitioning to quantum-resistant cryptography.

Purpose: Demonstrate the operator understands the expected need for Post-Quantum Cryptography, and the likelihood that changing cryptographic algorithms will at some point become necessary

Audit Guidance

2. Network Participation

Validator failures that incur slashing penalties for a Node Operator and their clients are generally on a permanent public record, representing a reputational risk. Decentralization failures in Node Operations can damage the overall safety of a blockchain Protocol, with consequent effects in market perception. The potential for damage can attract malicious actors who seek to profit from destructive behaviour.

This domain's requirements ensure that nodes strictly adhere to established best practices, and network-specific regulations or conventions. It emphasizes proactive measures to prevent issues such as slashing as well as to uphold the overall integrity and reliability of the blockchain network.

Consensus

Follow Protocol Conventions
Nodes MUST perform all standard activities — including attesting, executing, proposing, and any other responsibilities — in strict accordance with the documented best practices of their respective network.

Purpose: Help maintain the network in optimal state, mitigate risks of slashing or other operational failures

Audit Guidance

Follow Protocol Consensus
Nodes MUST remain on the most recent accepted chain

Purpose: Minimize chain forking, and the risk of slashing or operational failures due to following a fork rather than the accepted chain

For nodes that do not produce on-chain attestations (e.g., full nodes, archive nodes), Node Operators SHOULD maintain logs that enable verification of chain-head adherence, such as periodic chain-head comparisons against independent reference sources.

Audit Guidance

Rewards and Slashing

Document Anti-slashing Controls
Node Operators MUST maintain documentation of the controls they follow to prevent slashing or other penalties for non-participation in network duties

Purpose: Mitigate the risk of slashing penalties being applied to the Node Operator, incurring downstream increases in customer costs

See also Document Continuity Process

Audit Guidance

Network Topology

Maintain Boot Peers Lists
The node operator MUST maintain boot peers lists

Purpose: Protect against network fragmentation

Audit Guidance

Configure Discovery Appropriately
Nodes MUST only allow discovery by peers where necessary to support the network.

Purpose: Enable decentralization and permissionless participation, and reduce the attack surface for nodes that do not need to be discoverable.

Audit Guidance

Verify Discovery Configuration
Node Operators MUST review and update the discoverability configuration of all nodes every month.

Purpose: Ensure discoverability configuration matches operational requirements

Audit Guidance

Decentralization

Limit Consensus Power
Node operators MUST limit control of consensus-setting power to support decentralization of the protocol:

Purpose: Protect the network against centralization risks such as "51%" attacks

These thresholds reflect the fact that any entity able to marshall a higher proportion of the network decision-making power can single-handedly force consensus, breaking the fundamental security guarantee of the blockchain.

Audit Guidance

3. Resilience and Performance

Individual nodes failing generally impacts the operators and users of those nodes, however serious cases can impact the overall network as well.

This domain specifies requirements for nodes that enable them to adapt to evolving threats and quickly recover from failures elsewhere in the network, including within the set of nodes managed by a Node Operator. Implementing these requirements can significantly enhance the overall stability and security of the network as well as in their own operation, thereby reinforcing trust among participants.

Client Diversity

Practice Client Diversity
Node operators SHOULD deploy a diverse set of client software implementations where they are available.

Purpose: Support network robustness, and ensure that the Node Operator is not completely compromised by a bug in a single client implementation.

Client diversity is important both to ensure overall network robustness. Operating multiple clients helps to ensure that if a given client has a specific bug the Node Operator is not completely compromised.

Audit Guidance

Balance Client Share
Node Operators SHOULD NOT run any single client software representing more than 2/3 of their overall deployment.

Purpose: Protect Node Operators, and the network, from bugs present in one client.

Running a super-majority of clients that have a specific bug can exacerbate problems caused by that bug, for the Node Operator, and, if the Node Operator's deployment pattern is common, for the network itself.

Audit Guidance

Resilience

Document Continuity Process
Node Operators MUST maintain documentation of their fault-tolerance strategies and continuity and failover procedures.

Purpose: Ensure Node Operations are resilient to failures of individual nodes or clusters of nodes.

It is important that Node Operation is sufficiently resilient to function under sub-optimal conditions, including where a part of the Node Operator's systems fail, as well as external issues.

These processes are necessary to ensure the most seamless transition possible of node operations during downtime events.

A particular risk during failover is that double-signing occurs, leading to slashing. See also Document Anti-slashing Controls, specifically addressing that risk.

Audit Guidance

Document Uptime Monitoring
Node Operators MUST maintain documentation of processes for monitoring node uptime and remediating detected issues.

Purpose: Demonstrate that the Node Operator receives timely notification of issues that affect their uptime, and thus ability to provide a reliable service.

Audit Guidance

Distribute Nodes
Nodes SHOULD be distributed among multiple hosting providers, data centers, and geographic regions.

Purpose: Provide operational continuity when a specific provider, data center, or geographic region has a problem that impacts Nodes.

Problems that Node distribution helps mitigate can include military activity, government-imposed shutdowns, power outages, or commercial decisions by providers to shut down services.

Failure of a substantial proportion of Nodes can do significant damage to a network's throughput, and as a consequence its reputation and liquidity, impacting the network long-term.

Given a trend leading to a small number of large global providers, it is important to consider that many Node Operations may be using the same providers, so a failure in one provider can impact multiple Node Operation providers at the same time, magnifying the impact on the network.

Audit Guidance

Software Updates

Document Recovery Procedures
Node Operators MUST maintain documentation of the procedures they follow for the deployment, recovery, and updating of nodes.

Purpose: Support efficient recovery from node failures

Audit Guidance

Document Procedural Deviations
Node Operators MUST maintain documentation of any deviations from documented procedures for node deployment, recovery, and update.

Purpose: Identify where existing procedures do not meet real needs

Audit Guidance

Document Cryptography Migration Procedures
Node Operators MUST document plans and any procedures for cryptographic migration scenarios, including protocol-level transitions to post-quantum algorithms.

Purpose: Provide transparency into resilience planning

Note that this requirement applies even if the Node Operator has no planning, or their planning is only to copy changes made upstream in software they use.

See also Document Supply Chains

Audit Guidance

Prepare for Cryptography Migration
Node Operators SHOULD maintain operational readiness to adopt updated cryptographic schemes in accordance with protocol governance timelines.

Purpose: Ensure Node Operators can respond to changes in the cryptography environment in a timely manner and not get rekt

Audit Guidance

Node Capacity

Provision Nodes Sufficiently
Node operators MUST provision nodes with sufficient hardware and network resources—including, but not limited to, disk space, disk speed, network speed, and bandwidth—to effectively perform their designated duties.

Purpose: Ensure operations are not interrupted because nodes lack capacity to fulfil their requirements

Audit Guidance

Configure Resilient Nodes
Node Operators MUST maintain documentation of resilience to spikes in activity, with relevant measures assessed and if necessary updated at least annually.

Purpose: Ensure operations are not interrupted because nodes lack capacity to meet requirements at peak demand levels

Network activity can jump significantly due to events such as a "hard fork" or "network upgrade", or a sudden rush. It is important that Nodes have sufficient capacity to manage this heightened activity effectively.

Audit Guidance

4. Security and Access Control

Unauthorized access to the keys that secure nodes continue to be a cause of significant financial losses, alongside insufficiently documented security protocols, or failures to implement those protocols in practice.

This domain defines critical measures to protect nodes from unauthorized access and mitigate potential security threats, both through proactive defense, and logging that supports investigation of incidents to identify necessary improvements.

Access Control

Use Remote Signers
Remote signers SHOULD be employed

Purpose: Eliminate sensitive key material on network-connected nodes.

It is important to consider the network configuration for remote signers. If they are on insecure networks, this can introduce a new vulnerability.

Audit Guidance

Secure Remote Signer Alternatives
Where remote signer support is unavailable, operators MUST implement alternative security controls to safeguard key material.

Purpose: Ensure security of Key material

Audit Guidance

Communicate Securely
Node Operators MUST use appropriately secured communication methods that adhere to industry-standard encryption protocols

Purpose: Protect data from unauthorized access or modification

It is important to consider current industry standards for encryption, as those change over time, and the possibility of "collect for later decryption", in assessing the risk profile for a communication channel

Best practice is to use strong encryption or equivalent measures to mitigate the risk of man-in-the-middle (MITM) and denial-of-service (DoS) attacks for communication channels by default.

Audit Guidance

Document Unsecured Channels
Node Operators MUST maintain documentation of any instance where encryption is not used for information in transit, including a risk assessment.

Purpose: Ensure security is not compromised by unsecured communication channels

Audit Guidance

Restrict Privileged Access
Access to node control planes, logs, and signed Stored Transactions MUST be restricted to authorized parties, by implementing the Principle of Least Privilege.

Purpose: Restrict exposure of operations only allowing access for authorized parties with an operational requirement.

Unauthorized access to signed transactions that are stored, such as exit transactions, can lead to undesired deployment.

Best Practice is to use Role Based Access Control to manage access rights.

Audit Guidance

Minimize Network Exposure
The network exposure of node clients MUST be minimized to include only the services essential for effective network operation

Purpose: Minimize attack surfaces

Audit Guidance

Restrict Agentic Write Access
Node Operators MUST NOT allow autonomous agents such as generative AI tools unmoderated write access to production code

Purpose: Protect against rogue agents causing damage to customers or the Node Operation

At minimum, all updates to production code created by an autonomous agent need to have a human approval before deployment.

Best Practice is to ensure that Autonomous Agents are restricted to a sandboxed parallel version of the code and network, with keys sufficiently isolated and rotated often enough to mitigate the risk of an agent compromising the Node Operation's production code.

See also Test in Controlled Environments

Audit Guidance

Activity Logging

Log Access Events
Node Operators MUST record all access events for the control plane.

This covers both successful and failed attempts to access relevant facilities, logs, software, etc.

Purpose: Ensure that forensic analysis has the broadest feasible range of information to work on.

Audit Guidance

Review Logs
Node Operators MUST review event logs for anomalies at least every 24 hours.

Purpose: detect patterns of anomalous behaviour, that could signal an attack in preparation, or the early stages of an error, enabling proactive interdiction.

Best practice is continuous automated monitoring with Incident Response reporting triggered by anomalies detected, with a monthly manual review of log patterns by a security team including consideration of what is considered anomalous behaviour.

Audit Guidance

Retain Logs
Node logs MUST be retained for a minimum of 90 days, or a longer period where required by applicable regulation or documented retention policies. Security-relevant logs (access events, authentication events, configuration changes) SHOULD be retained for at least 180 days.

Audit Guidance

Aggregate Logs
Node logs SHOULD be aggregated where feasible.

Purpose: Ensure that all logged information is readily available from a single source. This facilitates detecting problems in a timely manner.

Audit Guidance

Do Not Log Sensitive Information
Logs containing sensitive information, such as cryptographic keys or personally identifiable information (PII), MUST be suppressed, sanitized, or otherwise secured to prevent unauthorized access.

Audit Guidance

Use Automated Monitoring
Node Operators SHOULD use automated monitoring systems to detect operational anomalies

Purpose: Provide rapid response to anomalies in operations that can signal an attack or failure in progress

Audit Guidance

Incident Response

Document Incident Response Plans
Node Operators MUST maintain documentation of the Security incident response procedures they follow.

Purpose: Demonstrate the Node Operator's ability to anticipate and respond to threats and adverse circumstances.

Audit Guidance

Follow Incident Response Plans
In the event of a security incident, Node Operators MUST execute documented Incident Response Procedure to ensure node availability and to facilitate a secure and safe return to operations.

Audit Guidance

Provide Rapid Human Response
Node Operators SHOULD ensure that automated incident responses are limited in scope, and that timely human oversight is engaged

Purpose: Manage risk of inappropriate responses impacting overall business

Audit Guidance

5. Transparency

Customers cannot make rational choices about Node Operators without clear and accurate disclosure of relevant operational information. Failure to provide the necessary transaparency can bring significant regulatory pressure, as well as expanded legal risk in the event of anything going wrong.

This domain mandates clear and accessible disclosures regarding operational practices and risk mitigation measures, to minimize the exposure of a Node Operator to risks that are taken by their customers.

Follow Reward Conventions
Nodes that are eligible for rewards MUST receive any form of incentive in accordance with the specific chain’s established protocols.

Purpose: Transparent compliance for payments and incentives received

Audit Guidance

Log Protocol Payments
Node Operators MUST document all rewards or incentives received in a verifiable log.

Purpose: Ensure transparency for payments and incentives

Audit Guidance

Document Insurance
Node Operators MUST document the scope and terms of any insurance coverage they provide. This must specifically detail the protections afforded against losses resulting from each of

Purpose: Help customers understand the level of protection the Node Operation has against undesired and unexpected events.

This requirement ensures transparency, not a mandate for insurance coverage. Where no insurance coverage is provided for one or more loss vectors, documentation MUST clearly state this.

Audit Guidance

Document Exit Procedures
Node Operators MUST document exit procedures including:

Purpose: Ensure that customers can properly understand the implications of ceasing operations with the Node Operator, including costs and relevant timelines.

Documentation of exit procedures and triggers is important to users both at an individual level in making rational choices, and in enabling better assessments of the overall networks that a Node Operator participates in. Reliable and clear documentation can increase user trust, leading to a "virtuous cycle" of improved stability. Likewise, inadequate or unreliable documentation can significantly reduce trust in a given Node Operator or even in the networks where they participate.

Audit Guidance

Document Governance Positions
Node operators participating in protocol governance MUST document governance participation policies including:

Purpose: Provide transparency into Node Operator participation in governance that can impact operations and could give rise to conflicts of interest

Where a Node Operator participates in governance, this can have an impact on the project they govern, but also on the Node Operation itself, potentially heightening e.g. regulatory or market risks. Participation in governance of an external project often heightens the risk of a Conflict of Interest, as well as of "sampling" bias" caused by extensive exposure to particular projects influencing the Node Operation inappropriately.

Audit Guidance

Alignment with other Standards

The Network Participation domain is aligned with other similar node operation standard proposals such as Liquid Collective's Node Operator Risk Standard [NORS], and Lido's Distributed Utilization of Configurations and Knowledge [DUCK]project.

Additionally, some concepts within the Resilience, Performance, and Security and Access Control align with common risk management standards such as [SOC 2] and [ISO 27001].

References

[DUCK]

"Distributed Utilization of Configurations and Knowledge", Lido. https://duck-initiative.gitbook.io/d.u.c.k.-knowledge-base

[ERC-20]

"ERC-20: Token Standard", F. Vogelsteller and V. Buterin, Ethereum Improvement Proposals 2015. https://eips.ethereum.org/EIPS/eip-20

[GSP]

"BSSC General Security and Privacy Guidelines", J. D'Annolfo and J. Kemp eds, BSSC 2025. https://specs.blockchainssc.org/gsp

[ISO 27001]

ISO/IEC 27001 - Information security management systems, ISO. https://www.iso.org/standard/27001

[KMS]

"BSSC Key Management Standard", M. Nesbitt, A. Rawal and J. Kemp eds, BSSC 2025. https://specs.blockchainssc.org/kms

[NORS]

"Node Operator Risk Standard", Liquid Collective. https://docs.nors.global/

[RFC2119]

"Key words for use in RFCs to Indicate Requirement Levels", S. Bradner, IETF 1997. https://www.rfc-editor.org/rfc/rfc2119.html

[RFC8174]

"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", B. Leiba, 2017. https://www.rfc-editor.org/rfc/rfc8174.html

[SCSS]

"BSSC Smart Contract Security Standard", John Neufeld ed., BSSC 2026. https://specs.blockchainssc.org/scs/

[SOC2]

"SOC 2® - SOC for Service Organizations: Trust Services Criteria", AICPA. https://www.aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2

Change History

The following notable changes have been made since version 2 of this specification was published (14 May 2026).

The formatting was expanded, with explanations removed from requirement text, and more explanations added to many requirements.

Requirements added

Requirements Removed

Requirements changed or clarified

The term "provide documentation" used in a number of requirements was changed to "maintain documentation", but the meaning was retained as previously.

This affects the following requirements:

In addition, the following requirements were clarified or adjusted as described:

How to Read This Document

Requirements

The requirements are the core of this document. Each requirement has a standard structure:

As an example:

Communicate Securely
Node Operators MUST use appropriately secured communication methods that adhere to industry-standard encryption protocols

Purpose: Protect data from unauthorized access or modification

It is important to consider current industry standards for encryption, as those change over time, and the possibility of "collect for later decryption", in assessing the risk profile for a communication channel

Best practice is to use strong encryption or equivalent measures to mitigate the risk of man-in-the-middle (MITM) and denial-of-service (DoS) attacks for communication channels by default.

Audit Guidance

has the name "Communicate Securely".

Its stable URL is https://specs.blockchainssc.org/NOS/#req-communicate-securely which points to the requirement in the latest published version of the specification. If it is removed from a future version, it will point to the change history, that explains when and why it was removed

The statement of requirement is

Node Operators MUST use appropriately secured communication methods that adhere to industry-standard encryption protocols.

The rest of the text is explanatory. While it is helpful to some audiences as guidance to understanding what is necessary to meet this requirement, it is not part of the requirement that needs to be met.

The Purpose explains the goal of meeting the requirement. The linked Audit Guidance is the guidance provided in the Audit Framework for how to assess this requirement.

Requirements are grouped into a set of Requirement Domains, and generally into smaller groups within each Requirement Domain, as a convenience. Requirements are not prioritized, as specific priorities will depend substantially on specific implementations and use cases.

Some kinds of link used in this document are identified by specific formatting:

Glossary terms
Terms with a specific meaning defined in the BSSC Glossary appear in Title Case in italic text, and link to that glossary, for example Stored Transactions.
References
Links to external resources appear as follows: [RFC2119], and link to the relevant item in the References section.

Document Status and Feedback

This document is the BSSC Node Operations Standard, version 3, developed by the Technical Working Group of the Blockchain Security Standard Council (BSSC Inc.), as a replacement for the Version 2 Specification.

The BSSC requests feedback on this document, which can be provided through our contact form.

The BSSC may publish a new version of this specification, or another specification, that obsoletes this version, in response to feedback received or other developments in the ecosystem.

Disclaimer of Warranty and Liability

NO WARRANTIES: THIS SPECIFICATION IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, ACCURACY, COMPLETENESS AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL BSSC, ITS MEMBERS OR ITS CONTRIBUTORS BE LIABLE FOR ANY CLAIM, OR ANY DIRECT, SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THE SPECIFICATION.

THIRD PARTY RIGHTS: Without limiting the generality of the foregoing, BSSC ASSUMES NO RESPONSIBILITY TO COMPILE, CONFIRM, UPDATE OR MAKE PUBLIC ANY THIRD PARTY ASSERTIONS OF PATENT OR OTHER INTELLECTUAL PROPERTY RIGHTS THAT MIGHT NOW OR IN THE FUTURE BE INFRINGED BY AN IMPLEMENTATION OF THE SPECIFICATION IN ITS CURRENT, OR IN ANY FUTURE FORM. IF ANY SUCH RIGHTS ARE DESCRIBED ON THE SPECIFICATION, LICENSOR TAKES NO POSITION AS TO THE VALIDITY OR INVALIDITY OF SUCH ASSERTIONS, OR THAT ALL SUCH ASSERTIONS THAT HAVE OR MAY BE MADE ARE SO LISTED.