Public Key Infrastructure and Its Implementation

Understanding The Operational Model and Requirements
1. Auflage 2023
ISBN: 978-1-4842-8302-8
Verlag: Apress

Buch, Englisch, Book, Format (B × H): 178 mm x 254 mm

Learn implementation, automation, and the implications of introducing Public Key Infrastructure in your organization. This book will not only guide you in implementing PKI, but also help you understand exactly what is happening and why, and how to properly manage digital certificates wherever they exist.
Author Julian Ashbourn starts by discussing the basics of PKI and its primary applications, such as server identification, authentication for VPNs, email encryption, and much more. Further, he demonstrates how to work with digital certificates and how a PKI is used to encrypt sensitive data. Biometrics and PKI is discussed next, followed by the conventional infrastructure setup of PKI. Moving forward, you will learn what PKI certificate authentication is required in Kubernetes, and gain an understanding of the container model and its implications for PKI. You'll also learn more about certificate authorities, certificate expiry, and methodologies for security. Implementing a PKI is discussed next along with its technicalities and required skills, such as RFC and crypto standards. Finally, you will learn how to embed a PKI culture in your workplace, how to maintain it, and how to ensure accountability.
After reading this book, you will understand PKI infrastructure, implementation, its components, and its maintenance.
What Will You Learn - Understand the certificates requirements and how to maintain them
- Master the use of SSL/TLS certificates
- Gain an understanding of the container model and its implications
- Plan and document PKI requirements during new acquisitions and mergers
Who Is This Book For
IT practitioners, students and interested individuals.

Zielgruppe

Professional/practitioner

Autoren/Hrsg.

Ashbourn, Julian

Fachgebiete

• Mathematik | Informatik EDV | Informatik Technische Informatik Computersicherheit

Inhaltsverzeichnis

Chapter 1. What exactly is a PKI?
Chapter Goals: The original concept and an overview
Chapter 2. How does PKI work?
Chapter Goals: This chapter will discuss the nuts and bolts of PKI
Chapter 3. What are the primary applications for it?

Chapter Goals: How applications are changingServer IdentificationAuthentication for Web ApplicationsElectronic Document SigningAuthentication for VPNsS/MIME Email Signing and EncryptionEmail List Server
Chapter 4. What exactly is a digital certificate?
Chapter Goals: The contents of a certificate and 3 versions available for X.509 discussed
Chapter 5. What about encryption?
Chapter Goals: How a PKI is used for encryption of sensitive data in an organization.SSL/TLS certificates
Registration authorityCertificate AuthoritySymmetrical EncryptionAsymmetrical Encryption
Chapter 6. Biometrics and PKI
Chapter Goals: The possibilities of biometric certificates and how a biometric-PKI authentication system works.
Chapter 7. What is the conventional wider infrastructure?
Chapter Goals: Different infrastructure models explained - Public Key Certificate, commonly referred to as 'digital certificate'.
- Private Key tokens.
- Certification Authority.
- Registration Authority.
- Certificate Management System.

Chapter 8. Kubernetes, containers and PKI
Chapter Goals: Kubernetes requires PKI certificates for authentication over TLS. In this chapter, we will discuss The container model and its implications for PKI.
Chapter 9. How may we trust Certificate Authorities?
Chapter Goals: The original concept has changed
Chapter 10. What’s wrong with a self signed certificate?
Chapter Goals: self-signed certificates are public key certificates that their users issue on their own behalf, as opposed to a certificate authority issuing them. Here we will discuss the trust associated with self signed certificates
Chapter 11. How may a localised infrastructure work?
Chapter Goals: Keeping things simple
Chapter 12. What happens when certificates expire?
Chapter Goals: What can go wrong?
Chapter 13. How do we ensure that certificates do not expire?
Chapter Goals: Methodologies for security
Chapter 14. How does the the human interaction work?
Chapter Goals: Managing things manually. CSTCASRK Certificates
Chapter 15. Can we organize everything ourselves?
Chapter Goals: Understanding what to do
Chapter 16. How long does it take to implement a proper PKI?
Chapter Goals: Understanding the scale of the problem
Chapter 17. What skills do we need for operational personnel?
Chapter Goals: Understanding associated technologies
Chapter 18. How do we embed a PKI culture in the workplace?
Chapter Goals: CommunicationPeer-to-Peer networks
Chord protocol
Chord architecture

Chapter 19. How do we keep it all working as we grow?
Chapter Goals: Planning and documentation
Chapter 20.What happens if we acquire other companies?Chapter Goals: Merging PKIsUnderstanding Certificate policiesCertificate Practice Statement(CPS), Cross-Certification, PKI Interoperability.

Chapter 21. Who should be responsible for it all?Chapter Goals: Accountability

Chapter 22. PKI, the Cloud and the Internet of Things.Chapter Goals: What we should understand
Chapter 23. PKI and the global financial industryChapter Goals: The reliance upon a large scale PKI
Chapter 24. PKI and government legislationChapter Goals: Ensuring that legislation is compatible

Über Autor(innen)

Julian Ashbourn is an experienced and successful author on topics ranging from computer science and identity management through geoscience and the natural sciences in general. With experience of more than 20 years, Julian has been working for British Airways IT Deptartment; government agencies around the world regarding the application of biometrics and in the Natural and Physical Sciences producing an archive for the Geological Society.
He is also an accredited PKI engineer, an audio engineer and has numerous industry certificates and awards in his name. Julian has spoken at international conferences around the world and, on several occasions, has represented the European Commission.