Cryptography Flashcards

1
Q

Cipher text

A

encrypted text that you cannot read

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Encryption/Decryption Algorithm

A

the process of encrypting/decrypting plain text to cipher text

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Symmetric Algorithm

A

uses the same key to encrypt and decrypt

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Asymmetric Algorithm

A

one key for encryption, and another key for decryption

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Data Encryption Standard (DES)

A

key size 56 bit - symmetric algorithm

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Triple DES

A

same as DES but using it 3 times to make the algorithm more secure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Advanced Encryption Standard (AES)

A

key size 128 bit - symmetric

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

RSA (Rivest-Shamir-Adleman)

A

asymmetric cryptographic algorithm with a key size 1024, 2048, 3072, 4096

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Why not use Asymmetric Algorithm for everything instead of Symmetric?

A

the resources that you need to handle asymmetric keys is much more (CPU pwer). The speed for asymmetric algorithm is much slower than symmetric algorithm

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Hash Algorithm

A

a one-way algorithm (once you encrypt your message you can not decrypt it)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is a Digest or Digital Fingerprint?

A

the result of a hashing algorithm. Also can be called a hash file.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is the purpose of hashing?

A

just for the integrity of the message

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are some common hash algorithms?

A

MD5, SHA, SHA-2, RIPEMD

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Hashed Message Authentication Code (HMAC)

A

cryptographic authentication technique that uses a hash function and a secret key. verify that data is correct and authentic with shared secrets.

Works by first sharing a private key. Then, generating a hash of the private key and message/file together as one hash. Then, sending it to end user. End user then hashes that file with their shared private key included, and compares that hash to the hash that the sender sent.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Digital Signature

A

hashing the message and then encrypting the hash using a private key and providing the end user with the public key so that they can decrypt the hash and rehash the message to compare with the sender hash.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is the difference between a Digital Signature and HMAC?

A

HMAC uses symmetric encryption and a Digital Signature uses asymmetric encryption

17
Q

Certificate Authority (CA)

A

3rd party that provides certificates to users to confirm that they are actually them. they also keep track of the status and can revoke the digital certificate

18
Q

Intermediate Certificate Authority

A

certificate authorities that are placed between a root CA to issue certificates on its behalf. The intermediate CA is also responsible for verifying the identity of the entity requesting the certificate and issuing the certificate.

19
Q

How does a Digital Certificate work?

A

user generates a public-private key pair, creates a Certificate Signing Request (CSR) which contains their public key and other identifying information. The user sends the CSR to the CA which then verifies the user’s identity and encrypts the CSR with its private key to create a digital certificate (which contains the user’s public key and additional info about the user and the CA). The CA then sends the signed digital certificate back to the user.

20
Q

How does a server or user verify a Digital Certificate?

A

by checking its validity, the CA’s signature, and ensuring the CA is trusted. Then extracting the public key from the CA and use it to decrypt the hash that was encrypted in the digital certificate. then compare the hash with the hash that was received earlier.

21
Q

Registration Authority (RA)

A

subordinate entities that are designed to handle some intermediate CAs tasks such as : identify and authenticate requesters, and then passes it to intermediate CAs.

22
Q

Certificate Repository (CR)

A

Publicly accessible centralized database of digital certificates. Can be used to view certificate status

23
Q

What are the 2 types of certificate revocation technologies?

A

Certificate Revocation List (CRL) and Online Certificate Status Protocol (OCSP)

24
Q

Certificate Revocation List (CRL)

A

a list of revoked digital certificates that is maintained by the CA. It contains a list of revoked certificates along with their serial numbers and other relevant information.

25
Q

Online Certificate Status Protocol (OCSP)

A

a protocol that allows the user to query the CA directly for the status of a certificate. It provides real-time responses and can quickly determine whether a certificate is valid or not. When a user requests the status of a certificate, the OCSP responder sends a signed response indicating the certificate’s status.

26
Q

Domain Digital Certificate

A

also know as an SSL/TLS certificate, is a digital certificate used to establish a secure connection between a web server and a client.

27
Q

What are the different types of Domain Digital Certificates?

A

Domain Validation - verify the domain ownership and encrypt the connection between a website and its visitors.

Extended Validation - provide the highest level of security by validating the legal, physical, and operational existence of the website owner.

Wildcard - secure a domain and its subdomains with a single certificate, allowing for cost savings and simplified certificate management.

Subject Alternative Names (SAN) - secure multiple domains or subdomains with a single certificate, making them ideal for multi-domain environments.

28
Q

Public Key Infrastructure (PKI)

A

a system of hardware, software, policies, and procedures that allows entities (such as individuals, organizations, or devices) to securely exchange digital information over the internet.

29
Q

Hierarchical Trust Model

A

where you can trust the digital certificate because it is issued by a root CA that certified the intermediate CAs who certified the leaf CAs who issued the certificate.

30
Q

Distributed Trust Model

A

trust is distributed across multiple parties, which collaborate to verify the authenticity of digital certificates and establish trust in the public keys associated with them. For example, in a distributed trust model like PGP, each user can choose who they trust based on their own criteria, rather than relying on a central authority.

31
Q

Bridge (Hybrid) Trust Model

A

multiple hierarchical trust models are linked together through a series of bridge CAs, which act as intermediaries between the different trust domains. allow different organizations or communities with their own PKI hierarchies to establish trust relationships with each other. The bridge CAs act as trusted intermediaries, issuing cross-certificates that allow entities in one hierarchy to trust entities in another hierarchy.

32
Q

Certificate Policy (CP)

A

a document that defines the rules, procedures, and standards for issuing and managing digital certificates within a Public Key Infrastructure (PKI).

33
Q

Certificate Practice Statement (CPS)

A

a document that describes the detailed procedures and practices for implementing the policies defined in the Certificate Policy (CP) within a Public Key Infrastructure (PKI). While a Certificate Policy defines the general rules and requirements for issuing and managing digital certificates, the Certificate Practice Statement provides more detailed information about the specific practices and procedures that are used to implement the policy

34
Q

What is the certificate life cycle?

A

Certificate generation
Certificate distribution
Certificate validation
Certificate usage
Certificate renewal
Certificate revocation
Certificate expiration

35
Q

Diffie-Hellman key exchange

A

allows two parties to agree on a shared secret key over an insecure communication channel by generating and exchanging different random numbers and using a shared prime number. The shared secret key is derived using modular exponentiation, which ensures that both parties will end up with the same key.