Introduction Flashcards

1
Q

What are the 4 components involved in building dependable systems?

A

Policy ( what you are supposed to achieve)
Mechanisms (measures and controls used to implement the policy)
Assurance (amount of reliance you can place on each mechanism and how well the mechanisms work together)
Incentive (motive of people guarding and maintaining the system to do their job properly and motive over attackers to jeopardise the policy)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Define asset

A

Something that has value to the organisation (tangible or intangible)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Define threat

A

Potential cause of an incident that may harm the assets of an organisation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Define threat agent

A

Party that is responsible for opposing a threat to a system.
Could be human (intentional vs unintentional) or natural (e.g. disaster)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Define vulnerability

A

A weakness in a system that can be exploited by a threat agent

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Define risk

A

The potential that a threat agent would exploit the vulnerability and adversely impact the system.
risk = impact * likelihood

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Define attack

A

Action of exploiting a vulnerability to compromise a system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Define security policy

A

Set of rules that defined the assets to protect, the security objectives to achieve, the standards to follow and constraints of a security program

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Define security controls

A

Measures to protect a system according to a security policy

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Define confidentiality

A

Protecting information and assets from unauthorised access

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Define integrity

A

Ensuring accuracy and completeness of data and processes and protecting them from unauthorised modification

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Define availability

A

Ensuring that data and services are available to the system users and preventing unorganised impairment of functionality

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Define accountability

A

Actions can be traced to responsible users/entities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Define non-repudiation

A

Committed actions cannot be denied by responsible actors

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Define authentication

A

Verifying the identity of the user of process to grant access to resources

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are the types of security activities?

A

Source code auditing (manual or automated review of source code to identify flaws and sources of vulnerabilities)
Software component analysis (investigating third-party and source software components for security risks)
Vulnerability scanning (using automated scanners to identify potential vulnerabilities or flaws)
Vulnerability assessment (manual verification of vulnerabilities to confirm exposure, without exploiting)
Penetration testing (exploiting identified vulnerability to gain further access, simulating and attack)
Red teaming (holistic offensive approach to simulate how real world adversaries can attack a system)
Security audit (evaluation of security controls in relation to their compliance with security objectives, policies or standards)
Security review (verifying that security policy and standards have been applied through performing gap analysis and reviewing design/implementation documents, code reviews and testing reports)

17
Q

What are the types of security flaw classifications?

A

Input validation and representation
API abuse
Security features
Time and state
Errors
Code quality
Encapsulation
+1 Environment