 | This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Hardening" computing – news · newspapers · books · scholar · JSTOR (March 2009) (Learn how and when to remove this message) |
In computer security, hardening is usually the process of securing a system by reducing its attack surface, which is larger when a system performs more functions; in principle a single-function system is more secure than a multipurpose one. Reducing available ways of attack typically includes changing default passwords, the removal of unnecessary software, unnecessary usernames or logins, and the disabling or removal of unnecessary services.
Hardening measures can include setting up intrusion prevention systems, disabling accounts, reducing file system permissions and using encrypted network connections.
Binary hardening
Binary hardening is a security technique in which binary executables are analyzed and modified to protect against common exploits. Binary hardening is independent of compilers and involves the entire toolchain. For example, one binary hardening technique is to detect potential buffer overflows and to substitute the existing code with safer code. The advantage of manipulating binaries is that vulnerabilities in legacy code can be fixed automatically without the need for source code, which may be unavailable or obfuscated. Secondly, the same techniques can be applied to binaries from multiple compilers, some of which may be less secure than others.
Binary hardening often involves the non-deterministic modification of control flow and instruction addresses so as to prevent attackers from successfully reusing program code to perform exploits. Common hardening techniques are:
- Buffer overflow protection
- Stack overwriting protection
- Position independent executables and address space layout randomization
- Binary stirring (randomizing the address of basic blocks)
- Pointer masking (protection against code injection)
- Control flow randomization (to protect against control flow diversion)
See also
References
External links
- "Hardening Your Computing Assets" (PDF). at globalsecurity.org
- "CIS Benchmark List". at globalsecurity.org