Cybersecurity

Front 1

IS Risk Management.

Back 1

Threats (bad things, cause harm);

Vulnerabilities (weakness in systems/policies; exploited to cause damage.

Impacts ( consequences when threat exploits vulnerability )

Front 2

Computer crime

Back 2

Using a computer to commit an illegal act.

Front 3

Hacking

Back 3

Gain access without permission

Front 4

Cracking

Back 4

Illegal access, do damage or commit crime.

Front 5

Hacktivists

Back 5

Political/ideological graffiti (website defacement)

Front 6

Cyberterrorist

Back 6

Plant destructive programs; threaten to activate for ransom.

Front 7

Industrial Espionage

Back 7

Covert activities; theft; trade secrets; blackmail etc.

Front 8

Risk

Back 8

Possibility that threat will exploit a vulnerability

Front 9

Asset

Back 9

Monetary value of a configuration item

Front 10

Vulnerability

Back 10

Weakness that can be exploited

Front 11

Threat

Back 11

Exploits a vulnerability

Front 12

Risk Management Process

Back 12

1. Identify Risk

2. Analyze and Prioritize

3. Mitigate

4. Audit the RM plan

Front 13

Breach impact

Back 13

Fines

Loss of intellectual property

Loss of reputation and customers

Loss of employees

Loss of stakeholders confidence

Front 14

Network Address Translation (NAT)

Back 14

Many computers share same public IP address

Front 15

Risk Analysis

Back 15

Quantitative (mathematical)

Qualitative (severity level)

Front 16

Defense in depth (layers)

Back 16

Network security

Front 17

Mission critical system protection

Back 17

Information Assurance

Risk Management

Defense in depth

Contingency planning

Front 18

Cybersecurity goals

Back 18

Confidentiality

Integrity

Availability

Nonrepudiation

Authentication

Front 19

Encryption

Back 19

Maintains confidentiality

Front 20

Obstacles

Back 20

Human

Technological

Front 21

CIA

Back 21

Confidentiality

Integrity

Availability

Front 22

AAA

Back 22

Assurance

Authenticity

Anonymity

Front 23

Assurance = trust

Back 23

Policies

Permissions

Protections

Front 24

Authenticity

Back 24

Nonrepudiation - cannot be denied

Digital signatures

Front 25

Anonymity

Back 25

Aggregation

Mixing

Proxies

Pseudonyms

Front 26

Threats

Back 26

Eavesdropping -- data interception

Alteration -- data modification

Denial-of-service -- data interruption

Masquerading -- data fabrication

Repudiation -- denial of data assurance

Correlation -- data integration to discover the source

Front 27

Economy of mechanism

Back 27

Simplicity in design or implementation of security measures

Front 28

Fail-safe defaults

Back 28

Default configuration should have a conservative protection scheme

Front 29

Complete mediation

Back 29

Access to a resource must be checked for compliance with the protection scheme.

Front 30

Open design

Back 30

Security shouldn't rely on keeping source code secret. It should rely only on keeping cryptographic keys secret.

Security through obscurity.

Front 31

Separation of privilege

Back 31

Access control through meeting multiple conditions.

Component separation.

Front 32

Least privilege

Back 32

Bare minimum privileges to accomplish task.

Front 33

Least common mechanism

Back 33

Minimize sharing of resources. Users should use separate channels to access a shared resource.

Front 34

Psychological acceptability

Back 34

Well designed and intuitive UI. Minimize differences to avoid user confusion.

Front 35

Work factor

Back 35

Security scheme should fit the risk. No need to use a sledgehammer to kill a mosquito.

Front 36

Compromise recording

Back 36

Sometimes better to log an intrusion than to spend resources preventing the break in.

Front 37

Risk framework

Back 37

Threat

Vulnerability

Risk

Attack

Target

Hint 37

You need all five of these to have a problem. Take away any one of them and you eliminate the problem.

Front 38

Unified Threat Management (UTM)

Back 38

Blacklist

Firewall, antivirus, IDS

Whitelist

Applocker