System Hardening
Octavious W.
Incident Response | Digital Forensics | Vulnerability Analysis | Security+ | CHFI | CEH | Cisco Certified CyberOps Associate | GFACT | GSEC (2025) | GCIH (2025)
System hardening is the process of making changes to a system or application to make it more secure than it’s default configuration.
System Hardening Techniques:
Changing default configurations:
The default password for systems and devices like routers should be changed before using the them; default passwords can be easy to guess or find online
Changing the default name of the administrator account may also be helpful since attackers need the correct username and password to break into the account
The Registry may need to be modified so that Powershell activity is logged
Disabling non-essential ports or services:
Ports and services that are not necessary for a given system’s intended function should be disabled.
This will reduce the system’s attack surface.
For example we’d only expect a web server to be running HTTP and HTTPs on ports 80 and 443 respectively.
Check for open ports on Windows via Command Prompt with the netstat command:
Once you’ve learned the PIDs associated with open ports you can close the ports, and end the process on Windows with the taskkill command:
Check for open ports on Linux in the terminal with the ss command:
Close open ports in Linux using the kill command with the process ID:
Using secure protocols:
Protocols for securely transferring files:
Secure protocols for voice and video data:
Secure protocols for web and email data:
Securing Directory Services:
Time Synchronization:
Securing DNS:
领英推荐
Securing network address allocation:
Secure Remote Access:
Keeping up with the latest system patches:
Remove unnecessary software to avoid any vulnerabilities that software may have
Maintaining the latest updates ensures that software has the most recent security patches for bugs and vulnerabilities
Strong passwords:
A stronger, more complex password is harder to crack
Characteristics of a strong & complex password:
Multi-factor Authentication (MFA): Requires the user to provide more than 1 form of authentication to gain access such as something you know like a PIN, and something you have like a smart card. MFA is helpful, but this can be bypassed.
Implementing a robust password policy:
Password expiration identifies when users will be forced to change their passwords (Example: every 90 days users will be prompted to change their password)
Password history controls remember previously used passwords and prevent users from reusing old passwords via the password age setting (Example: block users from using their last 30 previously used passwords)
Account lockout policies can prevent password guessing attacks like brute forcing. Lockout threshold defines how many failed login attempts will cause the account to lock, and lockout duration defines how long the account lock will last
Account Management:
Use 2 accounts for admins: Administrators should have one account for day-to-day work and a seperate account for activities that require elevated privileges. If the account used for normal daily work gets compromised, the attacker won’t instantly have elevated privileges.
Do not allow shared accounts: Allowing the use of shared accounts negates the implementation of authorization controls, and makes it harder to attribute actions to specific users
Disabling default and unnecessary accounts: Accounts for termed employees should be disabled ASAP and deleted when no longer needed. Disable the account initially to retain any decryption keys that may provide access to encrypted data associated with the account. Guest accounts should be disabled when not in use.
Resources:
CIS Benchmarks:
12 ss Command Examples to Monitor Network Connections:
netstat:
The art of MFA Bypass: How attackers regularly beat two-factor authentication:
Cloud Security & Compliance Leader | CEO @ Cyber Training Pro | YouTuber, Trainer, Career Coach, Mentor ?? | Developing Information Security Beginners Into Experts
1 年Octavious have you ever heard of Privileged Access Workstations? If not, I highly recommend learning about it because it ties into your post. https://learn.microsoft.com/en-us/security/privileged-access-workstations/privileged-access-devices
System Hardening is a crucial step in making sure that systems are secure not only when they are first introduced but over time as things change in our environments! Great post Octavious!