π Lecture 30 β Security Hardening β Case Studies
π Overview: This lecture presents five detailed case studies of security hardening applied to different operating systems and applications, including Linux, Solaris, Apache, Oracle, and MS SQL Server. Using real-world benchmark documents from CIS and DISA, it demonstrates how to audit and remediate specific security vulnerabilities to reduce attack surfaces and enforce least privilege.
ποΈ Topics Covered
The lecture covers security hardening case studies for Red Hat Enterprise Linux 7 (CIS Benchmark), Solaris 10 X86 (DISA STIG), Apache Tomcat 7 (CIS Benchmark), Oracle Database 12c (DISA STIG), MS SQL Server 2012 (CIS Benchmark), and Oracle Database 11.2g (DISA STIG). Each case study presents a specific rule, including description, rationale, audit procedure, remediation, and control correlation identifiers.
π Lecture Summary
Topic no 72: Case Study Security Hardening β Linux
This case study is based on the CIS Benchmarks for Red Hat Enterprise Linux 7 (January 31, 2017, 347-page PDF). The specific rule covered is 5.2.2 (page 258): Ensure SSH Protocol is set to 2 (Scored). This rule applies to Level 1 profiles for both Server and Workstation.
SSH supports two incompatible protocols: SSH1 and SSH2. SSH1 was the original protocol and was subject to security issues, while SSH2 is more advanced and secure. The rationale is that SSH v1 suffers from insecurities that do not affect SSH v2.
The audit procedure requires running the command # grep "^Protocol" /etc/ssh/sshd_config and verifying the output shows Protocol 2. The remediation involves editing the /etc/ssh/sshd_config file to set the parameter as follows: Protocol 2.
This rule maps to Critical Controls: 3.4 Use Only Secure Channels For Remote System Administration. The recommendation is to perform all remote administration of servers, workstations, network devices, and similar equipment over secure channels. Protocols such as telnet, VNC, RDP, or others that do not actively support strong encryption should only be used if performed over a secondary encryption channel, such as SSL, TLS, or IPSEC.
π Definition β SSH Protocol 2: The more advanced and secure version of the SSH protocol, replacing the insecure SSH1.
π Rule: SSH Protocol must be set to 2 β Ensures only the secure SSH2 protocol is used for remote administration.
π Example: To harden an RHEL7 SSH server, a system administrator edits /etc/ssh/sshd_config, sets Protocol 2, and restarts the SSH service, preventing any SSH1 connections.
Topic no 73: Security Hardening β Case Study β Solaris
This case study is based on DISA (Defense Information Systems Agency) for Solaris 10 X86, Release 18 (28 April 2017). The rule is: All shell files must have mode 0755 or less permissive (STIG ID: GEN002220, Severity: CAT I).
The discussion explains that shells with world/group-write permissions give the ability to maliciously modify the shell to obtain unauthorized access.
The check content procedure: if /etc/shells exists, check the group ownership of each shell referenced using # cat /etc/shells | xargs -n1 ls -lL. Otherwise, check any shells found on the system using # find / -name "*sh" | xargs -n1 ls -lL. If a shell has a mode more permissive than 0755, this is a finding.
The fix text is to change the mode of the shell: #chmod 0755 <shell>.
The CCI (Control Correlation Identifier) is CCI-000225: The organization employs the concept of least privilege, allowing only authorized accesses for users (and processes acting on behalf of users) which are necessary to accomplish assigned tasks. This maps to NIST SP 800-53 :: AC-6.
π Definition β 0755 permission: A file permission mode where the owner has read, write, and execute (7), and the group and others have read and execute (5), but no write access.
π Rule: Shell files must have mode β€ 0755 β Prevents unauthorized modification of shell executables.
π Example: If a shell like /bin/bash has permissions 0777 (world-writable), an attacker could modify it to execute malicious commands. The fix changes it to 0755 (chmod 0755 /bin/bash), removing write access for group and others.
Topic no 74: Case Study Security Hardening β Apache
This case study is based on the CIS Benchmarks for Apache Tomcat 7 (April 26, 2016, 94-page PDF). The specific rule is 7.7 (page 65): Configure log file size limit (Scored) (Profile applicability: Level 2).
The description explains that by default, the logging.properties file will have no defined limit for the log file size. This is a potential denial of service attack as it would be possible to fill a drive or partition containing the log files.
The rationale is that establishing a maximum log size that is smaller than the partition size will help mitigate the risk of an attacker maliciously exhausting disk space.
The audit requires validating that the max file limit is not greater than the size of the partition where the log files are stored.
The remediation is to create the following entry in the logging.properties file (value specified in bytes): java.util.logging.FileHandler.limit=10000. The default value is no limit.
π Definition β Denial of Service (DoS) attack via log files: An attacker fills the disk partition with log entries until no space remains, causing system failure.
π Rule: Configure log file size limit β Prevents disk exhaustion by capping log file growth.
π Example: An Apache Tomcat server has no log size limit. An attacker sends many requests, filling the /var/log partition. This causes the server to crash. The fix sets java.util.logging.FileHandler.limit=10000 (10KB), preventing unlimited log growth.
Topic no 75: Security Hardening β Case Study β Oracle
This case study is based on DISA for Oracle Database 12c, Release 18 (28 April 2017). The rule is: The Oracle Listener must be configured to require administration authentication (STIG ID: O121-BP-022700, Severity: CAT I).
The discussion explains that Oracle listener authentication helps prevent unauthorized administration of the Oracle listener. Unauthorized administration of the listener could lead to DoS exploits, loss of connection audit data, unauthorized reconfiguration, or other unauthorized access. This is a Category I finding because privileged access to the listener is not restricted to authorized users.
The check content: If a listener is not running on the local database host server, this check is not a finding. For Windows hosts, view all Windows services with TNSListener embedded in the service name in the format Oracle[ORACLE_HOME_NAME]TNSListener. View the STIGVIEWER for Unix hosts.
The fix text states that by default, Oracle Net Listener permits only local administration for security reasons. The listener can be administered only by the user who started it, enforced through local operating system authentication. For example, if user1 starts the listener, then only user1 can administer it. The super user is the only exception. Remote administration of the listener must not be permitted. If required, granting secure remote access to the Oracle DBMS server and performing local administration is preferred.
The CCI is CCI-000366: The organization implements the security configuration settings (NIST SP 800-53 :: CM-6 b).
π‘ Why this matters: Unauthenticated listener administration is a severe risk. An attacker could stop the listener (DoS) or overwrite audit logs to hide malicious activity.
π Definition β Oracle Listener: A network service that listens for incoming client connections to the Oracle database.
π Rule: Require administration authentication for Oracle Listener β Prevents unauthorized control of the listener service.
π Example: If an Oracle listener allows remote administration without authentication, an attacker on the network could issue lsnrctl stop to stop the database listener, causing a denial of service. The fix enforces local OS authentication so only the user who started the listener (or superuser) can administer it.
Topic no 76: Case Study Security Hardening β MS SQL
This case study is based on the CIS Benchmarks for MS SQL Server 2012 (September 30, 2016, 73-page PDF). The specific rule is 2.14 Ensure 'sa' Login Account has been renamed (Scored) (Profile applicability: Level 1 database engine).
The description explains that the sa account is a widely known and often widely used SQL Server account with sysadmin privileges. The rationale is that it is more difficult to launch password-guessing and brute-force attacks against the sa account if the username is not known.
The audit procedure uses the following syntax to determine if the sa account is renamed: SELECT name FROM sys.server_principals WHERE sid = 0x01; A name of sa indicates the account has not been renamed.
The remediation is to replace the different_user value within the below syntax and execute rename the sa login: ALTER LOGIN sa WITH NAME = <different_user>;
The impact is that it is not a good security practice to code applications or scripts to use the sa account. If this has been done, renaming the sa account will prevent scripts and applications from authenticating to the database server and executing required tasks or functions. The default value is that the 'sa' account name is 'sa'.
π Definition β sa account: The default system administrator account in Microsoft SQL Server with full sysadmin privileges (SID = 0x01).
π Rule: Rename the 'sa' login account β Hides the well-known privileged account to prevent targeted attacks.
π Example: An attacker knows that most SQL Servers have an 'sa' account. They attempt a brute-force attack on 'sa'. If the account is renamed to 'Admin_DB', the attacker's guess of 'sa' fails, making the attack harder. The fix executes ALTER LOGIN sa WITH NAME = Admin_DB;.
Topic no 77: Security Hardening β Case Study β Oracle
This case study is also based on DISA for Oracle database 11.2g, Release 11 (28 April 2017). The rule is: The Oracle REMOTE_OS_ROLES parameter must be set to FALSE (STIG ID: O112-BP-022000, Severity: CAT I).
The discussion explains that setting REMOTE_OS_ROLES to TRUE allows operating system groups to control Oracle roles. The default value of FALSE causes roles to be identified and managed by the database. If REMOTE_OS_ROLES is set to TRUE, a remote user could impersonate another operating system user over a network connection.
The check content uses SQL*Plus: select value from v$parameter where name = 'remote_os_roles'; If the returned value is not FALSE or not documented in the System Security Plan as required, this is a Finding.
The fix text: Document remote OS roles in the System Security Plan. If not required, disable use of remote OS roles. From SQL*Plus: alter system set remote_os_roles = FALSE scope = spfile; This command sets the parameter to take effect at next system startup.
The CCI is CCI-000366: The organization implements the security configuration settings (NIST SP 800-53 :: CM-6 b).
π‘ Why this matters: Allowing OS roles to control database roles can lead to privilege escalation, where a remote attacker gains database roles they should not have.
π Definition β REMOTE_OS_ROLES: An Oracle parameter that, when TRUE, allows operating system groups to control Oracle database roles remotely.
π Rule: Set REMOTE_OS_ROLES = FALSE β Ensures database roles are managed by the database, not by external OS groups.
π Example: If REMOTE_OS_ROLES=TRUE, a remote attacker who gains access to an OS group like "dba" on the client machine could gain DBA privileges in the Oracle database. The fix sets remote_os_roles=FALSE, so only the database manages role assignments.
β Key Takeaways
The key takeaway is that security hardening follows a standard pattern across different systems: identify a specific vulnerability (like weak SSH protocols, writable shell files, unlimited logs, unauthenticated listeners, default accounts, or OS-controlled roles), understand the risk (DoS, privilege escalation, unauthorized access), audit for compliance using specific commands, and remediate by applying configuration changes. Each case study maps to recognized security frameworks (CIS Benchmarks, DISA STIGs, NIST SP 800-53, Critical Controls), and many vulnerabilities are categorized as CAT I (highest severity), meaning they pose immediate and severe risks. A security professional must know how to read these benchmark documents, perform audits using command-line tools, and apply specific remediation steps for different operating systems and applications.
π§ Quick Revision Questions
- What is the remediation command to ensure SSH Protocol is set to 2 on a Linux system?
- Why must shell files have a mode of 0755 or less permissive on Solaris?
- What specific parameter must be added to logging.properties to prevent a DoS attack via log file exhaustion in Apache Tomcat?
- What is the danger of not requiring administration authentication for the Oracle Listener, and how is it prevented?
- Why should the 'sa' login account be renamed in MS SQL Server, and what SQL command is used to do so?
π Lecture 31 β Case Study Security Hardening β Windows 8
π Overview: This lecture presents a real-world case study of security hardening using the CIS Benchmarks for Windows 8.1. It demonstrates how a specific security configuration recommendationβdisabling automatic sending of memory dumpsβis documented, justified, and implemented, showing students the practical application of security hardening standards in enterprise environments.
ποΈ Topics Covered
This lecture covers a specific CIS Benchmark recommendation (18.9.70.3) for Windows 8.1 security hardening. It examines the benchmark's structure including profile applicability, description of the policy setting, recommended state, rationale for the recommendation, audit procedures, and the registry location where the setting is backed. The lecture demonstrates how to interpret and apply a single security configuration from a comprehensive 891-page security benchmark document.
π Lecture Summary
Topic no 78: Case Study Security Hardening β Windows 8
This section introduces the CIS Benchmarks case study specifically for Windows 8.1. The benchmark document was published on January 31, 2017 and is an extensive 891-page PDF containing hundreds of security recommendations. The lecture focuses on a single recommendation: 18.9.70.3 Ensure 'Automatically send memory dumps for OS-generated error reports' is set to 'Disabled' (Scored).
π Definition β CIS Benchmarks: Consensus-based security configuration guidelines developed by the Center for Internet Security to help organizations harden their systems against attacks.
The benchmark specifies profile applicability for this recommendationβit applies to Level 1 and Level 1 + BitLocker configurations. The description explains that this policy setting controls whether memory dumps generated by the OS during error reporting are automatically sent to Microsoft.
π Example: A Windows 8.1 system experiences a Blue Screen of Death (BSOD). Without this policy, the memory dump containing all RAM contents (including passwords, encryption keys, and sensitive data from running applications) would automatically be uploaded to Microsoft for analysis. With the policy set to Disabled, the user or administrator must manually approve the transmission, preventing potential data leakage.
π‘ Why this matters: Memory dumps are complete snapshots of system memory and can contain highly sensitive information that should never be transmitted automatically to any external party.
The rationale provided is clear: Memory dumps may contain sensitive information and should not be automatically sent to anyone. This emphasizes the security principle of data minimization and controlled disclosure.
π Definition β Memory dump: A complete copy of the contents of computer memory (RAM) at the time of a system crash, which can include passwords, encryption keys, personal data, and application secrets.
The audit procedure instructs administrators to navigate to the UI Path described in the Remediation section of the benchmark to confirm the setting is applied as prescribed. The lecture notes that this group policy setting is backed by the following registry location:
- HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsError Reporting:AutoApproveOSDumps
π Formula: Registry Path β HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsError Reporting:AutoApproveOSDumps = 0 β Disables automatic sending of OS-generated memory dumps for error reports.
Note 1: This policy does not apply to error reports generated by 3rd-party products or additional data other than memory dumps. Note 2: The recommended state for this setting is: Disabled.
β Key Takeaways
The lecture demonstrates that security hardening is a detailed, specific process involving hundreds of configuration decisions documented in comprehensive standards like CIS Benchmarks. A single security settingβdisabling automatic memory dump transmissionβprotects against sensitive information leakage because memory dumps contain complete system memory contents including passwords and encryption keys. The setting is implemented through Group Policy and backed by a specific registry key, and administrators must verify compliance through manual audit. This case study shows how theoretical security principles translate into concrete, measurable configuration controls that can be systematically applied across an enterprise.
π§ Quick Revision Questions
- What is the exact CIS Benchmark recommendation number and title for the Windows 8.1 security setting discussed in this lecture?
- Why should automatic sending of memory dumps to Microsoft be disabled from a security perspective?
- What is the registry location that backs this Group Policy setting, and what value should the registry key have?
- Does this policy apply to error reports generated by third-party products? What are the limits of its applicability?
- Describe the difference between Level 1 and Level 1 + BitLocker profile applicability for this recommendation, based on what is stated in the lecture.
π Lecture 32 β Case Study Security Hardening β Win 10 & MS Exchange
π Overview: This lecture examines real-world security hardening case studies for two major Microsoft systems: Windows 10 and Exchange Server 2016. It demonstrates how to apply specific security configuration benchmarks from authoritative sources like DISA and CIS, focusing on antivirus signature updates and email database retention policies to protect against malware and data loss.
ποΈ Topics Covered
The lecture covers two case studies. First, the Windows 10 hardening case study based on DISA STIG Release 9, focusing on the requirement for daily antivirus signature updates (Rule Title, STIG ID, Severity CAT I). Second, the Microsoft Exchange Server 2016 case study based on CIS Benchmarks, focusing on the setting to not permanently delete mailbox items until the database has been backed up, including its audit and remediation via PowerShell cmdlets.
π Lecture Summary
Topic no 79: Case Study Security Hardening β Win 10
This case study is based on the DISA (Defense Information Systems Agency) STIG (Security Technical Implementation Guide) Release 9 (April 28, 2017) for Windows 10. The specific rule examined is: "The antivirus program must be configured to update signature files on a daily basis." The rule is identified by STIG ID: WN10-00-000046 and has a severity of CAT I (Category I, the highest severity, indicating a critical vulnerability). The discussion explains that virus scan programs are a primary line of defense against the introduction of viruses and malicious code that can destroy data and render a computer inoperable. Updated virus scan data files are essential because constantly changing malware is identified by antivirus software vendors.
π Definition β STIG (Security Technical Implementation Guide): A cybersecurity methodology for standardizing security protocols within networks, servers, computers, and software, published by DISA. π Definition β CAT I (Category I): The highest severity classification for a STIG finding, indicating a vulnerability that can directly allow immediate unauthorized access to a system. π Definition β CCI (Control Correlation Identifier): A standard identifier used to map security controls across different frameworks; here CCI: 000366 maps to "The org implements the security config settings." π Check Content: This requirement is Not Applicable (NA) if McAfee VirusScan Enterprise (VSE) is used, as it will be addressed with the corresponding McAfee VSE STIG. Configurations will vary depending on the product. π Fix Text: Configure the antivirus program to update signature files at least daily. Ensure the updates are occurring on a timely basis and are not more than a week old. π NIST References: NIST SP 800-53 :: CM-6 b; NIST SP 800-53A :: CM-6.1 (iv); NIST SP 800-53 Revision 4 :: CM-6. π‘ Why this matters: This rule is CAT I because outdated antivirus signatures can miss new malware, leaving the entire system exposed to infection and data destruction β making daily updates a critical baseline control.
Topic no 80: Case Study Security Hardening β MS Exchange
This case study is based on the CIS Benchmarks (Center for Internet Security) for MS Exchange Server 2016, a 66-page PDF document dated November 16, 2015. The specific control examined is 2.5 titled: "Set 'Do not permanently delete items until the database has been backed up' to 'True' (Scored)." The profile applicability is Level 1 - Mailbox Services Security. The description states that this setting allows you to ensure that items are not permanently deleted until the database has been backed up. The rationale is that to ensure accidentally deleted items can be recovered, they should not be permanently deleted until the database is backed up.
π Definition β CIS Benchmarks: A set of globally recognized, consensus-based best practices for securely configuring IT systems, developed by the Center for Internet Security.
π Definition β Scored Benchmark: A setting that contributes to a measurable security score; failing to comply reduces the overall security score of the system.
π Audit: Execute the following PowerShell cmdlet and ensure RetainDeletedItemsUntilBackup is set to 'True':
Get-MailboxDatabase <Mailbox Database Name> | fl -property RetainDeletedItemsUntilBackup
π Remediation: To implement the recommended state, execute the following PowerShell cmdlet:
Set-MailboxDatabase <Mailbox Database Name> -RetainDeletedItemsUntilBackup $true
π Impact: The impact of enabling this setting should be minimal. More storage space will be required until any pending items are permanently deleted.
π Default Value: False (items can be permanently deleted before the database backup occurs, risking permanent data loss).
π‘ Why this matters: In Exchange, if an administrator or user accidentally deletes critical emails, this setting ensures those items are recoverable until a full database backup is completed β preventing irreversible data loss.
β Key Takeaways
This lecture demonstrates that security hardening is applied through specific, actionable configuration rules from authoritative benchmarks like DISA STIGs and CIS Benchmarks. For Windows 10, the most critical rule (CAT I severity) is requiring daily antivirus signature updates to defend against rapidly evolving malware, with enforcement through NIST CM-6 configuration management controls. For Exchange Server 2016, a key CIS Benchmark (Level 1) is setting RetainDeletedItemsUntilBackup to True to prevent permanent deletion of mailbox items before a database backup occurs, which is audited and remediated via PowerShell cmdlets. Students must remember that hardening is not generic advice β it involves precise rule IDs (STIG ID WN10-00-000046), severity ratings (CAT I), non-applicability conditions (McAfee VSE exemption), and specific PowerShell commands for implementation and verification.
π§ Quick Revision Questions
- What is the STIG ID and severity level for the Windows 10 rule requiring daily antivirus signature updates?
- Under what condition is the Windows 10 antivirus signature update rule considered "Not Applicable (NA)"?
- What PowerShell cmdlet is used to audit whether the
RetainDeletedItemsUntilBackupsetting is enabled on an Exchange Server 2016 mailbox database? - What is the default value of the
RetainDeletedItemsUntilBackupsetting, and what is the rationale for changing it toTrue? - Which NIST SP 800-53 control family is referenced for the Windows 10 STIG rule, and what is the associated CCI identifier?
π Lecture 33 β Security Hardening β Case Study β AD
π Overview: This lecture examines security hardening through real-world case studies of Active Directory, Internet Explorer, Google Chrome, and Mozilla Firefox. It demonstrates how to apply DISA STIG and CIS Benchmark configurations to reduce attack surfaces and enforce security policies in enterprise environments.
ποΈ Topics Covered
The lecture covers four case studies: Active Directory Domain hardening using DISA STIG Release 8 (Topic 81), Internet Explorer 11 browser hardening using CIS Benchmarks (Topic 82), Google Chrome security configuration using DISA STIG (Topic 83), and Mozilla Firefox hardening using CIS Benchmarks (Topic 84). Each case study provides detailed rule information, check procedures, and remediation steps.
π Lecture Summary
Topic No 81: Security Hardening β Case Study β AD
This section presents a STIG rule for hardening Active Directory domains. The Domain Admins group is a highly privileged group that must be restricted to accounts used exclusively for managing the Active Directory domain and domain controllers. Personnel who are system administrators must log on to Active Directory systems only using accounts with the level of authority necessary. A separation of administrator responsibilities helps mitigate the risk of privilege escalation resulting from credential theft attacks. The check content requires reviewing the Domain Admins group in Active Directory Users and Computers to ensure each Domain Administrator has a separate unique account specifically for managing the domain. If any account in Domain Admins is also a member of other administrator groups (Enterprise Admins, domain member server administrators, or domain workstation administrators), this is a finding. The fix involves creating documentation identifying members and ensuring each has a separate unique account. The CCI (Control Correlation Identifier) CCI-000366 maps to NIST SP 800-53 CM-6, requiring the organization to implement security configuration settings.
π Definition β STIG (Security Technical Implementation Guide): A configuration standard for Department of Defense (DoD) information assurance systems, containing rules with severity ratings (CAT I being most severe) and detailed check/fix procedures.
π Formula: CCI Mapping β CCI-000366 maps to NIST SP 800-53 :: CM-6 b (Configuration Management baseline)
π Example: Rule AD.0002: If a Domain Admin account is also a member of the Enterprise Admins group, this violates the rule and is a CAT I finding requiring immediate remediation.
Topic No 82: Case Study Security Hardening β IE Browser
This section covers CIS Benchmarks case study for Microsoft Internet Explorer 11 from January 12, 2014 (178-page PDF doc). The specific rule is "1.5 Configure 'Do not allow users to enable or disable add-ons' (Not Scored)". This policy setting allows management of whether users can allow or deny add-ons through Add-On Manager. If enabled, users cannot enable or disable add-ons through Add-On Manager, except for add-ons specifically entered into the 'Add-On List' policy setting that allows user management. If disabled or not configured, appropriate controls in Add-On Manager are available to users. The rationale states that users often choose to install add-ons not permitted by an organization's security policy, which can pose significant security and privacy risks. The audit checks the registry key HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\InternetExplorer\Restrictions\NoExtensionManagement. Remediation via Group Policy sets the UI path to Not Configured: Computer Configuration\Administrative Templates\Windows Components\Internet Explorer\Do not allow users to enable or disable add-ons. The default value is Disabled.
π Definition β CIS Benchmark: Consensus-based security configuration guidelines developed by the Center for Internet Security for hardening operating systems, applications, and network devices.
π Example: If an organization enables the "Do not allow users to enable or disable add-ons" policy, employees cannot install unauthorized browser extensions like toolbars or plugins that might exfiltrate data.
π‘ Why this matters: Browser add-ons are a common attack vector; controlling them prevents drive-by downloads and data theft through malicious extensions.
Topic No 83: Security Hardening β Case Study β Chrome
This section covers Google Chrome hardening using DISA STIG Release 8 (April 27, 2017). The rule title is "Session only based cookies must be disabled" (Vuln ID: V-44799, STIG ID: DTBC-0045, Severity: CAT I). The policy allows setting a list of URL patterns specifying sites allowed to set session-only cookies. If this policy is left not set, the global default value from the 'DefaultCookiesSetting' policy or user's personal configuration will be used for all sites. If the 'RestoreOnStartup' policy is set to restore URLs from previous sessions, this policy will not be respected and cookies will be stored permanently for those sites. The check content has a universal method: in omnibox type chrome://policy and verify if the policy CookiesSessionOnlyForUrls exists with any defined values β this is a finding. Windows method involves navigating registry to HKLM\Software\Policies\Google\Google Chrome\Content Settings\CookiesSessionOnlyForUrls. The fix via Windows group policy sets: Policy Path Computer Configuration\Administrative Templates\Google\Google Chrome\Content Settings, Policy Name "Allow session only cookies on these sites", Policy State: Disabled, Policy Value: N/A. The CCI-000166 maps to NIST SP 800-53 AU-10 (non-repudiation), protecting against individuals falsely denying having performed organization-defined actions.
π Definition β Session-only cookies: Temporary cookies that are deleted when the browser session ends, preventing persistent tracking across browsing sessions.
π Example: If an organization disables session-only cookies for all sites, users cannot bypass cookie policies, ensuring all websites store cookies permanently as per organizational security requirements, preventing non-repudiation issues.
Topic No 84: Case Study Security Hardening β Firefox
This section covers CIS Benchmarks case study for Mozilla Firefox from December 31, 2015 (72-page PDF doc). The rule is "3.5 (L2) Enable IDN Show Punycode (Scored)" at Level 2. This feature determines whether all Internationalized Domain Names (IDNs) displayed in the browser are displayed as Punycode or as Unicode. The rationale states that IDNs displayed in Punycode are easier to identify and therefore help mitigate the risk of accessing spoofed web pages. The audit procedure involves: typing about:config in the address bar, typing network.IDN_show_punycode in the filter, and ensuring the preference is set to true. The remediation involves opening the mozilla.cfg file in the installation directory and adding the line: lockPref("network.IDN_show_punycode", true);. The default value is false.
π Definition β Punycode: A standardized encoding system used to represent Internationalized Domain Names (IDNs) in ASCII characters, making visually similar characters (homoglyphs) distinguishable.
π Example: A malicious site might use Cyrillic "Π°" (U+0430) instead of Latin "a" in "apple.com" to create "Π°Ρple.com". Punycode encoding shows xn--pple-43d.com instead, making the spoofing attempt obvious.
π‘ Why this matters: Homograph attacks use visually identical characters from different scripts to create lookalike domains. Punycode display prevents users from being tricked into visiting fake websites.
β Key Takeaways
Security hardening must be applied systematically across all enterprise components, from Active Directory to browsers. The Domain Admins group must contain only accounts dedicated exclusively to domain management, with strict separation of duties to prevent privilege escalation. Browser hardening controls (add-ons, cookies, and domain display) are critical because browsers are primary attack surfaces for credential theft and malware delivery. STIG rules and CIS Benchmarks provide standardized, auditable configurations with clear severity ratings, check procedures, and remediation steps. Understanding the CCI mapping to NIST SP 800-53 controls helps align hardening with broader compliance frameworks.
π§ Quick Revision Questions
- What is the severity rating of STIG rule AD.0002, and what specific violation does it address regarding Domain Admins group membership?
- How does enabling the IE "Do not allow users to enable or disable add-ons" policy help mitigate security risks from browser extensions?
- What is the registry path to audit the Chrome "CookiesSessionOnlyForUrls" policy on Windows systems?
- Why does enabling Punycode display (network.IDN_show_punycode=true) in Firefox help prevent spoofing attacks?
- What is the CCI identifier for the Chrome rule DTBC-0045, and which NIST SP 800-53 control does it map to?
π Lecture 34 β Security Hardening β Case Study β FW
π Overview: This lecture examines a specific case study in security hardening by analyzing a Firewall STIG (Security Technical Implementation Guide) from DISA. It demonstrates how to read and apply STIG requirements to protect a network against common denial-of-service attacks, using real-world vulnerability identifiers and remediation steps.
ποΈ Topics Covered
The lecture examines the DISA Firewall STIG, Release 22, dated 28 April 2017, using the STIGViewer window. It details a specific rule (Rule Title, Vuln ID, STIG ID, Severity) requiring protection against denial of service attacks. The discussion explains SYN-flood attacks and ping sweeps, then covers check content for verifying compliance and fix text for remediation.
π Lecture Summary
STIGVIEWER WINDOW
General Information
The lecture presents a specific firewall STIG rule. The Rule Title states: "The device must be configured to protect the network against denial of service attacks such as Ping of Death, TCP SYN floods, etc." The Vuln ID is V-3156, the STIG ID is NET0375, and the Severity is CAT II (meaning a significant risk that requires attention but is not catastrophic).
π Definition β STIG (Security Technical Implementation Guide): A standardized security configuration document from DISA (Defense Information Systems Agency) that specifies hardening requirements for devices and systems. π‘ Why this matters: STIGs are the authoritative source for securing government and military systems, and their principles apply broadly to enterprise security.
Discussion
The discussion section explains two attack types. A SYN-flood attack is a denial-of-service attack where the attacker sends a huge number of "please-start-a-connection" packets (TCP SYN packets) and then nothing else. This causes the attacked device to be overloaded with open sessions pending completion of the three-way handshake, eventually causing it to crash. A ping sweep (also known as an ICMP sweep) is a basic network scanning technique used to determine which of a range of IP addresses map to live hosts (computers) by sending ICMP echo requests.
Check Content
The Check Content provides the verification procedure. It instructs: "Review the device configurations to determine if denial of service attacks are guarded against. If the device is not configured to mitigate denial of service attacks, this is a finding."
π Example: An auditor reviews a firewall's configuration. They find no SYN flood protection or ICMP rate-limiting enabled. According to the check content, this is a "finding" (a non-compliance issue that must be documented and fixed).
Fix Text
The Fix Text provides the remediation steps. It states: "If the firewall supports SYN-flood or ping sweep protection then enable these features. If the firewall does not support these features, enable the security features on the router to protect the network from these attacks."
π Example: A system administrator looks at the firewall's capabilities. If it has a "SYN flood protection" toggle, they enable it. If the firewall lacks this feature, they go to the network router and enable TCP intercept or similar router-based protection.
CCI (Control Correlation Identifier)
The lecture notes CCI as "Misc info" β meaning it provides a cross-reference to a master control catalog used for compliance tracking, but the specific details are beyond the scope of this lecture.
β Key Takeaways
A STIG rule is structured into five critical sections: General Information (Rule Title, Vuln ID, STIG ID, Severity), Discussion, Check Content, Fix Text, and CCI. Severity levels (like CAT II) indicate the criticality of the vulnerability, driving prioritization for remediation. The Check Content tells you exactly what to verify, while Fix Text gives you the exact steps to resolve non-compliance. When a firewall lacks native protection (e.g., against SYN floods or ping sweeps), the solution is to enable equivalent security features on an upstream router. Understanding these five sections enables a security professional to read, interpret, and implement any STIG requirement systematically.
π§ Quick Revision Questions
- What are the five standard sections of a STIG rule as shown in this lecture?
- What is the difference between a SYN-flood attack and a ping sweep?
- According to the Fixed Text, what should you do if the firewall does not support SYN-flood protection?
- What does a "finding" mean in the context of Check Content?
- What does the severity "CAT II" indicate about the importance of this rule?
Here is the summary for Lecture 35 based on your text, following the exact format you provided.
π Lecture 35 β Security Hardening β Case Study β Switch
π Overview: This lecture examines a specific case study from the DISA STIG (Security Technical Implementation Guide) for Layer 2 switches. It focuses on a critical port security rule that requires a switchport to shut down upon detecting a MAC address violation, explaining the vulnerability, the required configuration, and the severity of non-compliance.
ποΈ Topics Covered
The lecture covers the specifics of a single STIG rule from the "Layer 2 Switch STIG, DISA, Release 20, 28 Oct 2016". It details the rule's title, vulnerability ID, STIG ID, and severity rating of CAT III. It also includes a discussion of the Port Security feature's behavior, the required "shutdown" action for violations, and the specific Cisco IOS command to implement this security hardening measure.
π Lecture Summary
[No Section Heading Provided - Content is the lecture itself]
The lecture presents a case study based on a specific rule from the DISA STIG. The IAO (Information Assurance Officer) is responsible for ensuring all switchports are configured with MAC port security. The key requirement is that the switchport must be configured to shutdown upon receiving a frame with a layer 2 source address that does not match the configured or dynamically learned address. This is identified as Vuln ID: V-18565 and STIG ID: NET-NAC-032, with a severity of CAT III (Category III).
The Port Security feature functions by remembering the Ethernet MAC address connected to a specific switch port. It then restricts communication on that port exclusively to that MAC address. If any other MAC address attempts to communicate through the port, port security disables the port by placing it in an error-disabled state and sending an SNMP trap notification.
π‘ Why this matters: This rule is a direct defense against MAC address flooding attacks and unauthorized device connections. By forcing the switchport to "shutdown" on a violation, it immediately stops the attack or unauthorized access, providing a robust security boundary.
π Definition β Port Security: A switch feature that restricts input to an interface by limiting and identifying the MAC addresses of the stations allowed to access the port.
π Definition β DISA STIG: The Defense Information Systems Agency Security Technical Implementation Guide; a standard for securing information systems and networks.
π Definition β CAT III (Category III): A severity classification in the STIG framework for vulnerabilities that result in the loss of confidentiality, availability, or integrity, but are not considered as critical as CAT I or II.
π Required Action/Command: switchport port-security violation shutdown
β This specific interface command forces the switchport to enter the error-disabled state and send an SNMP trap if it receives a frame with a source MAC address that violates the port's configured security settings.
π Example: A network administrator configures port security on interface Gi0/1, manually specifying the allowed MAC address as aaaa.bbbb.cccc. If an attacker connects a device with MAC address 1111.2222.3333 and sends a frame, the switch will place Gi0/1 into an error-disabled state and send an SNMP trap to the network management system. The port will remain down until manually re-enabled by an administrator.
β Key Takeaways
A student must remember that this lecture details a specific STIG rule requiring a "shutdown" action for MAC port security violations on switchports. This is a network hardening technique that defends against MAC address flooding and unauthorized device access. The core command is switchport port-security violation shutdown, which immediately places the port in an error-disabled state and sends an SNMP trap. This action is classified as a CAT III vulnerability if not implemented, meaning it has a moderate impact on security. The ultimate goal is to ensure that only authorized MAC addresses can communicate through a given switchport.
π§ Quick Revision Questions
- What is the specific action that the STIG rule V-18565 requires a switch to take when a MAC address violation occurs? (The switchport must shutdown/place the interface into an error-disabled state.)
- What is the exact Cisco IOS command used to configure this security hardening rule?
(
switchport port-security violation shutdown) - What two actions does the switch perform when a port violation occurs under this configured rule? (It places the interface into the error-disabled state and sends an SNMP trap notification.)
- What is the primary purpose of configuring MAC port security on a switchport? (To remember the Ethernet MAC address connected to the port and allow only that address to communicate.)
- What is the severity level (Category) assigned to this STIG rule (NET-NAC-032)? (CAT III)
π Lecture 36 β Case Study Security Hardening β Cisco IOS 15
π Overview: This lecture examines the CIS Benchmark case study for Cisco IOS 15 routers, focusing on security hardening recommendations. It demonstrates how to apply specific configuration controlsβsuch as OSPF MD5 authenticationβto enforce enterprise security policies and protect routing protocol exchanges between network devices.
ποΈ Topics Covered
The lecture first discusses a fix text for configuring a port to shut down when insecure hosts are connected. It then presents Topic No 87: Case Study Security Hardening β Cisco IOS 15, covering the CIS Benchmarks case study for Cisco routers running IOS 15M. The main content details the specific benchmark 3.3.2.2, which requires setting 'ip ospf message-digest-key md5' as a scored configuration item, including its profile applicability, description, rationale, audit procedure, remediation steps, impact, and default value.
π Lecture Summary
Fix Text
Configure the port to shutdown when insecure hosts are connected to the wall jack.
Topic No 87: Case Study Security Hardening β Cisco IOS 15
This section introduces a case study on security hardening for Cisco routers running IOS 15M based on the CIS Benchmarks document dated June 30, 2015 (151 pages PDF). The focus is on a specific benchmark item: 3.3.2.2 Set 'ip ospf message-digest-key md5' (Scored).
π Definition β CIS Benchmark: A set of security configuration guidelines published by the Center for Internet Security for hardening systems.
The benchmark specifies:
- Profile applicability: Level 2
- Description: Enable Open Shortest Path First (OSPF) Message Digest 5 (MD5) authentication.
- Rationale: This is part of the OSPF authentication setup.
- Audit: Verify the appropriate MD5 key is defined on the appropriate interface(s) using the command:
hostname#sh run int {interface} - Remediation: Configure the appropriate interface(s) for Message Digest authentication using:
hostname(config)#interface {interface_name}hostname(config-if)#ip ospf message-digest-key {ospf_md5_key-id} md5 {ospf_md5_key}
- Impact: Organizations should plan and implement enterprise security policies that require rigorous authentication methods for routing protocols. Configuring the proper interface(s) for 'ip ospf message-digest-key md5' enforces these policies by restricting exchanges between network devices.
- Default Value: Not set
π‘ Why this matters: OSPF authentication prevents unauthorized routers from injecting false routing information into the network, which could cause traffic redirection, denial of service, or man-in-the-middle attacks.
β Key Takeaways
Students must remember that the CIS Benchmark for Cisco IOS 15 provides scored security hardening recommendations, with benchmark 3.3.2.2 specifically requiring OSPF MD5 authentication on router interfaces. The default value for OSPF MD5 authentication is not set, meaning routers are vulnerable unless explicitly configured. The remediation involves two commands on the appropriate interface: one to enter interface configuration mode, and one to set the MD5 key with an ID and key value. The audit command verifies the configuration by showing the running interface configuration. This hardening measure enforces enterprise security policies by authenticating routing protocol exchanges between network devices.
π§ Quick Revision Questions
- What is the exact CIS benchmark number for requiring OSPF MD5 authentication in the Cisco IOS 15 case study?
- What is the default value for 'ip ospf message-digest-key md5' on a Cisco IOS 15 router?
- What two commands are needed to configure OSPF MD5 authentication on a Cisco interface?
- How can an administrator verify that the appropriate OSPF MD5 key is configured on an interface?
- Why does the CIS benchmark recommend configuring OSPF MD5 authentication rather than leaving it unset?