Notes / Module 11
Understanding Defense
Module 11 is about defending an organisation on purpose: know what you own, know what can hurt it, then stack layers so one failure does not expose everything. The exam weights defense-in-depth (onion versus artichoke, the five strategies), asset management and the policy types.
11.1.1Assets, vulnerabilities, threats
Before defending a network an analyst must identify three things: the assets, the vulnerabilities in the system and the threats to the assets.
- Asset
- Anything of value to the organisation that must be protected: servers, infrastructure devices, end devices and, the greatest asset, data.
- Vulnerability
- A weakness in a system or its design that a threat actor could exploit.
- Threat
- Any potential danger to an asset.
- Attack surface
- All the devices and information the organisation owns or manages, which threat actors could target.
11.1.2Identifying and classifying assets
Asset management is inventorying every asset, then building and applying policies and procedures to protect them. The organisation also has to locate its critical information assets and know how access to them is gained. Different assets attract different threat actors: a retail business stores card data, an engineering firm stores competition-sensitive designs, a bank stores customer and account data.
Asset classification groups resources by common characteristics so the most critical receive the highest protection and, if needed, special handling. A labelling system shows how valuable, sensitive and critical information is. It takes four steps.
| Step | Action | Detail |
|---|---|---|
| 1. Category | Pick the identification category | Information assets, software assets, physical assets, services |
| 2. Accountability | Assign an owner | An owner for every information asset and every piece of application software |
| 3. Criteria | Decide what the classification is based on | Confidentiality, value, time, access rights, destruction |
| 4. Schema | Implement a classification schema | A consistent way of identifying information so protection is uniform and monitoring is easier |
Asset standards name the specific hardware and software products an organisation uses. After a failure, staff do not scramble for a replacement part. Non-standard environments need more expertise and raise the cost of maintenance contracts and inventory.
11.1.6Asset lifecycle
Cybersecurity specialists manage an information asset and its systems through five stages.
| Stage | What happens |
|---|---|
| 1. Procurement | Bought on needs identified from gathered data, then added to inventory. |
| 2. Deployment | Assembled, inspected for defects, tested, tagged or barcoded for tracking. Moves from inventory to in-use. |
| 3. Utilization | The longest stage. Performance is checked continuously; upgrades, patches, new licences and compliance audits. |
| 4. Maintenance | Extends the productive life; the asset may be modified or upgraded. |
| 5. Disposal | End of life. All data is wiped. May include dismantling for parts; parts that are an environmental hazard follow local guidelines. |
Worked example
Which stage? Adding barcodes to new equipment
- 1Barcodes and tags are installed so the asset can be tracked.
- 2The asset is moving from inventory to in-use.
- 3That is deployment, not procurement (the purchase) or utilization (patching and audits).
11.1.8Identifying vulnerabilities and threats
Threat identification gives the organisation a list of likely threats for its environment. It asks three questions.
- What are the possible vulnerabilities of the system?
- Who may want to exploit them to reach specific information assets?
- What are the consequences if they are exploited and assets are lost?
Finding vulnerabilities means understanding the important applications in use and the weaknesses of each application and its hardware. The module's example is an e-banking system with seven threats.
| Threat | What the attacker does |
|---|---|
| Internal system compromise | Uses the exposed e-banking servers to break into the bank's internal system. |
| Stolen customer data | Takes personal and financial data from the customer database. |
| Phony transactions (external server) | Alters the application code and impersonates a legitimate user. |
| Phony transactions (stolen PIN or smart card) | Steals a customer's identity and transacts from the compromised account. |
| Insider attack | A bank employee finds a flaw in the system to attack from. |
| Data input errors | A user enters incorrect data or makes incorrect transaction requests. |
| Data centre destruction | A cataclysmic event damages or destroys the data centre. |
11.1.9Defense-in-depth: layers and the onion
Defense-in-depth uses multiple layers of security at the network edge, inside the network and on endpoints. The layers work together so that the failure of one safeguard does not affect the effectiveness of the others. It does not remove the need for firewalls or mitigate every vulnerability.
| Layer | Role |
|---|---|
| Edge router | First line of defence. A rule set of allowed and denied traffic; passes connections meant for the internal LAN to the firewall. |
| Firewall | Second line. A checkpoint that filters further and tracks connection state. Denies connections started from the outside (untrusted) network, lets inside users open two-way connections out. Can do an authentication proxy so external remote users reach internal resources. |
| Internal router | Another line. Applies final filtering rules before traffic reaches its destination. |
Other devices in the design: IPS (intrusion prevention systems), AMP (advanced malware protection), web and email content security, identity services and network access controls.
Security onion — peel every layer
Security artichoke — remove only some leaves
| Security onion | Security artichoke | |
|---|---|---|
| Attacker's path | Must peel and penetrate each layer, one after another, before reaching the target | Only needs to remove certain leaves; not every leaf has to go |
| Fits | A network with a clear perimeter | Borderless networks |
| Key idea | Layers stand between the attacker and the data | Each leaf protects and also gives a path to attack; the heart holds the most confidential data |
| Example | A layered server | A mobile device is easier to compromise than a layered internal server, and leaf after leaf leads to more data |
11.1.11The five defense strategies
With only one measure in place, a criminal needs to beat only that one. The five strategies build in more.
| Strategy | Idea | Example |
|---|---|---|
| Layering | A barrier of multiple defences that work together. Ideally each layer is harder to beat than the last. Not impenetrable, but it minimises risk. | Top-secret documents on a password-protected server in a locked building behind an electric fence |
| Limiting | Each user gets only the access their job needs, using tools, settings and procedures. | File permissions; sensitive documents may only be consulted in a room with CCTV |
| Diversity | The layers must differ so one technique cannot beat them all. | A swipe card from one vendor and a fingerprint reader from another; time-delay locks plus supervision by security staff |
| Obscurity | Hide details that reveal the OS, equipment make, software or vulnerabilities, including in error messages. | An error message that does not name the server's OS |
| Simplicity | Complexity does not guarantee security. Hard-to-understand systems get misconfigured and backfire. | Simple on the inside, complex on the outside |
11.2Configuration, logs and protocol analysers
Configuration management is identifying, controlling and auditing the implementation of, and any changes to, a system's established baseline. The baseline configuration is the settings configured for a system that form the template for all similar systems. For example, the required applications and system settings for every Windows workstation the organisation deploys.
A log records all events as they occur, and each log entry holds the details of one event. Logs show how an attack occurred and which defences worked.
| Log | Records |
|---|---|
| Audit log | User authentication attempts |
| Access log | Requests for specific files on a system |
| Operating system log | Events tied to OS actions: client requests and server responses such as successful authentications, and usage such as the number and size of transactions in a period. A log of failed logins is an example. |
| Application security log | Output of network-based or system-based security software that detects malicious activity. Supports audits, trend analysis, and documents compliance with laws and regulations. |
Log management sets the procedures for generating, transmitting, storing, analysing and disposing of log data.
A protocol analyser (packet analyser, packet sniffer) intercepts and logs network traffic on wired and wireless networks. It captures each packet, reads its fields and analyses its content. Its functions are traffic logging, network problem analysis, detection of network misuse, detection of intrusion attempts and isolation of exploited systems.
11.3.1Business and security policies
Business policies govern an organisation's actions and define correct behaviour. On a network they define the allowed activities and so set a baseline of acceptable use. Behaviour that breaks policy may mean a security breach.
| Policy | What it is |
|---|---|
| Company | Rules of conduct and responsibilities of employees and employers. Protects workers' rights and business interests. |
| Employee | Written and maintained by HR: salary, pay schedule, benefits, work schedule, vacations. New hires review and sign it. |
| Security | Security objectives, rules of behaviour for users and administrators, and system requirements. Evolves with threats, vulnerabilities and business needs. |
A comprehensive security policy demonstrates commitment to security, sets expected behaviour, ensures consistency in operations, acquisition and maintenance, defines the legal consequences of violations and gives security staff the backing of management.
| Policy within a security policy | Covers |
|---|---|
| Identification and authentication | Authorised persons who may access network resources, and how identity is verified. |
| Password | Minimum requirements and regular changes. |
| Acceptable use (AUP) | Acceptable network applications and uses, and the ramifications of violation. |
| Remote access | How remote users connect and what they can reach. |
| Network maintenance | Network device OS and end-user application update procedures. |
| Incident handling | How security incidents are handled. |
The AUP (also called an appropriate use policy) is one of the most common components. It defines what users may and may not do, including the type of traffic allowed. Make it as explicit as possible, for example by listing prohibited websites, newsgroups or bandwidth-heavy applications. Every employee signs it and signed copies are kept for the length of employment.
11.3.3BYOD and compliance
BYOD (bring your own device) lets employees use personal mobile devices to reach company systems, software, networks or information. Benefits: higher productivity, lower IT and operating costs, better mobility, greater appeal for hiring and retention. Risk: data breaches and greater liability for the organisation.
A BYOD security policy states the goals of the program, which employees may bring devices, which devices are supported, the access level granted, the rights and permitted activities of security staff on the device, which regulations apply and the safeguards if a device is compromised.
| BYOD best practice | What to do |
|---|---|
| Password protected access | Unique passwords for each device and account. |
| Manual wireless control | Turn off Wi-Fi and Bluetooth when not in use. Connect only to trusted networks. |
| Keep updated | Update the OS and software; updates carry security patches. |
| Back up data | Enable backup in case the device is lost or stolen. |
| Find my Device | A locator service with remote wipe. |
| Antivirus | Provide antivirus software for approved BYOD devices. |
| MDM | Mobile Device Management software applies security settings and software configurations to all devices on company networks. |
Compliance regulations are external rules that define what an organisation must provide and its liability if it fails to comply. Which ones apply depends on the type of organisation and the data it handles. INFOSEC (Information Systems Security) professionals must know the laws and codes of ethics that bind them.
Check yourself
Answer these out loud, without scrolling up. Any you can't, reread that section — then let the deck mark you.
- 1.What three things must be identified before a network can be defended, and how do an asset, a vulnerability and a threat differ?
- 2.Give the four steps of asset classification and the five lifecycle stages. Which lifecycle stage is the longest?
- 3.Explain the security onion and the security artichoke. Why does the artichoke fit borderless networks better?
- 4.Name the five defense-in-depth strategies and give one example of each.
- 5.What is the difference between an audit log and an access log, and what does log management cover?
- 6.List the six policies within a security policy and the seven BYOD best practices.