Implementing Best Practices

Basic Hygiene

Visibility
  1. Send system logs to a centralized logging server. 1.Alert on:

    1. Added, changed, or removed software packages.

    2. Administrative logins from unknown source locations.

    3. Interactive administrative logins.

    4. Users added or removed.

    5. Changes to users’ group membership.

    6. Changes to operating system configuration.

    7. Changes to network configurations.

Default Deny
  1. Utilize system firewalls to deny access to system services unless required.

  2. Restrict access to administrative functions except through approved, secured communication channels.

Least Privilege
  1. Limit privileged access to the operating system to authorized personnel.

  2. Do not allow shared superuser accounts to log into systems remotely.

  3. Disable default accounts.

Segmentation
  1. Create a segmented network for user workstations separate from other types of operating systems used.

Configuration
  1. Ensure endpoints are up to date with the latest patches from the vendor.

  2. Install Anti-Malware defenses and keep them updated.

  3. Implement 2FA for access to high-value systems.

Advanced Hygiene

Visibility
  1. Deploy EDR or similar functionality (https://github.com/SwiftOnSecurity/sysmon-config) to gain greater visibility.

  2. Expand logging to include audit trails of privileged users’ access and activities. 1.Improve alerting by adding detections for:

    1. Privilege escalation attempts.

    2. Failed logins.

    3. Log clearing events.

    4. Security policy changes in host-based defenses.

    5. Changes in users’ authorizations.

    6. Account lockouts.

    7. Wired and wireless LAN system simultaneous connections.

    8. Two directly connected user workstations.

Default Deny
  1. Implement application control by preventing installation or execution of software from:

    1. Unapproved sources.

    2. Browser downloads, including those to temporary folders.

  2. Prevent wireless and wired workstations from directly accessing each other.

  3. Prevent wireless clients from directly accessing other wireless devices.

  4. Prevent or limit direct internet access wherever possible. Servers, for example, rarely need to browse any website.

Least Privilege
  1. Ensure users utilize separate accounts for administrative functions.

  2. Discontinue the use of shared superuser accounts.

  3. Restrict use of living off the land binaries (https://threatpost.com/living-off-the-land-malicious-use-legitimate-utilities/177762/) using application control.

Segmentation
  1. Segment user workstations by job role.

  2. Segment servers by logical grouping such as physical location, use case sensitivity, or workload.

  3. Separate any mission-critical system from all other network endpoints, especially those that are older or difficult, if not impossible, to patch.

Configuration
  1. Utilize CIS benchmarks to harden systems.

  2. Remove default accounts if possible.

  3. Use random passwords to secure default accounts that must remain active.

Resilient Operations

Visibility
  1. Implement behavior analysis and alert on:

    1. “Superman” rules that help indicate impossible user access based on time and distance between geographies of the source IP.

    2. Geography, source IP, destination IP, session duration, and transfer sizes are tracked per device and user with anomaly alerting.

    3. Patterns of administrator access and actions taken, tracked with alerts for abnormal behaviors.

    4. Abnormal network connections based on network (https://en.wikipedia.org/wiki/Network_layer) and transport (https://en.wikipedia.org/wiki/Transport_layer) layer session details.

    5. Abnormally large transfer sizes per user, source address, and destination address.

    6. Abnormal process execution.

    7. Abnormal command-line arguments for any process.

Default Deny
  1. Deny users from utilizing simple passwords by enforcing a password policy that requires a complex password of at least ten (10) characters and enforces password history.

  2. Use application control to prevent process execution except for specifically approved applications.

Least Privilege
  1. Instead of using privileged accounts for operating system administration, use software that enables authorized users to execute a minimal set of functions.

Segmentation
  1. Work to achieve microsegmentation as much as possible. Separate computers based on workload with security controls enforcing access between all segments.

Configuration
  1. Harden configurations using guidance from a government (https://media.defense.gov/2021/Sep/28/2002863184/-1/-1/0/CSI_SELECTING-HARDENING-REMOTE-ACCESS-VPNS-20210928.PDF), third-party (https://www.cisecurity.org/cis-benchmarks/), or vendor source as much as possible.

  2. Remove all unnecessary applications from each system install.

Operating Systems Resources