Glossary
O
Obfuscation
- Description: The process of making data or code unreadable or difficult to understand, often for security purposes.
- Origin: Used since early software development to hide implementation logic or sensitive info.
- Impacts Data Types: Source code, configuration files, sensitive output.
- Examples: JavaScript minification, email address masking.
- Potential Fines: Indirect — useful in avoiding data leaks, thus supporting compliance.
Ohio Revised Code 1349.19
- Description: Requires disclosure of security breaches involving personal information to affected Ohio residents.
- Enacted and Enforced: Enacted June 2006; enforced since July 1, 2006.
- Impacts Data Types: SSNs, driver’s licenses, financial records.
- Examples: Emailing breach notices to affected consumers.
- Potential Fines: Civil penalties up to $1,000 per violation, plus restitution.
One-Way Hashing
- Description: Cryptographic method where data is transformed into a fixed-length hash that can’t be reversed.
- Origin: Used since the 1990s in password storage and verification systems.
- Impacts Data Types: Passwords, file integrity checks.
- Examples: SHA-256 hashed login credentials.
- Potential Fines: Indirect — improper use can lead to data breaches and fines under GDPR, HIPAA.