1/11
Looks like no tags are added yet.
CIA Triad
A combination of three core principles that form the foundation of security. It’s sometimes referred to as the AIC Triad (Access, Integrity, Confidentiality) to avoid confusion with the Central Intelligence Agency. These principles are:
Confidentiality: Ensuring that information is not disclosed to unauthorized individuals or systems. It protects sensitive data from being accessed by people who shouldn’t see it.
Integrity: Ensuring that messages or data cannot be altered without detection. This guarantees that the information remains accurate and trustworthy.
Availability: Ensuring that systems and networks are functioning and accessible when needed. This means making sure that the data and services are always up and running.
Confidentiality
Ensuring that certain information is only accessible to the people who are authorized to know it. It involves preventing unauthorized disclosure of sensitive data. To maintain confidentiality, several methods are used:
Encryption: This involves encoding messages so that only authorized individuals can read them. It keeps information secure while it’s being transmitted.
Access Controls: These are measures that selectively restrict access to resources, ensuring that only certain users can access specific information or systems.
Two-factor Authentication: This adds an extra layer of security by requiring an additional confirmation (such as a code sent to a phone) before information is disclosed or accessed.
Integrity
Ensures that data is stored and transferred exactly as intended, with any modification being detectable.
Hashing: This process maps data of any length to a fixed-length value. A person creates a hash of the data and sends both the data and the hash to you. You then apply the same hashing function to the received data. If your hash matches the one sent, you can be sure the data hasn’t been changed.
Digital Signatures: This is a mathematical method to verify the integrity of data.
Certificates: Certificates work with digital signatures to verify the identity of the sender. They ensure that the sender’s public key is legitimate and that they are who they claim to be.
Non-repudiation: This provides proof of integrity, ensuring that the sender cannot deny sending the data.
Availability
Ensures that information and systems are accessible to authorized users whenever they need it.
Redundancy: This involves building systems with backup components or services to ensure they remain available even if one part fails. It helps keep services running at all times.
Fault Tolerance: This ensures that a system continues to function even if a failure occurs. It’s designed to handle errors gracefully without causing major disruptions.
Patching: This is the process of updating and fixing systems to close security vulnerabilities and improve stability. Regular patching helps keep systems secure and running smoothly.
Non-repudiation
Once you’ve made a statement or action, you cannot deny it later. It’s the idea that there’s no way to take it back. Provides proof of integrity and origin, ensuring the authenticity of data or messages.
Sign a Contract: When you sign a contract, your signature adds non-repudiation. It proves that you genuinely agreed to the terms.
Digital Signatures: Just like a physical signature, a digital signature confirms that you really sent a message or document. Others can see your signature and verify that it came from you.
Proof of Integrity & Origin: Non-repudiation provides high assurance that the data hasn’t been altered and that it came from the right source. It helps prevent the sender from denying their involvement.
Proof of Integrity
Ensures that data has not been altered, remaining accurate and consistent over time. In cryptography, this is typically done using a hash, which represents the data as a short string of text.
Hashing: A hash, sometimes called a message digest or fingerprint, is generated based on the data. If the data changes, the hash will also change, signaling that the data has been modified.
Data Integrity: A hash doesn’t associate data with a specific individual—it only shows if the data has been altered. If someone changes the data, the hash will no longer match the original, providing proof that the integrity has been compromised.
Hashing
One way algorithms that produce an unique hexadecimal number to represent the source data. The output will never match anything else but the exact source data.
So people can hash data and check if the output hash matches what it should be to verify integrity.
Hashing the Encyclopedia Example
Suppose I downloaded volume one of the Gutenberg Encyclopedia, which is 8.1 megabytes of data. Using an application, I created a hash (or fingerprint) of that file.
Detecting Changes: If I change even one character in the file, the size stays the same, but the data is altered. It would be nearly impossible for someone to manually find the change in all that text.
Comparing Hashes: However, by creating a hash of the modified file and comparing it to the original hash, I can easily spot the difference. If the hashes don’t match, I know the file has been altered.
Data Integrity: If the hash is different, it means the data integrity has been compromised, showing that the content of the file has changed.
Proof of Origin
Ensures that the message hasn’t been altered and confirms its integrity.
Integrity: This means verifying that the content of the message is intact and hasn’t been changed in transit.
Authentication: Ensures the signature on the message is legitimate, confirming the identity of the sender.
Non-repudiation: Guarantees that the sender cannot deny sending the message once it’s signed.
Digital Signature
The sender signs the message with their private key. This provides proof of origin, and the message doesn’t need to be encrypted.
Nobody else can sign it because only the sender has the private key.
The recipient verifies the signature using the sender’s public key. If the message is altered in any way, the signature will be invalid.
Creating a Digital Signature
Message: Alice wants to send a message to Bob that says, "You're hired, Bob."
Hashing: Before sending the message, Alice applies a hashing algorithm to generate a unique hash of the plaintext message ("You're hired, Bob.").
Encryption: Alice then encrypts the hash with her private key. This ensures that only Alice could have created the hash, as only she has the private key.
Sending the Message: Alice sends both the original message and the encrypted hash (digital signature) to Bob.
Verifying a Digital Signature:
Decryption: Bob will use Alice’s public key (which anyone can access) to decrypt the digital signature. This gives him the original hash that Alice created from the plaintext message.
Hashing the Message: Bob then applies the same hashing algorithm that Alice used (they agreed on this beforehand) to the original message he received. This generates a hash of the message he got.
Comparison: Bob compares the decrypted hash (from the digital signature) with the hash he generated from the message. If the two hashes match, it confirms that the message has not been altered and came from Alice.