A digital signature is a value created with a sender's private key that proves who sent a message and that it hasn't been altered. Anyone can verify it using the sender's public key, making it a core application of asymmetric cryptography (Topic 5.4).
A digital signature is what you get when you flip asymmetric encryption around to prove identity instead of hide a message. Normally you encrypt with someone's public key so only they can read it with their private key. A digital signature does the reverse: the sender locks something with their private key, and anyone can unlock it with the matching public key. Since only the sender owns that private key, a successful unlock proves the message really came from them and wasn't tampered with on the way.
This works because of how key pairs are built (EK 5.4.A.2). The two keys are binary strings of equal length, generated together, and they're mathematical inverses, so each key reverses its partner. Either key can encrypt, but only the other key can decrypt. That two-way property is exactly what makes signatures possible. Algorithms like RSA and elliptic curve cryptography (ECC) are the usual engines behind digital signatures (EK 5.4.C.1), and you can produce them with tools like OpenSSL on the command line.
Digital signatures live in Unit 5: Securing Applications and Data, specifically Topic 5.4 Asymmetric Cryptography. The CED names them directly in EK 5.4.C.1 as one of the main applications of asymmetric algorithms, alongside digital certificates. They tie straight to AP Cybersecurity 5.4.A, where you decide which key fits the job. Encrypting for someone uses their public key; signing as yourself uses your own private key. Mixing those up is the classic mistake. Signatures also connect to 5.4.B on key length, because a longer key means a bigger keyspace and a signature that's harder to forge.
Keep studying AP Cybersecurity Unit 5
Visual cheatsheet
view galleryAsymmetric Encryption (Unit 5)
A digital signature is asymmetric encryption running in reverse. Instead of encrypting with the public key for privacy, you encrypt with the private key for proof of identity. Same key pair, opposite direction.
Private Key and Public Key (Unit 5)
Signing uses your private key; verifying uses your public key. If you can remember 'I sign with what's secret, you check with what's public,' you've basically solved every signature question.
Certificate Authority and Digital Certificates (Unit 5)
A digital certificate is a public key signed by a trusted certificate authority. So a digital signature is the building block that makes certificates trustworthy in the first place.
RSA and ECC (Unit 5)
These are the algorithms that actually do the math behind a signature. ECC reaches the same security as RSA with shorter keys, which is why mobile and IoT devices lean on it.
Expect multiple-choice stems that hand you a scenario and ask which key does the work. The pattern from practice questions is clear: when Alex encrypts data with Jordan's public key, that's confidentiality, but flip it to 'proves who sent it' and you're in signature territory using the sender's private key. You need to identify the purpose (confidentiality versus authenticity) and then pick the matching key. Questions may also describe generating two mathematically inverse binary strings, which is the key-pair generation that signatures depend on. No released FRQ has used 'digital signature' verbatim, but it's a textbook example of EK 5.4.C.1, so be ready to explain how asymmetric keys provide authenticity, not just secrecy.
Encryption for confidentiality uses the recipient's public key so only they can read the message. A digital signature uses the sender's private key so anyone can confirm who sent it. One hides content, the other proves identity. They use the same key pair but opposite keys and opposite goals.
A digital signature is created with the sender's private key and verified with the sender's public key.
Signatures prove authenticity and integrity (who sent it and that it wasn't changed), not confidentiality.
It's the reverse of normal asymmetric encryption, which encrypts with the recipient's public key for privacy.
RSA and ECC are the asymmetric algorithms that power digital signatures (EK 5.4.C.1).
Longer keys make signatures harder to forge because the keyspace grows to 2^n (EK 5.4.B.1).
It's a value the sender creates with their private key that proves the message came from them and wasn't altered. Anyone can verify it using the sender's public key. The CED lists it as a main application of asymmetric algorithms in EK 5.4.C.1.
No. A signature proves who sent the message and that it's unchanged, but it doesn't keep the content secret. If you need privacy, you encrypt with the recipient's public key, which is a separate step.
Regular encryption for confidentiality uses the recipient's public key so only they can read it. A digital signature uses the sender's private key so anyone can confirm the sender's identity. Same key pair, opposite keys, opposite goals.
Sign with your private key, verify with the matching public key. Since only you hold the private key, a successful verification proves the message is genuinely yours.
A digital certificate is basically a public key that a certificate authority has digitally signed. So the signature is the trust mechanism that makes certificates (and things like TLS) reliable.
Connect this key term to the AP exam workflow: review the course, practice questions, and check related study tools.