📘 Lecture 23 — What Does “Box Security” Mean? & Best Approach: IT Enterprise Security
📖 Overview: This lecture critiques the common industry practice of “box security,” where organizations purchase security devices without proper planning or staffing. It then introduces the 4-layer security transformation model as a more effective and practical approach to building a strong security posture, especially in environments with weak security awareness.
🗂️ Topics Covered
The lecture first defines “box security” and explains its prevalence, highlighting that security is a combination of people, process, and technology and that purchased devices are often underutilized. It then details the challenges with this approach, including staff shortages and lack of planning. Finally, it presents the 4-layer security transformation model as the best approach, covering security hardening, vulnerability management, security engineering, and security governance.
📝 Lecture Summary
Topic no 46: What Does “Box Security” Mean?
“Box Security” refers to a common industry approach, especially in larger organizations, where the solution for every security challenge is a dedicated device or “box.” Examples include boxes for email security, web security, firewalls (FW), IPS (Intrusion Prevention Systems), APT attack prevention (Advanced Persistent Threat), DDOS prevention (Distributed Denial of Service), Network DLP (Data Loss Prevention), and Network Forensics. However, this approach is flawed because security is a combination of people, process, and technology. Industry observation shows that most devices are not used to their full capability or capacity after purchase, with a case in point being SIEM (Security Information and Event Management) or DB security (Database Security) solutions.
The lecture emphasizes that “box security” is not a silver bullet. Although many devices and boxes are required, they do not ensure a good security posture, and this approach is unfortunately promoted by vendors who have equipment to sell. Other challenges include a shortage of IT and security staff, and the training and skills required to operate sophisticated devices and features. To mitigate these issues, device objectives and high-level-design (HLD) should be planned prior to commissioning, a minimum operational baseline and configuration should be documented in SOP (Standard Operating Procedure), and device feature set and configuration audits should be conducted on a periodic basis (annually).
💡 Why this matters: This topic highlights that simply buying security tools is ineffective without proper planning, staffing, and process integration. It sets the stage for the more holistic model that follows.
Topic no 47: Best Approach: IT Enterprise Security
The best approach is the 4-layer security transformation model, which is the only way to effectively and practically address security posture. This model is tried and tested for geographies where the overall security awareness and posture is weak. The four layers are:
- Security hardening: This addresses the security configuration of all IT assets which security “boxes” won’t do for you. It is the foundational layer.
- Vulnerability management: This involves scanning to inspect patching of IT assets and is considered essential. It is supported by security engineering and security governance.
- Security engineering: This is where more serious investments may be made once layers 1 and 2 have been completed satisfactorily (or are being addressed). It focuses on architectural design and integration.
- Security governance: This ensures the proper utilization (as intended), ROI (Return on Investment), and audits of purchased devices & solutions. It also ensures configurations are as per design and SOPs.
🔑 Definition — 4-layer security transformation model: A hierarchical framework that builds security posture from the ground up, starting with configuration (hardening) and vulnerability management before progressing to advanced engineering and governance. 📐 Order of Layers: Security Hardening (Layer 1) → Vulnerability Management (Layer 2) → Security Engineering (Layer 3) → Security Governance (Layer 4). The model is sequential, meaning layers 1 and 2 must be addressed before significant investment in layers 3 and 4. 📌 Example: An organization first hardens all its servers and endpoints (Layer 1), then sets up a scanning schedule to ensure all patches are applied (Layer 2). Only after this secure baseline is established does it invest in a new SIEM solution, ensuring the engineering (Layer 3) is based on a clean environment. Finally, governance (Layer 4) audits the SIEM’s configuration and usage to confirm it meets the original objectives and provides a return on investment.
🔑 Definition — Security hardening: The process of configuring IT assets (e.g., servers, workstations, network devices) to reduce their attack surface by disabling unnecessary services, setting strong passwords, and applying secure baseline configurations. 🔑 Definition — Vulnerability management: The continuous process of identifying, classifying, prioritizing, and remediating vulnerabilities in IT assets, typically through automated scanning and patching.
⭐ Key Takeaways
The lecture’s core message is that “box security” is an incomplete and often ineffective approach because it ignores the crucial elements of people, process, and planning, leading to underutilized devices and a false sense of security. The key to a strong security posture is the 4-layer security transformation model, which builds security from the ground up, starting with fundamental hardening and vulnerability management before adding advanced technologies. A student must remember that security devices are tools, not solutions, and their effectiveness depends entirely on the organizational maturity, staffing, and processes surrounding them. Finally, the sequence of the 4-layer model is critical—layers 1 and 2 must be addressed before significant investment in layers 3 and 4, and governance (Layer 4) is essential for ensuring ROI and proper use.
🧠 Quick Revision Questions
- What is the core problem with the “box security” approach, and why does it not ensure a good security posture?
- List the four layers of the security transformation model and explain their correct sequence.
- Why is it important to plan device objectives and a high-level design (HLD) before commissioning a security device?
- What is the primary goal of the “security hardening” layer, and how does it differ from “vulnerability management”?
- What is the role of “security governance” in the 4-layer model, especially concerning previously purchased devices?
📘 Lecture 24 — DR In Enterprise Architecture – Part 1
📖 Overview: This lecture introduces Disaster Recovery (DR) and Business Continuity (BC) as critical security disciplines. It defines DR, its three-step process, and DR plan components, then distinguishes DR from BC, explaining BC management and planning. The lecture emphasizes the importance of RTO and RPO as key metrics in enterprise DR architecture.
🗂️ Topics Covered
The lecture covers the definition of disaster and disaster recovery, the three-step failover process, the DR plan checklist, the definition of business continuity and business continuity management, the BC plan, and then begins the topic of DR in enterprise architecture with detailed coverage of DR plan components, RTO, and RPO.
📝 Lecture Summary
Topic no 48: What Is Disaster Recovery (DR)?
A disaster is any significant event that causes disruption of information technology processing facilities, affecting business operations. Disaster Recovery (DR) is an area of security that allows an organization to maintain or quickly resume mission-critical IT functions following a disaster. The invocation of a DR failover to a DR site can be caused by natural disasters (flood, earthquake, lightning, storm) or disasters caused by human actions (riot, fire, terrorist act).
Disaster Recovery is an IT function, whereas Business Continuity (BC) addresses keeping all essential aspects of a business functioning despite disruptive events; DR is a part of BC.
The DR process involves three steps:
- Failover to the DR site (DR invocation)
- Restoration of the services/facilities on the primary site
- Recovery (switchover back to the primary site)
A DR plan is a documented, structured approach to dealing with unplanned incidents.
A DR plan checklist includes: scope of activity, gathering relevant network infrastructure documents, identifying the most serious threats/vulnerabilities and critical assets, identifying current DR strategies, identifying the emergency response team, management review & approval, testing the plan (drill), updating the plan, and implementing a DR plan audit.
Topic no 49: What is Business Continuity (BC)?
Business Continuity (BC) is the capability of the organization to continue delivery of products or services at acceptable predefined levels following a disruptive incident (Source: ISO 22301:2012). Business Continuity Management is a holistic management process that identifies potential threats and their impacts to business operations, and provides a framework for building organizational resilience with an effective response that safeguards interests of key stakeholders, reputation, brand, and value-creating activities (Source: ISO 22301:2012).
A BC plan is a document consisting of critical information an organization needs to continue operating during an unplanned event. The BCP should state essential functions of the business, identify which systems and processes must be sustained, and detail how to maintain them, taking into account any possible business disruption.
Topic no 50: DR In Enterprise Architecture – Part 1
DR considerations include the DR plan, RTO, and RPO. A comprehensive DR plan includes: a disaster recovery policy statement, plan overview, main goals, key personnel/DR team contact info, emergency response actions, a diagram of the entire network and recovery site, directions to the recovery site, a list of recovery software/systems, sample templates for technology recoveries, insurance coverage summary, actions for financial/legal issues, and ready-to-use forms.
🔑 Definition — RTO (Recovery Time Objective): The maximum amount of time, following a disaster, for an organization to recover files from backup storage and resume normal operations; the maximum amount of downtime an organization can handle.
📐 Formula: RTO = Maximum acceptable downtime → If an organization has an RTO of two hours, it cannot be down for longer than that.
📌 Example: An organization with an RTO of 2 hours must fully recover from backup and resume normal operations within 2 hours of a disaster.
🔑 Definition — RPO (Recovery Point Objective): The maximum age of files that an organization must recover from backup storage for normal operations to resume after a disaster; determines the minimum frequency of backups.
📐 Formula: RPO = Maximum acceptable data loss → Determines how frequently backups must occur.
📌 Example: If an organization has an RPO of four hours, the system must back up at least every four hours. This means in a disaster, no more than 4 hours of data can be lost.
💡 Why this matters: RTO and RPO are critical metrics that directly impact business risk and cost. A shorter RTO (faster recovery) and shorter RPO (less data loss) require more expensive infrastructure and more frequent backups.
Topic no 51: DR In Enterprise Architecture – Part 2
DR considerations include DR facility, DR drills & testing, DR testing checklist, and BC plan alignment.
A DR facility involves location, media circuits and backup circuits, power and environment, IT data center design based on the DR plan, and operations & maintenance.
DR drills & testing should follow frequency and execution as per IT policy, with a minimum of twice a year and preferably quarterly for critical business requirements. Backup testing is also included.
A DR testing checklist includes: secure management approval and funding, provide detailed test information, ensure full test team availability, avoid conflicts with other tests, confirm correct test scripts, verify test environment readiness, schedule a dry run, be ready to halt the test if needed, have a scribe take notes, complete an after-action report, and use test results to update the DR plan.
For BC plan alignment: DR is under IT ownership, whereas BC is under business operations ownership. DR is part of overall BC, and both plans must integrate and align seamlessly.
⭐ Key Takeaways
The most critical concept is that Disaster Recovery (DR) is an IT function focused on restoring mission-critical IT systems after a disaster, while Business Continuity (BC) is a broader business operations function that keeps all essential business aspects running. RTO (Recovery Time Objective) defines maximum acceptable downtime, and RPO (Recovery Point Objective) defines maximum acceptable data loss, both directly determining backup frequency and recovery infrastructure costs. DR follows a three-step process: failover to DR site, restoration of primary site, then recovery (switchback). A successful DR program requires a comprehensive DR plan, proper DR facility design, regular drills at least twice yearly, and seamless integration with the BC plan. Both plans must align under separate ownership — IT for DR and business operations for BC.
🧠 Quick Revision Questions
- What is the difference between Disaster Recovery (DR) and Business Continuity (BC)?
- What are the three steps in the DR process?
- Define RTO and RPO. If an organization has an RPO of 4 hours, what does that mean for backup frequency?
- According to IT policy, what is the minimum recommended frequency for DR drills?
- Which ownership — IT or business operations — is responsible for the Disaster Recovery plan, and which is responsible for the Business Continuity plan?
📘 Lecture 25 — Role Of An IT Asset In Enterprise Security & How To Determine Security Posture?
📖 Overview: This lecture defines what constitutes an IT asset in an organization and explains the roles of asset and risk owners, as well as acceptable use policies for IT assets. It then provides a comprehensive set of diagnostic questions to assess an organization’s overall security posture, covering policies, hardening, vulnerability management, and disaster recovery.
🗂️ Topics Covered
The lecture first covers the definition of an IT asset (hardware, software, information, human resource, or facility), the distinct roles of asset owner and risk owner, and the concept of acceptable use for company assets like laptops, mobiles, and data. It then transitions to a detailed checklist of questions that help determine an enterprise’s security posture, including policy existence, security culture, team size, hardening standards, vulnerability scanning (VM), licensing, penetration testing, policy maturity, and disaster recovery drills.
📝 Lecture Summary
Topic no 52: Role Of An IT Asset In Enterprise Security
An IT asset is defined as any resource—such as hardware, software, information, human resource, or facility—that is owned or utilized by an organization for its IT processing. Understanding the different types of IT assets is crucial for effective security management. The asset owner is the person in the organization responsible for managing a specific asset, such as a laptop. 💡 Why this matters: Clear ownership ensures accountability for asset lifecycle and security.
🔑 Definition — IT asset: any resource such as hardware, software, information, human resource, or facility owned or utilized by the organization for IT processing.
🔑 Definition — Asset owner: a person in the organization responsible for managing an asset (e.g. for a laptop).
🔑 Definition — Risk owner: manages risks associated with the IT asset, is authorized to make decisions associated with managing risks, and is in a management position.
The lecture also defines Acceptable Use (Of IT Assets), which applies to laptops, mobiles, web browsing, email usage, servers, and company data. These policies govern how employees may use organizational resources.
📌 Example: An acceptable use policy for a company laptop would specify that it cannot be used for personal streaming services, ensuring the asset is used only for business purposes.
Topic no 53: How To Determine Security Posture?
To determine an organization’s security posture, a set of diagnostic questions must be asked. These questions cover multiple dimensions of security readiness and maturity. The first set of questions addresses policy and culture: Is there an information security policy? What is the organization’s security culture and tone at the top? Is there a clearly designated responsibility for security?
Next, the lecture asks about the security team: How many staff are in the security team (suggesting 10% as a benchmark) and what are their roles? Critical technical questions follow: Has security hardening been done on IT assets? Which standard was used for hardening (e.g., CIS, NIST)? Is there an internal vulnerability management (VM) program? What is the frequency of VM scanning?
The assessment continues with software compliance: Are all licensed software used for OS, databases, and programs? When was the last time a penetration test was conducted by a third party? The lecture also probes the maturity of system security policies pushed through Active Directory (AD) or Group Policy (GP). Finally, it asks about disaster recovery: Is there a DR and/or backup site? When was the last time a DR drill was performed?
📌 Example: If an organization has no internal VM program and has never performed a third-party penetration test, its security posture would be considered very low maturity, indicating high risk.
⭐ Key Takeaways
The most critical concepts from this lecture are: First, an IT asset encompasses hardware, software, information, human resources, and facilities, and each asset should have a designated asset owner and risk owner with distinct responsibilities. Second, acceptable use policies must be established for all major asset types including laptops, mobiles, email, and company data. Third, assessing an organization’s security posture requires a systematic checklist covering policy existence, security culture, team size (with a 10% staffing benchmark), hardening standards, vulnerability management (including scanning frequency), software licensing, third-party penetration testing, policy maturity through AD/GP, and disaster recovery readiness with regular DR drills.
🧠 Quick Revision Questions
- What are the five categories of resources that constitute an IT asset according to this lecture?
- What is the key difference in authority and responsibility between an asset owner and a risk owner?
- List four specific types of IT assets for which organizations should define acceptable use policies.
- What percentage of staff working in the security team does the lecture suggest as a benchmark for evaluating security posture?
- Name three technical questions that should be asked to evaluate an organization’s security posture related to vulnerability management, penetration testing, and disaster recovery.
📘 Lecture 26 — Driving Successful Security Transformation & Revisit Of Security Transformation Model
📖 Overview: This lecture explains what makes security transformation projects succeed or fail, focusing on critical success factors like board-level sponsorship and resource allocation. It then revisits the security transformation model, detailing the two essential technical processes—hardening and patching—that protect IT assets from vulnerabilities and attacks.
🗂️ Topics Covered
The lecture covers critical success factors for security transformation projects, including board-level buy-in, regular executive reviews, and resource allocation. It then introduces the security transformation stage from Chapter 3, explaining the concepts of security hardening (reducing system vulnerability surface) and patching (fixing software/firmware vulnerabilities), along with their differences and complementary roles.
📝 Lecture Summary
Topic no 54: Driving Successful Security Transformation
Successful security transformation projects depend on several critical factors that determine their outcome from the start. The most important factor is board-level buy-in and sponsorship, which ensures that security initiatives have top-down support and authority. Additionally, regular Board or Executive management project reviews and decisions keep the project aligned with organizational priorities and allow for timely adjustments. Finally, the allocation of sufficient priority & resources ensures that the project has the funding, personnel, and attention it needs to succeed.
💡 Why this matters: The lecture emphasizes that "projects either fail or succeed before they begin!" This means that without proper sponsorship, structure, strategy, and strong project management, even technically sound security initiatives are likely to fail. Success is determined by organizational commitment and governance, not just technical measures.
Topic no 55: Revisit Of Security Transformation Model
Security Hardening IT assets such as hardware and software come with default (insecure) configurations which become the basis for attacks. A typical case in point is the default username and password combination of "admin, admin" which attackers can easily exploit. Hardening makes a system more secure by reducing its surface of vulnerability, which is larger when a system performs more functions; in principle, a single-function system is more secure than a multipurpose one.
🔑 Definition — Hardening: Additional steps beyond patching to limit the ways a hacker or malware could gain entry, accomplished by turning on only the ports and services required, secure configuration of services, and additional steps to limit system access.
Patching Patching involves fixing vulnerabilities (which may be exploited by malware or attackers) in software or firmware with vendor-released patches (auto or manual updates). Patches are also called fixes. Patching considerations include: vendors release a patch when they become aware of a vulnerability; patches may be rolled up into a release; off-the-shelf software works well but testing is required for customized instances.
🔑 Definition — Patching: The process of applying vendor-released updates to fix vulnerabilities in software or firmware that could be exploited by malware or attackers.
Relationship Between Hardening and Patching Note that both hardening and patching are required. Hardening prevents existing and future vulnerabilities by tightening configuration, while patching is more of a vendor-driven process but essential nonetheless. They serve complementary roles: hardening proactively reduces the attack surface, while patching reactively fixes known vulnerabilities.
📐 Formula: Security Hardening + Patching = Comprehensive Vulnerability Management → Hardening addresses configuration weaknesses proactively; patching addresses software flaws reactively; both are necessary for complete protection.
⭐ Key Takeaways
Students must remember that successful security transformation depends more on organizational factors (board sponsorship, regular reviews, resource allocation) than on technical measures alone. Both hardening and patching are essential and complementary: hardening reduces the attack surface by tightening default configurations and disabling unnecessary services, while patching fixes known vulnerabilities through vendor updates. A single-function system is inherently more secure than a multipurpose one because it has a smaller vulnerability surface. Remember that "projects either fail or succeed before they begin" — preparation and organizational commitment are the foundation of success. Finally, the default "admin, admin" example illustrates how insecure default configurations can become the entry point for attacks.
🧠 Quick Revision Questions
- What are the three critical factors for successful security transformation projects?
- Why do projects "either fail or succeed before they begin"?
- What is the difference between hardening and patching?
- Why is a single-function system considered more secure than a multipurpose one?
- What is the typical example given for insecure default configurations in IT assets?
📘 Lecture 27 — Security Hardening Strategy
📖 Overview: This lecture introduces the concept of security hardening as a practical, priority-driven approach to securing IT assets. It emphasizes the importance of separating quick, baseline security measures from more complex security engineering tasks to achieve rapid risk reduction.
🗂️ Topics Covered
The lecture covers the definition and importance of security hardening as a distinct initial step in the security implementation process. It explains the role of priority in managing numerous assets, introduces the concept of the Minimum Security Baseline (MSB), and describes the "cascade" approach for progressive security improvements.
📝 Lecture Summary
Security Hardening Strategy
Depending on the size and type of the organization, there may be dozens, hundreds, or even thousands of IT assets to secure. Priority is a key factor in all security undertakings. You must prioritize what is most important and needs to be done first, then cascade as you go along.
💡 Why this matters: Without prioritization, security teams can become overwhelmed by the sheer volume of assets, leading to analysis paralysis and no actual security improvements.
Separate Security Engineering from Security Hardening
It is critical to separate security engineering (Step 3) from security hardening (Step 1). Security engineering requires more thorough working and will slow down the security implementation. Therefore, organizations should do the low hanging fruit first, which is security hardening.
🔑 Definition — Security Hardening: The process of securing a system by reducing its surface of vulnerability, typically by applying basic, quick, and obvious security measures.
🔑 Definition — Security Engineering: A more thorough and complex process of designing and building security into systems from the ground up, requiring more time and analysis.
Minimum Security Baseline (MSB)
The Minimum Security Baseline (MSB) refers to the obvious assets which need to be secured and the threshold which is the minimum expectation from the security program.
🔑 Definition — Minimum Security Baseline (MSB): The set of basic, essential security controls and configurations that must be applied to all assets as the starting point for security, representing the lowest acceptable level of protection.
📌 Example: An organization with 500 workstations might identify that all of them need antivirus software, password policies, and disabled guest accounts. The MSB would be deploying these three controls across all 500 machines before moving on to more complex security measures like firewall rule optimization or intrusion detection tuning.
⭐ Key Takeaways
The most critical understanding from this lecture is that security hardening must be separated from security engineering to avoid slow implementation. Priority is the key factor when dealing with large numbers of assets, and the "cascade" approach allows for progressive security improvements. The Minimum Security Baseline (MSB) represents the obvious, essential security controls that must be applied first as the minimum expectation. Organizations should always focus on the "low hanging fruit" — quick, easy wins — before tackling complex security engineering tasks.
🧠 Quick Revision Questions
- Why is it important to separate security hardening from security engineering?
- What does the term "cascade" mean in the context of the security hardening strategy?
- What is the Minimum Security Baseline (MSB) and why is it important?
- Why is priority considered a key factor in security undertakings?
- What does "low hanging fruit" refer to in security implementation?
📘 Lecture 28 — Pre-requisites For Security Hardening
📖 Overview: This lecture explains the essential pre-requisites needed before starting a security hardening project, identifies the key stakeholders involved in conducting security hardening, and introduces the 8-step methodology for standardizing the hardening process. Understanding these foundations ensures a structured, disciplined, and effective approach to improving an organization’s security posture.
🗂️ Topics Covered
The lecture covers five pre-requisites for security hardening: a security program approved, a consultant on board, a project kick-off meeting held, ISMC team identified and their loading communicated, and appraisal linkage of core resources announced by CIO. It then details the roles of IT operations teams, InfoSec team, IT management, consultant, and business stakeholders in conducting hardening. Finally, it introduces the 8-step security hardening methodology, its purpose, benefits, and risks of skipping it.
📝 Lecture Summary
Pre-requisites For Security Hardening
For a successful security transformation project, good planning, organization, and effective project management are essential. Five key pre-requisites must be in place before commencing security hardening.
-
Security program approved – This includes defining the project director, establishing a timeline, agreeing on the general project sequence and strategy, understanding the main players and their roles, and clarifying the project structure.
-
Consultant on board – Expert consultants in security transformation can facilitate project success. They should be third-party and independent, bring a focus on delivering results, and possess strong domain knowledge.
-
Project kick-off meeting held – This ensures all key stakeholders are aware of the project goals & mission, their responsibilities & authority, the success criteria, and the reporting mechanism.
-
ISMC team identified and their loading for this project communicated – The ISMC (Information Security Management Committee) plays a critical role. This ensures cooperation & teamwork, fosters a security leadership culture, and provides clarity on goals.
-
Appraisal linkage of core resources announced by CIO – The broader team is informed, the announcement is made by the CIO (Chief Information Officer), and there is clarity on the evaluation mechanism for performance.
💡 Why this matters: Without these pre-requisites, security projects lack direction, accountability, and executive support, making failure highly likely.
Who Will Conduct The Security Hardening?
Security hardening involves the involvement of various stakeholders, each with distinct responsibilities.
-
IT Operations teams: Study the security controls (e.g., CIS (Center for Internet Security) / DISA (Defense Information Systems Agency) standards), apply the security controls in a pilot/test environment, report the completion of control implementation to ISMC, and assist the InfoSec team with validation.
-
InfoSec team: Conduct validation of security controls implementation, acquire a checklist of controls from the relevant IT team, document the status of controls in the form of a checklist, and forward the validation report to ISMC.
-
IT management: Ensure IT operations teams receive required guidance and support, sign-off on change management requests, and assist with planning downtime and business-related downtime.
-
Consultant or project director: Drives the security program, ensures that strategy is aligned with project objectives, and ensures process and activities are moving at good momentum as per the timeline.
-
Business stakeholders: Provide downtime approvals if required, and help to engage other vendors if applicable.
8 Step Methodology – Security Hardening (1)
The 8-step security hardening methodology is a standardized approach to hardening assets.
Purpose: Many assets need to be hardened at various times, by various teams, for various requirements and projects. This methodology is designed to standardize and follow a consistent approach.
Benefits:
- Provides a clear process for security hardening
- Instills discipline to always follow the same steps
- Helps avoid missing any steps in the process
- Gives the team clarity on what to do and what sequence to follow
If You Skip This Process:
- You will follow a new approach every time
- Every resource has their own method
- Creates dependence on the resource rather than the process
- Complicate rather than simplify
- Leads to divergence in security activities
⭐ Key Takeaways
For a security hardening project to succeed, five pre-requisites must be met: an approved security program, a hired consultant, a completed kick-off meeting, a designated ISMC team, and appraisal linkage announced by the CIO. The actual hardening work involves multiple stakeholders: IT operations apply the controls, InfoSec validates, IT management supports, the consultant drives strategy, and business stakeholders authorize downtime. The 8-step methodology provides a standardized, disciplined approach that prevents reliance on individual resource methods and ensures consistency across all hardening activities. Skipping this methodology leads to divergence, complexity, and process failure. Memorize the five pre-requisites and the roles of each stakeholder group for the exam.
🧠 Quick Revision Questions
- List all five pre-requisites for security hardening as taught in this lecture.
- What is the primary responsibility of the InfoSec team when conducting security hardening?
- What are the three main benefits of using the 8-step security hardening methodology?
- Who is responsible for signing off on change management requests during hardening?
- What is the role of the business stakeholders in the security hardening process?
📘 Lecture 29 — 8 Step Methodology – Security Hardening (2)
📖 Overview: This lecture completes the 8-step methodology for security hardening, detailing the final steps from testing through production deployment. It then provides an in-depth look at two major security benchmark frameworks—CIS Benchmarks and DISA STIGs—including their structure, content examples, and a comparison to guide organizational selection.
🗂️ Topics Covered
The lecture covers steps 5–8 of the security hardening methodology (implement controls on test setup, validate implementation, change management for production, and production deployment with monitoring). It then examines CIS security benchmarks for network devices and operating systems, explores DISA STIGs including their viewer, checklist screens, and specific STIG examples for Windows Server 2012 R2 and firewalls, and concludes with a comparison of CIS vs. DISA and a practical hardening example for Windows Server 2012R2.
📝 Lecture Summary
Topic no 60: 8 Step Methodology – Security Hardening (2)
This lecture continues the 8-step methodology for security hardening. Step 1 involves identifying critical assets and asset owners, creating an asset inventory and infrastructure diagram, examining risks, analyzing assets at a high level to prioritize, establishing a minimum security baseline (MSB), and breaking the work into phases. Step 2 is researching applicable security controls from sources like CIS, DISA, Google searches, and reviewing standards/frameworks such as ISO27001, PCI, OWASP, CSA, NIST, and CIS Top 20, followed by selection of controls. Step 3 creates a checklist of applicable security controls for progress tracking, sharing with the appropriate IT team, and forming a record for controls trail. Step 4 documents controls into a Standard Operating Procedure (SOP), enters the controls set into a draft SOP, defines who will do what when (and briefly how), and gets Department Head agreement and sign-off on the checklist and SOP.
Topic no 61: 8 Step Methodology – Security Hardening (3)
Step 5 involves implementing controls on a test setup by the relevant IT team, updating the checklist and SOP if necessary, and sending the checklist back to the InfoSec team. Step 6 is validation of control implementation by the InfoSec team, requiring an InfoSec resource with relevant domain knowledge, conducting preparation before actual validation (studying controls), and updating the checklist with a status column. Step 7 is the change management process for PRODUCTION, where the ISMC (Information Security Management Committee) receives validation status from the InfoSec team, the relevant department head takes up the change management process and prepares for shifting to PROD, considering rollback, impact, etc. Step 8 implements controls on PROD and monitors closely for 24-48 hours after moving to PROD, with rollback in case of unforeseen circumstances; the IT team SOP is finalized and becomes an operations task.
Topic no 62-65: A Look At CIS Security Benchmarks (1)
The Center for Internet Security (CIS) provides security benchmarks available at https://www.cisecurity.org/cis-benchmarks/. Users fill out details and receive an email with a download link. CIS benchmarks cover mobile devices, network devices, desktop software, and multifunction print devices. A CIS benchmarks example for network devices (dated June 29, 2016, 174 pages PDF) includes control content: profile applicability (e.g., ASA 8.X, ASA 9.X), description, rationale, audit, remediation, default value, and references. For example, control 1.8 (page 88): Session Timeout — Profile applicability: Level 1, Cisco ASA9.X; Description: Sets the idle timeout for a console session before the security appliance terminates it; Rationale: Limiting session timeout prevents unauthorized users from using abandoned sessions to perform malicious activities.
A CIS benchmarks example for operating systems (MS Windows Server 2012-R2, dated January 31, 2017, 760 pages PDF) includes profile applicability with Level 1 and Level 2 profiles. Level 1 items are intended to be practical and prudent, provide a clear security benefit, and not inhibit the utility of the technology beyond acceptable means. Level 2 extends Level 1, intended for environments where security is paramount, acts as a defense in depth measure, but may negatively inhibit utility or performance. Control content includes profile applicability, description, rationale, audit, remediation, impact, default value, and references. For example, control 1.1.2 [L1]: Ensure 'Maximum password age' is set to '60 or fewer days, but not 0' (Scored) — Profile applicability: Level 1 Domain Controller, Level 1 Member Server; Description: defines how long a user can use their password before it expires, values range from 0 to 999 days (0 means password never expires); Audit: Navigate to UI Path in Remediation section and confirm prescribed setting; Default Value: 42 days; Reference: CCE-37167-4 (Common Configuration Enumeration — unique identifiers for common system config issues).
Topic no 66: A Look At DISA STIGs (1)
DISA STIGs (Security Technical Implementation Guides) come from the USA DoD and are the most expansive security benchmarks available, most regularly updated, with an unclassified version available at http://iase.disa.mil/stigs/Pages/index.aspx. There are 425 STIGs available. Resources include a STIGs master list (A-Z) at http://iase.disa.mil/stigs/Pages/a-z.aspx and a STIG viewer at http://iase.disa.mil/stigs/Pages/stig-viewing-guidance.aspx. The STIG viewer can be downloaded, and a STIG library compilation is available. DISA STIGs use a completely different mechanism compared to CIS.
🔑 Definition — STIG: Security Technical Implementation Guide — expansive, regularly updated security benchmarks from the USA DoD.
Topic no 67: A Look At DISA STIGs (2)
STIG content includes: general information (title), discussion, check content, fix text, and CCI (Control Correlation Identifier) references. Checklist screens show: overall totals, target data, role, finding details, and comments. Status options include: Not reviewed, Open, Not a finding, and Not applicable.
Topic no 68: A Look At DISA STIGs (3)
Example: Windows Server 2012 R2 Member Server — Import STIG, V1099 (Lockout duration). Rule Title: The lockout duration must be configured to require an administrator to unlock an account — Severity: CAT II. Discussion: The account lockout feature prevents brute-force password attacks; this parameter specifies the period an account remains locked after failed logon attempts; a value of 0 requires an administrator to unlock the account. Check Content: Verify in Local Group Policy Editor (gpedit.msc) → Local Computer Policy → Computer Configuration → Windows Settings → Security Settings → Account Policies → Account Lockout Policy; if "Account lockout duration" is not set to "0", this is a finding. Fix Text: Configure the policy value for the same path to "0" minutes — "Account is locked out until administrator unlocks it". CCI: NIST SP 800-53 Revision 4 :: AC-7 b.
Topic no 69: A Look At DISA STIGs (4)
Example: Firewall Security Technical Implementation Guide — Vulnerability ID: V-3967; Rule name: The console port does not timeout after 10 mins. General Information: Rule Title: The network devices must time out access to the console port at 10 minutes or less of inactivity; STIG ID: NET1624; Severity: CAT II. Discussion: Terminating idle sessions reduces the window of opportunity for unauthorized personnel to take control of unattended management sessions and frees up resources; setting timeout to 10 minutes or less increases protection for critical network components. Check Content: Review configuration and verify console port session times out after 10 minutes or less of inactivity; if not, this is a finding. Fix Text: Configure the timeout for idle console connection to 10 minutes or less.
Topic no 70: Comparison of CIS Vs DISA
Many controls are common between CIS and DISA, but approaches and organization styles are different. Selection considerations: size of organization, IT infrastructure extent, nature of business, security program goals, and maturity of IT & security staff. Rule of thumb: Smaller organizations use CIS, larger organizations use DISA. CIS is part of Homeland Security, DISA is part of the US Military. DISA is more frequently updated and maintained with wider coverage.
Topic no 71: Security Hardening – Windows Server 2012R2
Example: Windows Server 2012 R2, DISA Release 8 (28 April 2017), Domain Controller. Rule Title: Autoplay must be disabled for all drives — STIG ID: WN12-CC-000074; Severity: CAT I. Discussion: Allowing Autoplay to execute may introduce malicious code; Autoplay begins reading from a drive as soon as media is inserted; by default, Autoplay is disabled on removable drives and network drives but not CD-ROM; enabling this policy disables Autoplay on all drives. Check Content: If registry value does not exist or is not configured as specified, this is a finding — Registry Hive: HKEY_LOCAL_MACHINE; Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer; Value Name: NoDriveTypeAutoRun; Type: REG_DWORD; Value: 0x000000ff (255). Fix Text: Configure policy for Computer Configuration → Administrative Templates → Windows Components → AutoPlay Policies → "Turn off AutoPlay" to "Enabled: All Drives". CCI: CCI-001764 — The information system prevents program execution in accordance with organization-defined policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage (NIST SP 800-53 Revision 4 :: CM-7 (2)).
⭐ Key Takeaways
The 8-step hardening methodology proceeds from identifying assets through production deployment with monitoring. CIS Benchmarks and DISA STIGs are the two primary security benchmark frameworks, with CIS being more accessible for smaller organizations and DISA being more comprehensive, frequently updated, and suited for larger organizations. Both frameworks provide detailed controls with descriptions, rationales, audit procedures, and remediation steps, but use different organization styles. Key STIG severity levels are CAT I (most critical) and CAT II. Understanding how to navigate CIS benchmark documents and DISA STIG viewer, including interpreting profile applicability (Level 1 vs. Level 2 for CIS; CAT I vs. CAT II for DISA), is essential for implementing security hardening in real-world environments.
🧠 Quick Revision Questions
- What are the four criteria used in Step 2 to research applicable security controls?
- What is the purpose of Step 6 (Validation of control implementation) and who performs it?
- In CIS benchmarks, what distinguishes Level 1 from Level 2 profile applicability?
- What is the CCI (Control Correlation Identifier) and which standard does it reference in DISA STIGs?
- According to the rule of thumb, which benchmark framework (CIS or DISA) is recommended for smaller organizations and why?