CISSP (Domain 3 - Information Security Governance and Risk Management) Flashcards
4 Item for a Business Model for Information Security
OPPT
- Organization Design/Strategy
- People
- Process
- Technology
6 Interconnections for a Business Model in Information Security
(GCEEHA)
- Governance
- Culture
- Enablement & Support
- Emergence
- Human Factors
- Architecture
Corporate Governance
Set of responsibilities and practices exercised by the board and executive management with the goal of providing strategic direction, objectives achieved.
Plan Do Check Act (PDCA)
E/IO/MR/MI
Approach to continuous process improvement
- Establish ISMS
- Implement/Operate ISMS
- Monitor/Review ISMS
- Maintain/Improve ISMS
ISO 27001 (Governance)
PDCA model to structure the processes, and reflects the principals set out in the OECD guidelines
- How to implement
ISO 27002 (Governance)
AKA ISO 17799, basic outline of hundreds of potential controls and control mechanisms
- What should be secured
3 Goals of a Security Model
(long/mid/short)
(STO)
- Long Term: Strategic Goals (supported by med/short term, all PCs on VPN)
- Mid Term: Tactical Goals (Put in domains, add Firewalls)
- Short Term: Operational Goals (Patches)
Due Care
- *Do Connect
- Do the right thing and protect assets
- Functional Requirements
Due Diligence
- *Do Detect
- Senior Management
- Investigate actual threats and risks (Determine Risk Exposure)
- Assurance Requirements
CIA Triad
- Confidentiality: Prevent unauthorized disclosure of sensitive information
- Integrity: Prevent unauthorized modification of systems and information
- Availability: Prevent disruption of service and productivity
Confidentiality (CIA Triad) - Threats and Solutions
Threats:
- Hackers
- Malicious Software
- Social Engineering
- System Failure/Employee Error
Solutions:
- Identification
- AuthN
- AuthZ
Integrity (CIA Triad) - Threats and Solutions
Threats:
- Hackers
- Malicious Software
- Social Engineering
- System Failure/Employee Error
Solutions:
- Least Privilege
- Separation of Duties (SoD), prevents collusion
- Rotation of Duties (Mandatory Vacation)
Availability (CIA Triad) - Threats and Solutions
Threats:
- Deliberate Attacks
- System Failure/User Error
- Natural Disasters
Solutions:
- Redundancy
3 Reasons Why We Have Security Policies
OSR
- Objective/Goal or Purpose
- Scope
- Responsibility
What is a Security Policy
General statement products by senior management/board/committee to dictate what type of role security plays within the organization.
Security Policy Document Relationship
Drivers/MgmtSS/MgmtSD
- Drivers: Laws, Regulations, Best Practices
Program or Organizational Policy - Managements Security Statement: Program/Organizational Policy
- Managements Security Directive: Functional Policies (issue and system specific)
+ standards/procedures/baselines/guidelines
NIST SP 800-12: Program Policy
Programs security policy driving by Laws/Regulations/Best Practices. Large scope
NIST SP 800-12: Issue-Specific Policies
Addresses specific security threats management feels need more detailed explanation and attention.
Ex: Acceptable use of resources agreement, e-mail policy where management can read your email
NIST SP 800-12: System-Specific Policies
Includes two components: Security Objectives and Operational Security Rules.
Usually only on one system
Ex. Payroll and HR can only modify Payroll system
Regulatory Policy
Government ordinance, all who fall under must comply
Advisory Policy
NOT mandated by law. Company puts in place on self.
Informative Policy
Educate who reads the policy.
Ex: No smoking in the aircraft
4 Functions for Support Policies
SBPG
- Standards
- Baselines
- Procedures
- Guidelines
Standards - Supporting Policies
- Binding
- Common practice all adhere to (RHEL only)
Baselines - Supporting Policies
- Binding
- Min level of protection and security
- Password length 8 characters