CISSP Domain 1 - Flashcards
CIA - Confidentiality
- High level of assurance that info is kept from unauthorized parties
- Attacks: Shoulder surfing, social engineering, decryption, brute-force
- Defense: Encryption, access controls
CIA - Confidentiality - Definition
High level of assurance that info is kept from unauthorized parties
CIA - Confidentiality - Attacks
- Shoulder surfing
- Social engineering
- Decryption
- Brute-force
CIA - Confidentiality - Defense
- Encryption
* Access Controls
CIA - Confidentiality - Related concepts
- Sensitivity: What could happen if this info was disclosed
- Discretion: When you choose to control the information disclosure to limit damage
- Concealment: Act of hiding or preventing disclosure
- Secrecy: Keeping something secret
- Privacy: Keeping sensible info confidential
- Seclusion: Storing something in an out-of-the-way manner
- Isolation: Keeping something separated from others
<p>Sensitivity</p>
<p>What could happen if this info was disclosed</p>
<p>Discretion</p>
<p>When you choose to control the information disclosure to limit damage</p>
<p>Concealment</p>
<p>Act of hiding or preventing disclosure</p>
<p>Secrecy</p>
<p>Keeping something secret</p>
<p>Privacy</p>
<p>Keeping sensible info confidential</p>
<p>Seclusion</p>
<p>Storing something in an out-of-the-way location. This<br></br>
location can also provide strict access controls. Seclusion can help enforcement of<br></br>
confidentiality protections</p>
<p>Isolation</p>
<p>Keeping something separated from others</p>
<p>CIA - Integrity</p>
<p>When info remains unaltered by unauthorized parties<br></br>
Approaches:<br></br>
Preventing intentional unauthorized modification<br></br>
Preventing accidental modifications<br></br>
Ensure internal and external consistency of the information</p>
<p>CIA - Availability</p>
<p>Usable access to a resource is always provided in a timely and uninterrupted manner<br> * Examples:<br> - Load Balancing<br> - Clustering<br> - Backups<br> - Redundancy</p>
<p>AAA (IAAAA)</p>
<p>- Identification: A subject claims a specific identity<br></br>
- Authentication: A subject proves he is who he claims to be<br></br>
- Authorization: Deciding what the subject can access and how can it be used<br></br>
- Auditing: Recording activities of the subject in a log<br></br>
- Accountability: Reviewing the log to check for compliance</p>
<p>From Vulnerability to Exposure - Vulnerability</p>
<p>A weakness in a system that allows a threat to compromise security<br></br>
Examples:<br></br>
* AP without security enabled<br></br>
* Too many ports allowed on a firewall<br></br>
* Unneeded service running on a server</p>
<p>From Vulnerability to Exposure - Exploit</p>
<p>Occurs when a vulnerability is taken advantage of by an attacker</p>
<p>From Vulnerability to Exposure - Threat</p>
<p>Danger that a vulnerability will be exploited</p>
<p>From Vulnerability to Exposure - Threat Agent</p>
<p>Entity that exploits a vulnerability</p>
<p>From Vulnerability to Exposure - Risk</p>
<p>The likelihood that a threat agent will exploit a vulnerability combined with the damage that could result</p>
<p>From Vulnerability to Exposure - Exposure</p>
<p>Single real-world instance of a vulnerability being exploited by a threat agent</p>
<p>From Vulnerability to Exposure - Control</p>
<p>Countermeasure put into place to mitigate the risk</p>
<p>Controls - Categories</p>
<p>* Administrative Controls: Controls put in place by management<br></br>
Examples<br></br>
Training<br></br>
Security Policy<br></br>
* Technical Controls: Software elements such as hashing, encryption or authentication enforcement<br></br>
* Physical Controls: Controls that are physical<br></br>
* Examples<br></br>
- Lighting<br></br>
- Fences<br></br>
- Keycards<br></br>
- Security Guards</p>
<p>Controls - Functions</p>
<p>* Preventative: Avoid an incident<br></br>
* Corrective: Fix a component or system<br></br>
* Deterrent: Discourage an attacker<br></br>
* Detective: Identify an intruder<br></br>
* Recovery: Bring environment back to normal operation<br></br>
* Compensating: Alternative control if the first choice is unavailable</p>
<p>Security Frameworks - ISO 27000 Series - BS7799</p>
<p>* Created in 1995<br></br>
* Published by British Standards Institute<br></br>
* Outlines how an ISMS should be created and maintained<br></br>
* Part 1<br></br>
Describes controls<br></br>
* Part 2<br></br>
Shows how an ISMS can be setup</p>
<p>Security Frameworks - ISO 27000 Series (1-8,11, 14-15,31-35,37,799)</p>
<p>ISO 27000<br> Overview and vocabulary for the rest of the 27000 series<br> ISO 27001<br> Standard for creation, implementation, control and improvement of ISMS<br> ISO 27002<br> General guidelines for implementing an ISMS<br> ISO 27003<br> ISMS implementation<br> ISO 27004<br> ISMS measurement<br> ISO 27005<br> Risk management<br> ISO 27006<br> Certification body requirements<br> ISO 27007<br> ISMS auditing<br> ISO 27008<br> Guidance for auditors<br> ISO 27011<br> Telecommunications organizations<br> ISO 27014<br> Information security governance<br> ISO 27015<br> Financial sector<br> ISO 27031<br> Business continuity<br> ISO 27032<br> Cybersecurity<br> ISO 27033<br> Network security<br> ISO 27034<br> Application security<br> ISO 27035<br> Incident management<br> ISO 27037<br> Digital evidence collection and preservation<br> ISO 27799<br> Health organizations</p>
<p>ISO 27000</p>
<p>Overview and vocabulary for the rest of the 27000 series</p>
<p>ISO 27001</p>
<p>Standard for creation, implementation, control and improvement of ISMS</p>
<p>ISO 27002</p>
<p>General guidelines for implementing an ISMS</p>
<p>ISO 27003</p>
<p>ISMS implementation</p>
<p>ISO 27004</p>
<p>ISMS measurement</p>
<p>ISO 27005</p>
<p>Risk management</p>
<p>ISO 27006</p>
<p>Certification body requirements</p>
<p>ISO 27007</p>
<p>ISMS auditing</p>
<p>ISO 27008</p>
<p>Guidance for auditors</p>
<p>ISO 27011</p>
<p>Telecommunications organizations</p>
<p>ISO 27014</p>
<p>Information security governance</p>
<p>ISO 27015</p>
<p>Financial sector</p>
<p>ISO 27031</p>
<p>Business continuity</p>
<p>ISO 27032</p>
<p>Cybersecurity</p>
<p>ISO 27033</p>
<p>Network security</p>
<p>ISO 27034</p>
<p>Application security</p>
<p>ISO 27035</p>
<p>Incident management</p>
<p>ISO 27037</p>
<p>Digital evidence collection and preservation</p>
<p>ISO 27799</p>
<p>Health organizations</p>
<p>Security Frameworks - Enterprise Architecture Development - Introduction</p>
<p>* Addresses the structure and behavior of an organization<br></br>
* It's a guidance on how to build an architecture<br></br>
* Allows each group of people within an organization to view the business in terms they can understand</p>
<p>Security Frameworks - Enterprise Architecture Development - Zachman</p>
<p>* Created by John Zachman in the 80s<br></br>
* This framework is not security oriented, but it is a good template to work with because it offers direction on how to understand an actual enterprise in a modular fashion<br></br>
* 2-dimensional matrix<br></br>
X-axis<br></br>
5 different audiences<br></br>
Y-axis<br></br>
6 different views</p>
<p>Security Frameworks - Enterprise Architecture Development - Zachman (audiencies - views)</p>
<p>Audiences:<br></br>
* Executives<br></br>
* Business Managers<br></br>
* System Architects<br></br>
* Engineers<br></br>
* Technicians<br></br>
* Entire enterprise</p>
<p>Views<br></br>
* What<br></br>
* How<br></br>
* Where<br></br>
* Who<br></br>
* When<br></br>
* Why</p>
<p>Security Frameworks - Enterprise Architecture Development - TOGAF</p>
<p>* Created by US DoD<br></br>
* Architecture types<br></br>
Business<br></br>
Data<br></br>
Application<br></br>
Technology<br></br>
* Architecture Development Method (ADM)<br></br>
Used to create each type<br></br>
The last step feeds back into the first step<br></br>
After each iteration, the process has been improved to reflect changing requirements<br></br>
Each iteration addresses each of the four views</p>
<p>Security Frameworks - Enterprise Architecture Development - Military Oriented</p>
<p>* Department of Defense Architecture Framework:<br></br>
- Involves things as command, control, surveillance and reconnaissance<br></br>
- One of its primary objectives is to ensure a common communication protocol and standard payloads<br></br>
* Ministry of Defence Architecture Framework<br></br>
- British version of DoDAF</p>
<p>Security Frameworks - Enterprise Architecture Development - Sherwood Applied Business Security Architecture (SABSA)</p>
<p>* It's an Enterprise Security Architecture: Ensures an organization has an effective ISMS in place<br> * Similar to Zachman<br> * Views:<br> - Assets (What)<br> - Motivation (Why)<br> - Process (How)<br> - People (Who)<br> - Location (Where)<br> Time (When)<br> * Y-Axis from wide to narrow<br> - Contextual<br> - Conceptual<br> - Logical<br> - Physical<br> - Component<br> - Operational<br> * Difference between SABSA and the others<br> - It is also a methodology<br> - Provides an actual process to follow<br> - It is geared toward security</p>
<p>Security Frameworks - Architecture Framework Terms</p>
<p>* Strategic Alignment: An architecture is strategically aligned when it meets the needs of the business and all legal or regulatory requirements<br></br>
* Business Enablement: A good security architecture must enable the business to thrive by not getting in the way, but still providing proper security<br></br>
* Process Enhancement: Security forces us to take a closer look at existing processes. This could lead us to improve them<br></br>
* Security Effectiveness: Most quantifiable of the attributes. Examples: ROI, SLA achievements</p>
<p>Security Frameworks - Frameworks for Implementation</p>
<p>* COSO Internal Control<br></br>
* COBIT<br></br>
* NIST SP 800-53</p>
<p>Security Frameworks - Frameworks for Implementation - COSO IC</p>
<p>* Identifies 17 control principles grouped into 5 categories<br> * Created in the 80s as a result of financial fraud<br> * Provides Corporate Governance<br> * Categories<br> - Control Environments<br> - Risk Assessments<br> - Control Activities<br> - Information and Communication<br> - Monitoring Activities</p>
<p>Security Frameworks - Frameworks for Implementation - COBIT</p>
<p>* Created by ISACA and ITGI<br></br>
* Defines 17 enterprise and 17 IT goals<br></br>
* It's not strictly security related<br></br>
* It is an IT related subset of COSO IC<br></br>
* Principles<br></br>
Meeting stakeholder needs<br></br>
Covering the enterprise end-to-end<br></br>
Applying a single integrated framework<br></br>
Enabling a holistic approach<br></br>
Separating governance from management</p>
<p>Security Frameworks - Frameworks for Implementation - NIST SP 800-53</p>
<p>* Created by the US government<br></br>
* Specifies the control that federal agencies must implement<br></br>
* If an agency doesn't comply, they are violating the FISMA (Federal Information Security Management Act of 2002)<br></br>
* Contains a list of 18 control categories</p>
<p>Security Frameworks - Frameworks for Implementation - Private vs Federal controls</p>
<p>Administrative = Management<br> Technical = Technical<br> Physical = Operational</p>
<p>Security Frameworks - Process Development</p>
<p>* ITIL<br></br>
* Six Sigma<br></br>
* Capability Maturity Model Integration (CMMI)</p>
<p>Security Frameworks - Process Development - ITIL</p>
<p>* Developed in the UK in the 80s<br></br>
* De facto standard for IT management best practices<br></br>
* Focuses on achieving SLAs between the IT department and its customer<br></br>
* Stages<br></br>
- Design<br></br>
- Transition<br></br>
- Operation<br></br>
* Each stage has between 3 and 5 steps</p>
<p>Security Frameworks - Process Development - Six Sigma</p>
<p>* Measures process quality by using statistical calculations<br></br>
* A sigma rating is applied to a process to indicate the percentage of defects it contains</p>
<p>Security Frameworks - Process Development - Capability Maturity Model Integration (CMMI)</p>
<p>* Created by Carnegie Mellon for US DoD<br></br>
* Determines the maturity of an organization's processes<br></br>
* Designed to make improvements in an incremental and standard manner<br></br>
* Levels:<br></br>
- Level 0: Nonexistent Management<br></br>
- Level 1: Unpredictable Processes<br></br>
- Level 2: Repeatable Processes<br></br>
- Level 3: Defined Processes<br></br>
- Level 4: Managed Processes<br></br>
- Level 5: Optimized Processes</p>
<p>Security Frameworks - The Process Life Cycle</p>
<p>* Focuses on how to keep processes up-to-date and healthy<br></br>
* Four steps, and the last one feeds right back into the first one to start a new iteration<br></br>
* Steps: Plan, Implement, Operate, Evaluate</p>
<p>Security Frameworks - The Process Life Cycle - Steps - 1: Plan (6)</p>
<p>- Establish MGMT and oversight committees<br></br>
- Identify business drivers and threats<br></br>
- Perform a risk assessment<br></br>
- Create security architectures for the business, data, application and infrastructure<br></br>
- Select possible solutions for the problems identified<br></br>
- Get mgmt approval to move to the next steps</p>
<p>Security Frameworks - The Process Life Cycle - Steps - 2: Implement (8)</p>
<p>- Assign duties<br></br>
- Establish baselines<br></br>
- Put security policies into operation<br></br>
- Identify data that needs to be secured<br></br>
- Create blueprints<br></br>
- Implement controls based on the blueprints<br></br>
- Implement solutions to monitor the controls based on the blueprints<br></br>
- Establish goals, SLAs and metrics based on the blueprints</p>
<p>Security Frameworks - The Process Life Cycle - Steps - 3: Operate (4)</p>
<p>- Follow established procedures to ensure baselines met the blueprints<br></br>
- Execute audits<br></br>
- Execute tasks defined by the blueprints<br></br>
- Ensure SLAs are met</p>
<p>Security Frameworks - The Process Life Cycle - Steps - 4: Evaluate (4)</p>
<p>- Review logs, audit results, metrics and SLAs<br></br>
- Determine if the blueprint goals have been met<br></br>
- Hold quarterly meetings with the steering committee<br></br>
- Identify actions to improve as an input into the first step</p>
<p>Computer Crime Law - Cyberlaw</p>
<p>Any law that deals with computer-based crime</p>
<p>Computer Crime Law - Computer Crime Categories</p>
<p>* Computer-assisted: Computer is a tool<br></br>
- Example: Stealing money from a bank across the Internet<br></br>
* Computer-targeted: Computer is the victim<br></br>
- Example: DoS attack<br></br>
* Computer is incidental: Computer is involved but didn't play a significant role in the crime<br></br>
- Example: If a computer is used to temporarily store stolen or illegal goods</p>
<p>Computer Crime Law - Computer Crime</p>
<p>* Script Kiddies: Unsophisticated individuals who know just enough about pre-built hacking tools<br></br>
*Types of serious hackers<br></br>
1- The ones who randomly sniff around<br></br>
2- APT (Advanced Persistent Threats)<br></br>
- Most dangerous<br></br>
- They target specific persons or organizations</p>
<p>Computer Crime Law - Computer Crime - OECD</p>
<p>* OECD has issued guidelines on how to deal with data that is transfered between countries<br> * Core principles:<br> Collection Limitation<br> Data Quality<br> Purpose Specification<br> Use Limitation<br> Security Safeguards<br> Openness<br> Individual Participation<br> Accountability</p>