110• In a PKI you are given a digital certificate, which contains your identity, and a key public key people can use to encrypt data securely to you OR verify items that you have digit
Trang 2Public Key Infrastructure
So… Symmetric key (private key) encryption is fast and nice, but has what MAJOR
problem?
Symmetric Key encryption, also doesn’t
provide integrity concerns ;(
Asymmetric Key/public key encryption can be combined with Symmetric Key encryption to solve BOTH problems, but Symmetric Key
encryption has what problem of it’s own?
Trang 3MiM (normal exchange)
Trang 4MiM Attack! (part 1)
Trang 5MiM Attack! Part 2
Trang 6Public Key Infrastructure
Wouldn’t it be nice if some one we could
distribute public keys AND be assured that the public key we received was the actual public key of the person we expect to talk to?
Trang 7PKI to the rescue!
Trang 8PKI (109)
PKIs are generally concerned with ensuring and managing identity trust, specifically using
“digital certificates”
• Provides all the components necessary for
users to be able to communicate securely in a managed method
• Includes hardware, software, policies,
services, algorithms and protocols
• Enables C, and I of the CIA triad
• Enables non-repudiation
Trang 9PKIs how do they work? (110)
• In a PKI you are given a digital certificate, which contains
your identity, and a key (public key) people can use to
encrypt data securely to you OR verify items that you have digitally signed!
• However we must have some way of ensuring that the digital certificate has not been “faked” so we have a entity called a Certificate Authority (CA) that digitally signs your digital
certificate, proving that the digital certificate is really yours!
– It is important that users trust the CA, otherwise there is no purpose!!! The entire PKI structure relies upon the fact that the CA can be
trusted! If the CA is comprimised the whole PKI is useless.
(more)
Trang 10PKIs how do they work? (110)
• CAs are computer technology entities that issue/sign your
digital certificates, however they rely on an entity to actually do
a “background” check on you to prove you really are you you say you are before the CA will “vouch” for you This
“background” check entity is called an Registration Authority (RA)
RA would take identifying information that proves I am who I say
Trang 11PKIs how do they work? (115)
• Once a digital certificate has been created
and signed, they are stored in a “Certificate
repository” which can be queried by users and applications in a PKI when someone wants to communicate with a user
• These repositories are usually LDAP
compliant databases
Trang 12So what’s in a Digital Certificate?
Trang 13Lets look at a digital Certificate
together (n/b)
• Firefox – https://www.redhat.com
• Click on the yellow lock at the bottom
• In the pop-up click on “view certificate”
• What version is it?
• What’s the “Common Name”
• Who is the Issuing Certificate Authority
• When does the Certificate Expire
• Why would a certificate expire?
(more)
Trang 14Lets look at a digital Certificate
together (n/b)
Now click on the details tab
• What is this “Certificate Hierarchy” stuff?
• Who Signed the cert for www.redhat.com
• Who signed the cert for that CA?
• This “vouching” for CAs is called a
Trang 15PKI hierarchy
PKI implementations are usually a hierarchy,
where one CA signs another CAs
certificate
• Parent Child relationship
• Top parent is called a root CA
• All others are called subordinate CA
Visualization next slide
Trang 16PKI hierarchy (142)
Trang 17CA concerns (112)
• Every CA should have a Certification Practice
Statement which outlines
– How the RA verifies identities
– How the Certificates are transferred
– How keys are secured
– What data is in a Digital Certificate
– How revocations are handled… etc
• Before using a 3 rd party CA, you should understand and be comfortable with CPS and the security
controls they use If the CA does not handle things securely… there is no point in using them.
Trang 18Advanced PKI concepts
Trang 20Types of Certificates(145)
• Cross-certification certificates
– When two companies want to trust each
other, their root CAs may issue a certificate to the root CAs for each other, allowing a “peer
to peer” trust model for CAs and allowing
users in one organization to trust users in
another.
Visualization next slide
Trang 21Cross Certification
Trang 22Web of Trust model
Trang 23Web of Trust model (n/b)
Web of Trust is a PKI with no central hierarchy, it’s literally a web It’s like 6 degrees of
separation
• Bob vouches for Andy
• Sarah trusts Bob, so she trusts the identity of Andy
• Sara vouches for Bob
• Steve trusts Sara, therefore he trusts the
identities of Bob, and Andy via Sarah…
• PGP uses web of trust
Trang 24Web of Trust
Trang 25Example PGP verification
Do an example of verifing the signature of ClamAV (pentest1)
Trang 26PGP verify
Trang 27Multiple Certificates (133)
Some PKIs use multiple certificates, and as such multiple public/private key pairs
• One for digitally signing data
• One for encrypting data
Why would we want to have two different
keys? (Hint think key storage and
non-repudiation)
Trang 29Certificate Revocation (126)
We have a wonderful system of distributing and
verifying Digital Identities (certificates) But
we may need to revoke a users digital
Identity?
Why?
1 Hint – think encryption
2 Hint – think Human Resources
(more)
Trang 30Certificate Revocation (126)
The CA publishes a Certificate Revocation List
• Certificate serial number that have been
Trang 31• Suspended certificates MAY be
un-suspended
Trang 32OCSP (129)
Online Certificate Status Protocol – a client server model, where a client program
actually queries a server to see if
someone’s certificate is valid This way the client does not need to know how to find
the CRL for the given certificate Authority and doesn’t have to actually search
through the CRLS
Be aware of this term for the exam
Trang 33Key Recovery (133)
When an organization uses encryption to protect
data, we must also protect the keys For example
if Bob encrypts all his work and then quits, we
need to be able to retrieve his private key to encrypt his work!
un-• This is called “key archiving”
• Only backup the encryption private key in a certificate system – why?
multi-• Need to ensure the safety of these backups
• Use dual controls (m of n) concept to protect keys
- explain
(more)
Trang 34Key Recovery (133)
• No need to backup public keys
• The process of using backup keys is called key recovery
• Key recovery should be highly audited!
Trang 36Certificate Extensions (123)
Allow for further information to be inserted within a digital certificate
• Introduced in X.509 v3
• Important extension is “key usage” –
which defines what the public key may be used for
– Ex Use for S/MIME email, or for code signing
Trang 38PKI concerns
• What happens if my CA is compromised?
• What happens if your Certificate repository
Trang 39PKI concerns
• Remember PKI requires public keys (in
the certificate) and private keys (kept
private to a user) Often private keys are kept in storage on a hard drive, or on a
removable drive (USB key)
• What are some concerns and
countermeasures dealing with private key storage?
• Extended Validation Digital Certificates
Trang 40PKI review questions
Q What is a digital certificate generally analogous to?
Q What are the two most important pieces of info in a digital certificate
Q Why would you use multiple certificates
Q If you have 100 users, in a 2 certificate model
(encryption & signing) how many total keys do you have?
Trang 41PKI review
Q What is key escrow
Q How do I validate the identity of a certificate that someone has given me? When does the validation chain end?
Q What version of X.509 were extensions added?
Q My certificate has been revoked, how do I
“un-revoke it”