Cryptography is the set of techniques used to protect information by controlling who can read it, verify it or prove that it has not been changed. For enterprise teams, the important question is not only whether encryption exists. It is whether the algorithms, keys, identities and operating processes around it are trustworthy.
1. What is encryption?
Encryption transforms readable information, called plaintext, into unreadable ciphertext using an algorithm and a cryptographic key. A system with the correct key can reverse that transformation. Encryption is mainly used to protect confidentiality when data is stored or moving between systems.
2. What is a cryptographic key?
A key is a value used by a cryptographic algorithm to encrypt, decrypt, sign or verify information. The algorithm can be public; the security of the system depends heavily on protecting the key. This is why key generation, storage, access control, rotation, backup and retirement are central security responsibilities.
3. What is the difference between symmetric and asymmetric cryptography?
Symmetric cryptography uses the same secret key to encrypt and decrypt data. It is efficient and commonly used for protecting large volumes of data. Asymmetric cryptography uses a mathematically related public key and private key. It is commonly used for identity, digital signatures and securely establishing shared secrets.
4. Is hashing the same as encryption?
No. Encryption is designed to be reversible when the correct key is available. A cryptographic hash is designed to produce a fixed-size fingerprint of data without providing a practical way to reconstruct the original input. Hashes are commonly used for integrity checks, password-verification systems and digital-signature workflows.
5. What does TLS do?
TLS, or Transport Layer Security, protects connections such as HTTPS. It helps a client authenticate the server, establish protected session keys and encrypt data in transit. Strong TLS still depends on correct certificate management, trusted identities and secure private keys.
6. Why do keys need to be rotated?
Key rotation limits how long one key remains active and reduces the amount of data exposed if a key is compromised. Rotation should be planned so applications can move to new keys without losing access to data that still requires an older key for decryption.
7. Where should enterprise keys be stored?
High-value keys should be isolated from ordinary application code and managed through purpose-built controls such as hardware security modules or managed key-management systems. Access should be restricted, auditable and separated according to role and risk.
8. What makes cryptography fail in practice?
Failures often happen around the cryptography rather than inside the mathematical algorithm: exposed private keys, weak secrets, poor certificate handling, excessive permissions, missing rotation, insecure backups, outdated algorithms or systems that cannot identify where sensitive keys are being used. Good cryptography therefore requires strong operational discipline as well as strong algorithms.
The practical takeaway
For an enterprise, cryptography should be treated as an operating capability. Know which data needs protection, know which keys protect it, know who and what can use those keys, monitor their lifecycle and be able to rotate or revoke them without disrupting the business.