Skip to content

Commit 069084c

Browse files
committed
update Cybersecurity Primer
1 parent db60fa2 commit 069084c

1 file changed

Lines changed: 52 additions & 33 deletions

File tree

src/content/posts/cybersecurity-primer.md

Lines changed: 52 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -12,29 +12,38 @@ CIA
1212

1313
# Strategies
1414

15-
Threat Modeling
16-
- Red Teaming, what can an adversary do?
17-
- Insider Threats
18-
- Social Engineering
19-
- Attack Surface
15+
Three strategies for understanding Cybersecurity:
16+
- threat-based
17+
- risk-based
18+
- systems-based
19+
20+
## Threat Modeling
21+
22+
- Red Teaming. What can an adversary do?
23+
- Insider Threats. Usually worst case scenario, hard to detect. Attacker wants to hijack real accounts and become the insider.
24+
- Attack Surface. Where are we exposed?
25+
- Social Engineering. People are often the weak link.
26+
27+
## Risk Management
2028

21-
Risk Management
2229
- Assessment
2330
- Authorization
2431
- Compliance
2532

26-
Systems Engineering
33+
## Systems Engineering
34+
2735
- Data
2836
- Users
2937
- Software
3038
- Hardware
3139
- Network
32-
- Understand the system. What is in it, how they interact.
40+
41+
Understand the system. What is in it, how they interact.
3342

3443
Systems include
3544
- Data - category, classification, types
36-
- Users - Roles, Permissions, Administrators/Privileged/Root/Super
37-
- Software - Where did it come from? Supply chain, who made it, what does it do? how is it configured?
45+
- Users - roles, permissions, administrators/privileged/root/super
46+
- Software - where did it come from? supply chain, who made it, what does it do? how is it configured?
3847
- Hardware - inventory, physical access, supply chain, cloud/IaaS
3948
- Network - Ports, Protocols, Services (PPSM)
4049

@@ -103,7 +112,8 @@ Who is allowed to access what?
103112
Examples of who:
104113
- a person
105114
- a computer
106-
- an identity delegated to person or computer
115+
- an identity, role, or group
116+
- could be delegated to person or computer
107117

108118
Access Control patterns
109119
- Passwords
@@ -129,28 +139,37 @@ Access Control patterns
129139

130140
# Risk Management Framework
131141

132-
- Every system must be Assessed
133-
- Every system must be Authorized
134-
- Authority to Operate
135-
- System is defined by a boundary and what is in it
136-
- Information types
137-
- Who can access
138-
- What components
139-
- Connections. In/out, relationships with other systems
140-
- Sound familiar? This is restatement of the Systems Engineering Strategy: Data, Users, Software, Hardware, Network
141-
- Controls - The safeguards or countermeasures prescribed for an information system or an organization to protect the confidentiality, integrity, and availability of the system and its information.
142-
- 20 control families
143-
- around 1200 unique controls
144-
- Inheritance makes this manageable
145-
- Control selection prioritizes which controls to implement
146-
- Control assessment determines whether a control is implemented
147-
- Risk Assessment
148-
- Threat
149-
- Impact
150-
- Likelihood
151-
- STIG = Secure Technical Implementation Guide
152-
- Standardizes the questions to ask during Assessment
153-
- Maps directly to the controls
142+
Every system must be Assessed and Authorized. An Authority to Operate (ATO) specifies the controls that must be implemented.
143+
144+
System is defined by a boundary and what is in it.
145+
146+
- Information types
147+
- Who can access
148+
- What components
149+
- Connections. In/out, relationships with other systems
150+
151+
Sound familiar? This is restatement of the Systems Engineering Strategy: understand Data, Users, Software, Hardware, Network
152+
153+
Controls are the safeguards or countermeasures prescribed for an information system or an organization to protect the confidentiality, integrity, and availability of the system and its information.
154+
155+
- 20 control families
156+
- around 1200 unique controls
157+
- Control selection prioritizes which controls to implement
158+
- Control assessment determines whether a control is implemented
159+
- Inheritance makes this manageable
160+
- Informally, a control, simply asks a question.
161+
162+
Risk Assessment
163+
164+
- Threat
165+
- Impact
166+
- Likelihood
167+
168+
STIG
169+
170+
- Secure Technical Implementation Guides (STIG)
171+
- Standardizes the questions to ask during Assessment
172+
- Maps directly to the controls
154173

155174
# Scenarios
156175

0 commit comments

Comments
 (0)