Domain 1: Security and Risk Management Flashcards
1
Q
What is the CIA Triad?
A
Confidentiality, Integrity and Availability
2
Q
What is the principle of ‘confidentiality’?
A
It is about protecting secrecy of data, objects, or resources by preventing unauthorised access to data. Prevent unauthorised disclosure, need to know, and least privilege, assurance that information is not disclosed to unauthorised programs, users, processes, encryption, logical and physical access control.
3
Q
What is the principle of ‘integrity’?
A
Protecting the reliability and correctness of data. Examples include access controls, IDS/IPS, and hashing.
4
Q
What is the principle of ‘availability’?
A
Providing authorised subjects timely and uninterrupted access to objects. This means access to data is reliable, timely, accessible, fault tolerant, and has recovery procedures in place. Examples include, monitoring network traffic.
5
Q
What is an ‘object’?
A
Passive element, such as files, computers, network connections, and applications
6
Q
What is a ‘subject’?
A
Active element in a security relationship, such as users, programs and computers.
7
Q
What is defense in depth?
A
Use of multiple controls in a series to protect an asset
8
Q
What is abstraction?
A
Where details of something is hidden. Security controls can be applied to the entire group (thus hiding the details)
9
Q
What is ‘IAAA’?
A
Identification, Authentication, Authorisation, and Auditing
10
Q
What is ‘Authentication’?
A
Proving one’s identity. Process of verifying or testing that the claimed identity is valid. Examples include providing a correct password, or other correct information.
11
Q
What is ‘Authorisation’?
A
About defining the permissions (e.g. grant or deny) of a resource and object access for a specific identity. It involves evaluating an access control matrix that compares the subject, the object, and the intended activity.
12
Q
What is ‘Auditing’?
A
Process of recording log files to check for compliance and violations in order to hold subjects accountable for their actions. Ensures that a subject’s actions are non-repudiation.
13
Q
What is ‘layering’?
A
Use of multiple controls in a series. Also known as Defense in Depth. Serial configurations (controls in a row) are very narrow but very deep, alternatively parallel configurations are very broad, but lack depth.
14
Q
What is ‘data hiding’?
A
Preventing data from being discovered or accessed by a subject positioning the data in a logical storage compartment that is not accessible or seen by the subject. Such as polyinstantiaton.
15
Q
What is the weakest element in any security solution?
A
Humans
16
Q
What role does job descriptions play when hiring new staff?
A
Ensure job descriptions consider separation of duties to separate key functions to limit ability for one employee to circumvent key security controls. Further, ensure a classification for the job.
17
Q
What is ‘job rotation’?
A
Rotating employees among multiple job positions. This is the best way to investigate an employee’s daily business activity to uncover any potential fraud that may be taking place.
18
Q
Strategic Plan
A
Long term plan defining organisation’s security purpose. Aligns the plan with the organisations goals, mission, objectives. This is a 5 year plan with annual reviews
19
Q
Tactical Plan
A
Mid term plan developed to provide more details on accomplishing the goals set forth in the strategic plan or can be crafted ad hoc based upon unpredictable events. This lasts a year
20
Q
Operational Plan
A
Short term (for a month or quarter) highly detailed plan. Purpose to retain compliance with tactical plans. The plans may include: resource allotments, budgetary requirements.
21
Q
Data Classification Process
A
Identify the custodian, specify evaluation criteria, document any exceptions, select security controls for each level, specify the procedures for declassifying, and create enterprise wide awareness program
22
Q
Levels of Government/military classification
A
Top Secret, Secret, Confidential, Sensitive but Unclassified, Unclassified
23
Q
Levels of Corporate classifications
A
Confidential, Private, Sensitive, Public
24
Q
Due care
A
Using responsible care to protect the interests of an organisation. Company must do all that it could have reasonably done to try and prevent a security breach /compromise/disaster, and take the necessary steps required as countermeasures/controls (safeguards).
25
Due diligence
Practicing activities that maintain due care effort. Company properly investigated all of its possible weaknesses and vulnerabilities AKA understanding the threats.
26
Information security program
Designing and implementing security practices to protect critical business process and assets.
27
Types of policies
Corporate policy, security policy, system specific policy and issue specific policy
28
Dual control
Where two people must simultaneously authorise an action, such as use of two keys. This is similar to M of N control
29
What is the order of security documents in an organisation?
Policies --> Standards/Baseline --> Guidelines --> Procedures
30
What is a security policy?
Document that defines the scope of security needed by the organisation at a high level. Discusses the assets that require protection, and assigns roles and responsibilities.
31
What is a 'standard document'?
Mandatory document that provides compulsory requirements for systems to enable consistent use
32
Guidelines
Not mandatory, suggestive in nature actions to guide users
33
Procedure documents
For example, these are Standard Operating Procedures that provide step by step instructions on a given topic
34
Baselines
Mandatory minimum acceptable security configuration for a system or process, e.g. performing hardening, has a standard image
35
Risk
Possibility or likelihood of a threat exploiting a vulnerability to cause harm. Calculated as Risk = Threat x Vulnerability
36
Threat
Potential cause of an unwanted incident, which may result in harm to a system or organisation. Threats exploit vulnerabilities.
37
Vulnerability
Weakness in a system that allows a threat source to compromise its security
38
Exposure
Being susceptible to asset loss because of a threat
39
Safeguards
Security control to reduce/remove a vulnerability. Can be a technical, physical or administrative control
40
Attack
Exploitation of a vulnerability by a threat agent
41
Breach
Intentional or unintentional release of private data to an untrusted environment.
42
Threat agent
Entity that takes advantage of a vulnerability
43
What is 'DAD'?
Negative to CIA, this is the
1. Disclosure
2. Alteration
3. Destruction
44
Privacy
Maintaining the confidentiality of data
45
ISO 27005
Risk management framework
46
Risk management approach
It is not possible to get rid of all risk, therefore, aim is to bring risk to an acceptable/tolerable level
47
Responsibilities of the Information Security Officer
- Written products - ensure they are done
- Cyber Incident Response Team - implement and operate
- Security awareness - provide leadership
- Communicate - risk to higher management
- Report to as high a level as possible
- Security is everyone's responsibility
48
Control Frameworks
Ensure control frameworks are:
1. Consistent - approach and application
2. Measurable - way to determine progress
3. Standardised - all the same
4. Comprehension - examine everything
5. Modular - to help in review and adaptive. Layered, abstraction.
49
Patent
Grants ownership of an invention and provides enforcement for owner to exclude others from practicing the invention. After 20 years the idea is open source of application.
50
Copyright
Protects the expression of ideas but not necessarily the idea itself. For example, poem or song. Expires 70 years after author dies.
51
Trade secret
Something that is proprietary to a company and important for its survival and profitability (like formula of Coke or Pepsi). This is NOT registered
52
Trademarks
Words, name, product shape, symbol, color or a combination used to identify products and distinguish them from competitor products. For example, McDonald's 'M'. Expires in 10 years
53
Wassenaar Agreement (WA) AKA International Traffic in Arms Regulations
Agreement which implemented controls on the export of cryptographic systems.
54
SOX
Sarbanes Oxley. Protects shareholders and the general public from accounting errors and fraudulent practices in enterprises, and to improve the accuracy of corporate disclosures.
55
Section 302 SOX
CEO's and CFO's can be sent to jail when the information they sign is incorrect. CEO must sign
56
Section 404 SOX
This is about internal controls assessment: describing logical controls over accounting files, good auditing and information security.
57
Legal Liability for Executives
Executives are now held liable if the organisation they represent is not compliant with the law
58
Negligence
It is a breach of duty of care. This occurs if there is a failure to implement recommended precautions, if there is no contingency/disaster recovery plan, failure to conduct appropriate background checks, failure to institute appropriate information security measures, failure to follow policy or local laws and regulations.
59
COSO
Internal control system/framework to work with Sarbanes Oxley 404 compliance. Developed a model for evaluating internal controls. This model has been adopted as the generally accepted framework for internal control and is widely recognised as the definitive standard against which organisations measure the effectiveness of their systems of internal control.
60
COBIT
IT governance and management framework created by ISACA.
61
Incident
An event that has the potential to do harm
62
Data disclosure
Unauthorised acquisition of personal information
63
Event
Threat events are accidental and intentional exploitations of vulnerabilities
64
Fourth Amendment
Basis for privacy rights in fourth amendment to the constitution
65
1974 US Privacy Act
Protection of PII on federal databases
66
1980 OECD Privacy Guidelines
Established the first internationally agreed upon privacy principles.
67
1986 US Computer Fraud and Abuses Act
Protects computers used by the Government or in interstate commerce from a variety of abuses.
68
1986 Electronic Communications Privacy Act
Makes it a crime to invade the privacy of an individual
69
Health Information Technology for Economic and Clinical Health Act of 2009 (HITECH)
Amended version of HIPAA. The HITECH Act encouraged healthcare providers to adopt electronic health records and improved privacy and security protections for healthcare data. Federal law requires notification of individuals when a HIPAA-covered entity breaches their protected health information.
70
Digital Millennium Copyright Act
Prohibits the circumvention of copy protection mechanisms placed in digital media and limits the liability of ISP's for the activities of their users. ISP's are no longer liable for the transitory activities of the user.
71
Economic Espionage Act 1996
Provides penalties for individuals found guilty of the theft of trade secrets. Harsher penalties apply when the individual knows that the information will benefit a foreign government.
72
GDPR
General Data Protection Regulation governs the use and exchange of personal information.
73
ISC2 Code of Ethics Cannons
ISC has established four key cannon/principles
74
ISC Cannon 1
Protect society, the commonwealth, and the infrastructure
75
ISC Cannon 2
Act honorably, honestly, justly, responsibly, and legally
76
ISC Cannon 3
Provide diligent and competent service to principals
77
ISC Cannon 4
Advance and protect the profession
78
Ethics and Internet RFC 1087
Don't compromise the privacy of users. Access to and use of Internet is a privilege and should be treated as such. It is defined as unacceptable and unethical if you, for example, gain unauthorised access to resources on the internet, destroy integrity, waste resources or compromise privacy
79
BC Plan Development Process
Based on the ISC2 BCP Process:
1. Project scope and planning
2. BIA
3. Continuity Planning
4. Approval and Implementation
80
Business Impact Assessment
Goal is to create a document to be used to help understand what impact a disruptive event would have on the business.
81
BIA: 1. Project Scope and Planning
1. Business organisation analysis: analyse organisation, including teams
2. BCP Team Selection: make sure to include senior executives
3. Resource Requirements: who do you need?
4. Legal and Regulatory Requirements
82
BIA: 2. Business Impact Assessment
1. Identify priorities: valuation of assets, including MTD and RTO for each business function
2. Identify risks for those assets, such as natural, man made and perform a likelihood assessment
83
BIA: 3. Continuity Planning
Determine appropriate responses: such as risk reduction/mitigation, assign/transfer, risk acceptance, and risk rejection
84
BIA: 4. Approval and Implementation
1. Get approval from CEO
3. Plan Training
3. Plan implementation
85
Seperation of Duties
Assigns parts of tasks to different individuals thus no single person has total control of the system's security mechanisms; forces collision.
86
M of N Control
Requires that a minimum number of agents (M) out of the total number of agents (N) work together to perform high-security tasks. So, implementing three of eight controls would require three people out of the eight with the assigned work task of key escrow recovery agent to work together to pull a single key out of the key escrow database.
87
Least privilege
A system's user should have the lowest level of rights and privileges necessary to perform their work and should only have them for the shortest time. Three types exist: Read only, read/write, and access/change.
88
Two man control
Two persons review and approve the work of each other, for very sensitive operations
89
Dual control
Two persons are needed to complete a task
90
Rotation of duties
Limiting the amount of time a person is assigned to perform a security related task before being moved to different task to prevent fraud; forces collusion
91
Mandatory vacations
Prevent fraud and allowing investigations, one week minimum; kill processes
92
Need to know
The subject is given only the amount of information required to perform an assigned task, business justification
93
Agreement Examples
NDA, non compete, and acceptable use
94
Explain risk of employees in managing security
Staff members pose more threat than external actors. Loss of money, stolen equipment, loss of time work hours, loss of reputation, declining trusts and loss of resources, bandwidth theft, due diligence.
95
Controls during Voluntary and Involuntary Leave
Ensure you perform exit interview
96
Third Party Controls
Vendors, consultants, and contractors. Make sure they are properly supervised, with their rights based on policy.
97
Likelihood
Chance it will happen
98
Residual Risk
Amount of risk left over. Organisations own the risk, and risk is determined as a byproduct of likelihood and impact. Further, the cost of applying extra countermeasures is more than the estimated loss resulting from a threat or vulnerability (C > L). Legally the remaining residual risk is not counted when deciding whether a company is liable.
99
ITIL
Best practices for IT core operational processes, not for audit. This includes Service, change, release, and configuration, Strong end-to-end customer focus/expertise. Focused on services and service strategy.
100
Goal of Risk Management
Goal is to determine impact of threat and risk of threat occuring, then reduce risk to an acceptable level.
101
Step 1: Categorise
Categorise the information system and the information processed, stored, and transmitted by that system based on an impact analysis.
102
Step 2: Risk Management
Conduct Assessment:
- ID threat sources and events
- ID vulnerabilities and predisposing conditions
- Determine likelihood of occurrence
- Determine magnitude of impact
- Determine risk
103
Step 3: Implement
Implement the security controls and describe how the controls are employed within the information system and its environment of operation
104
Step 4: Assess
Assess the security controls using appropriate assessment procedures to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting the security requirements for the system.
105
Inherent: Types of Risk
Chance of making an error with no controls in place
106
Control: Types of Risk
Chance that controls in place will not prevent, detect or control errors
107
Detection: Types of Risk
Chance that auditors won't find an error
108
Business: Types of Risk
Concerns about effects of unforseen circumstances
109
Overall: Types of Risk
Combination of all risks aka Audit Risk
110
Preliminary Security Assessment (PSE)
Helps to gather the elements that you will need when the actual Risk Analysis takes place.
111
Risk Assessment Steps
1. Prepare
2. Perform
3. Communicate
4. Maintain
112
Qualitative Risk Management Process
1. Approval
2. Form Team
3. Analyse Data
4. Calculate Risk
5. Countermeasure Recommendations
113
Quantitative Risk Analysis
Uses quantitative values to calculate risk
114
Single Loss Expectancy (SLE)
Asset Value * Exposure Factor (% loss of asset). It is the dollar value lost when an asset is successfully attacked.
115
Annual Loss Expectancy (ALE)
SLE * ARO
116
Annualised Rate of Occurance (ARO)
Number of times an event occurs in a year
117
How to address risk
1. Accept: live with it and pay the cost
2. Mitigate: Reduce by implementing controls by calculating costs
3. Assign/Transfer: insure the risk to transfer it. Passing it to another entity.
4. Avoid: stop business activity
118
Loss Formula
Loss = probablity * cost
119
Controls Gap
Is the amount of risk that is reduced by implementing safeguards. A formula for residual risk is as follows: Total Risk - Controls Gap = Residual Risk
120
RTO
Recovery Time Objective: How quickly you need to have that application's information available after downtime has occurred.
121
RPO
Recovery Point Objective: Point in time that application data must be recovered to resume business functions. Amount of data you are willing to lose. For example, you may be willing to loose one day of data.
122
MTD
```
Maximum Tolerable Downtime: Maximum Delay a business can be down and still remain viable.
MTD: minutes to hours = critical
MTD: 24 hours = urgent
MTD 72 hours = important
MTD 7 days = normal
MTD 30 days = non-essential
```
123
Exposure Factor
How much of an asset is exposed to loss, expressed as a percentage (0 to 100%).
124
Factors that effect impact
Human life, dollars, prestige, market share
125
Risk Framework Countermeasures
- Accountability
- Auditability
- Source trusted and known
- Cost effectiveness
- Security
- Protection for CIA of assets
- Other issues created?
126
Primary Controls (types)
Control costs should be less than the value of the asset being protected
127
Administrative/Managerial/Policy
Preventive: hiring policies, screening security awareness (also called soft measures)
Detective: screening behaviour, job rotation, review of audit records
128
Technical (aka Logical)
- Preventive: protocols, encryption, biometrics, smartcards, routers, firewalls
- Detective: IDS and automatic generated violation reports, audit logs, CCTV (never preventative)
- Preventive: fences, guards, locks
- Detective: motion detectors, thermal detectors, video detectors
129
Physical Controls
Things you can see and touch, such as fences, doors and lock, windows
130
Prime Objective
Reduce effects of security threats and vulnerabilities to a tolerable level
131
Risk analysis
Process that analyses threat scenarios and produce a representation of the estimated potential loss
132
Main categories of access control
7 Types of controls
133
Directive control
Specify rules of behaviour
134
Deterrent
Discourage people, change my mind
135
Preventative
Prevent incident or breach
136
Compensating
Substitute for loss of primary controls
137
Detective control
Signal warning, investigate
138
Corrective
Mitigate damage, restore control. For example, correct a system by deleting its virus.
139
Recovery
Restore to normal after incident
140
Preventive Controls
1. Accuracy: data checks, validity checks
2. Security: labels, traffic padding, encryption
3. Consistency: DBMW, data dictionary
141
Detective controls
1. Accuracy: cyclic redundancy
2. Security: IDS, audit trails
3. Consistency: comparison tools
142
Corrective controls
1. Accuracy: checkpoint backups
2. Security: emergency response
3. Consistency: database controls
143
Functional order in which controls should be used
1. Deterrence
2. Denial
3. Detection
4. Delay
144
Penetration Testing
Testing a network's defenses by using the same technique as external intruders
145
Scanning and probing
Port scanners (such as nmap)
146
Sniffing
Capturing data packets
147
Demon Dialing
War dialing for modems
148
Dumpster diving
Searching paper disposal areas
149
Social engineering
Most common, get information by asking
150
Types of Penetration Testing
Blue Team: Had knowledge of the organisation, can be done frequent and least expensive
Red Team: is external and stealthy
151
White Box Testing
Ethical hacker knows what to look for, see code as a developer
152
Grey Box Testing
Partial knowledge of the system, see code, act as a user
153
Black Box
Hacker does not know what to find
154
4 Stages of Pen Testing
1. Planning
2. Discovery: recon/discover, and enumeration
3. Attack: Vulnerability analysis, and execution/exploitation
4. Reporting: document findings/reporting
155
Vulnerabilities exploited
Kernal flaws, buffer overflows, symbolic links, file descriptor attacks
156
Other Model
Footprint network (information gathering) port scans, vulnerability mapping, exploitation, report scanning, tools are used in penetration tests
157
Flaw hypotheses methodology
Operating system penetration testing
158
Penetration testing strategy
External, internal, blind, double blind.
| Categories: zero, partial, full knowledge tests
159
Deming Cycle
1. Plan: ID opportunity and plan for change
2. Do: implement change on small scale
3. Check: Use data to analyse results of change
4. Act: If change successful, implement wider scale, if fails begin, cycle again
160
Identification of threat
Individuals must be qualified with the appropriate level of training. This includes:
- Developing job descriptions
- Contact references
- Screen/investigate background
- Develop confidentiality agreements
- Determine policy on vendor, contractor, consultant and temporary staff access
161
Software Licenses
1. Public Domain; available for anyone to use
2. Open Source: source code made available with a license in which the copyright holder provide the rights to study, change, and distribute the software to anyone
3. Freeware: proprietary software that is available for use at no monetary cost. May be used without payment but may usually not be modified, re-distributed or reverse-engineered without the author's permission.
162
Assurance
Degree of confidence in satisfaction of security requirements. Is another word for security
163
Successful Requirements Gathering
Don't assume what client wants, involve users early, define and agree on scope.
164
Security awareness
Technical training to react to situations, best practices for security and network personnel. Employees need to understand policies.
Formal security awareness training provides exact prep on how to do things.
165
Wire Tapping
Eavesdropping on communication - only legal with prior consent or warrant
166
Data Diddling
Act of modifying information, progrms, or documents to commit fraud, tampers with INPUT data
167
Privacy Laws
Data collected must be collected fairly and lawfully and used only for the purpose for the purpose it was collected
168
Water holing
Create a bunch of websites with similar names
169
Work function (factor)
The difficulty of obtaining the clear text from the cipher text as measured by cost/time
170
Fair Cryptosystms
In this escrow approach, the secret keys used in a communication are divided into two or more pieces, each of which is given to an independent third party. When the government obtains legal authority to access a particular key, it provides evidence of the court order to each of the third parties and then reasembles the secret key.
171
SLA
Agreement between IT service provider and customer, document service levels, divorce: how to dissolve relationship
172
SLR (requirement)
Requirements for a service from client viewpoint
173
Service Level Report
Insight into a service providers ability to deliver the agreed upon service quality
174
FISMA (federal agencies)
The Federal Information Security Management Act (FISMA), passed in 2002, requires that federal agencies implement an information security program that covers the agency’s operations. FISMA also requires that government agencies include the activities of contractors in their security management programs.
175
Two phases of FISMA
Phase 1: categorising, selecting minimum controls, assessment
Phase 2: create national network of secure services to assess
176
ISO/IEC 27799
Known as the health informatics, and its purpose is to provide guidance to health organisations and other holders of personal health information on how to protect such information via implementation of ISO/IEC 27002.
177
Process improvement models
1. Six Sigma: Business management strategy that can be used to carry out process improvement
2. CMMI: organisational development for process improvement developed by Carnegie Mellon
178
Emergency procedures (BCP)
Are carried out to protect human life, and then other procedures need to be executed to reduce the damage from other threats.
179
Prudent Rule Man/Reasonable Person Test
The prudent man rule requires that senior executives take personal responsibility for ensuring the due care that ordinary, prudent individuals would exercise in the same situation. The rule originally applied to financial matters, but the Federal Sentencing Guidelines applied them to information security matters in 1991.
180
Gramm-Leach-Bliley Act of 1999 (GLBA)
Requires financial institutions to provide written privacy policies to all their customers.
181
STRIDE
```
Threat modelling technique.
S: Spoofing
T: Tampering
R: Repudiation
I: Information disclosure
D: Denial of access
E: Elevation of privilege
```
182
Reduction Analysis
Threat modelling diagramming where a greater understanding of the logic of the product as well as its interactions with external elements.
183
Communications Assistance for Law Enforcement Act (CALEA) 1994
Requires all carriers to make wiretaps possible for law enforcement with an appropriate court order, regardless of the technology in use.
184
Step 5: Authorise (risk management framework)
Authorise information system operation based on a determination of the risk to organisational operations and assets, individuals, other organisations, and the country resulting from the operation of the information system and the decision that this risk is acceptable.
185
Step 6: Monitor (risk management framework)
Monitor the security controls in the information system on an ongoing basis including assessing control effectiveness, documenting changes to the system or its environment of operation, conducting security impact analyses of the associated changes, and reporting the security state of the system to designated organisational officials.
