Impair Command History Logging

Detection Strategy for Impair Defenses via Impair Command History Logging across OS platforms.

Operating System Configuration: Operating System Configuration involves adjusting system settings and hardening the default configurations of an operating system (OS) to mitigate adversary exploitation and prevent abuse of system functionality. Proper OS configurations address security vulnerabilities, limit attack surfaces, and ensure robust defense against a wide range of techniques. This mitigation can be implemented through the following measures:

Disable Unused Features:

• Turn off SMBv1, LLMNR, and NetBIOS where not needed.
• Disable remote registry and unnecessary services.

Enforce OS-level Protections:

• Enable Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), and Control Flow Guard (CFG) on Windows.
• Use AppArmor or SELinux on Linux for mandatory access controls.

Secure Access Settings:

• Enable User Account Control (UAC) for Windows.
• Restrict root/sudo access on Linux/macOS and enforce strong permissions using sudoers files.

File System Hardening:

• Implement least-privilege access for critical files and system directories.
• Audit permissions regularly using tools like icacls (Windows) or getfacl/chmod (Linux/macOS).

Secure Remote Access:

• Restrict RDP, SSH, and VNC to authorized IPs using firewall rules.
• Enable NLA for RDP and enforce strong password/lockout policies.

Harden Boot Configurations:

• Enable Secure Boot and enforce UEFI/BIOS password protection.
• Use BitLocker or LUKS to encrypt boot drives.

Regular Audits:

• Periodically audit OS configurations using tools like CIS Benchmarks or SCAP tools.

Tools for Implementation

Windows:

• Microsoft Group Policy Objects (GPO): Centrally enforce OS security settings.
• Windows Defender Exploit Guard: Built-in OS protection against exploits.
• CIS-CAT Pro: Audit Windows security configurations based on CIS Benchmarks.

Linux/macOS:

• AppArmor/SELinux: Enforce mandatory access controls.
• Lynis: Perform comprehensive security audits.
• SCAP Security Guide: Automate configuration hardening using Security Content Automation Protocol.

Cross-Platform:

• Ansible or Chef/Puppet: Automate configuration hardening at scale.
• OpenSCAP: Perform compliance and configuration checks.

Environment Variable Permissions: Restrict the modification of environment variables to authorized users and processes by enforcing strict permissions and policies. This ensures the integrity of environment variables, preventing adversaries from abusing or altering them for malicious purposes. This mitigation can be implemented through the following measures:

Restrict Write Access:

• Use Case: Set file system-level permissions to restrict access to environment variable configuration files (e.g., .bashrc, .bash_profile, .zshrc, systemd service files).
• Implementation: Configure /etc/environment or /etc/profile on Linux systems to only allow root or administrators to modify the file.

Secure Access Controls:

• Use Case: Limit access to environment variable settings in application deployment tools or CI/CD pipelines to authorized personnel.
• Implementation: Use role-based access control (RBAC) in tools like Jenkins or GitLab to ensure only specific users can modify environment variables.

Restrict Process Scope:

• Use Case: Configure policies to ensure environment variables are only accessible to the processes they are explicitly intended for.
• Implementation: Use containerized environments like Docker to isolate environment variables to specific containers and ensure they are not inherited by other processes.

Audit Environment Variable Changes:

• Use Case: Enable logging for changes to critical environment variables.
• Implementation: Use auditd on Linux to monitor changes to files like /etc/environment or application-specific environment files.