1 Scope
2 References
3 Definitions
3.1 Terms defined elsewhere
3.2 Terms defined in this Recommendation
4 Abbreviations and acronyms
5 Conventions
6 Overview
7 Evaluation on whether to deliver a security service based on DLT
8 DLT-based public-key certificate management
8.1 Basic concept
8.2 Brief description
9 DLT-based software defined perimeter
9.1 Basic concept
9.2 Brief description
10 DLT-based threat intelligence sharing
10.1 Basic concept
10.2 Brief description
11 DLT-based security audit
11.1 Basic concept
11.2 Brief description
Annex A – DLT-based public-key certificate management methods
A.1 Revoke, suspend, resume or renew an existing public-key
certificate
A.2 Verification of a public-key certificate at the relying party
A.3 Storage optimization
Annex B – Authentication and authorization by DLT-based software defined
perimeter
B.1 Authorization by nodes in the DLT system
B.2 Authorization by ASDPHs
Appendix I – Using DLT for security services: Challenges and benefits
I.1 Using DLT for public-key certificate management
I.2 Using DLT for software defined
perimeter
I.3 Using DLT for threat intelligence sharing
I.4 Using DLT for security audit
Appendix II – H(e)NB device authentication and verification by public-key
certificate identifier – Two use cases of DLT-based public-key certificate
management service
II.1 H(e)NB device authentication
II.2 Verification by the public-key certificate identifier
Appendix III – Developer access to private cloud network as a use case of
DLT-based software defined perimeter service
Appendix IV – Architecture and use case of DLT-based threat intelligence
sharing platform
IV.1 DLT-based threat intelligence sharing platform architecture
IV.2 Threat intelligence sharing and rating
Appendix V – Architecture and use case of DLT-based security audit platform
V.1 DLT-based security audit platform architecture
V.2 Public-key certificate audit
Bibliography