Security pillar principles in AWS - Step-by-Step Execution

Process Flow - Security pillar principles

Identify sensitive data

↓

Control access tightly

↓

Protect data in transit and at rest

↓

Monitor and log activity

↓

Respond to security events

↓

Review and improve

This flow shows the main steps to keep cloud systems secure, from knowing what to protect to improving security over time.

Execution Sample

AWS

1. Identify sensitive data
2. Set access permissions
3. Encrypt data
4. Enable logging
5. Respond to alerts

This sequence outlines the key actions to secure cloud resources step-by-step.

Process Table

Step	Action	Purpose	Result
1	Identify sensitive data	Know what needs protection	List of sensitive resources created
2	Set access permissions	Limit who can see or change data	Access policies applied
3	Encrypt data	Protect data from unauthorized reading	Data encrypted at rest and in transit
4	Enable logging	Record activity for audits and alerts	Logs start capturing events
5	Respond to alerts	Act on suspicious activity quickly	Security incidents handled
6	Review and improve	Keep security up to date	Security posture enhanced
Exit	All steps done	Security principles applied	Cloud environment secured

💡 All security pillar principles steps completed to protect cloud resources

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
SensitiveDataList	empty	identified	identified	identified	identified	identified	identified
AccessPermissions	none	none	set	set	set	set	set
EncryptionStatus	none	none	none	enabled	enabled	enabled	enabled
LoggingStatus	off	off	off	enabled	enabled	enabled	enabled
IncidentResponse	none	none	none	none	none	active	active

Key Moments - 3 Insights

Why do we identify sensitive data first before setting permissions?

Because without knowing what data is sensitive (see Step 1 in execution_table), we cannot decide who should have access (Step 2).

Is encryption enough to secure data?

No, encryption protects data but logging and response (Steps 4 and 5) are also needed to detect and handle threats, as shown in the execution_table.

Why enable logging after setting permissions and encryption?

Logging records what happens after protections are in place, so we can monitor if they work or if there are attacks (Step 4 in execution_table).

Visual Quiz - 3 Questions

Look at the execution_table, what is the result after Step 3?

A Logs start capturing events

B Data encrypted at rest and in transit

C Access policies applied

D Security incidents handled

💡 Hint

Check the 'Result' column for Step 3 in the execution_table

At which step does logging get enabled according to the execution_table?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the 'Action' column and find when 'Enable logging' happens

If we skip identifying sensitive data, which variable in variable_tracker remains empty?

A SensitiveDataList

B AccessPermissions

C EncryptionStatus

D LoggingStatus

💡 Hint

Check the 'SensitiveDataList' row in variable_tracker for its initial and after Step 1 values

Concept Snapshot

Security Pillar Principles:
1. Identify sensitive data to protect
2. Set strict access controls
3. Encrypt data in transit and at rest
4. Enable logging to monitor activity
5. Respond quickly to security events
6. Review and improve regularly

Full Transcript

The security pillar principles guide how to protect cloud resources. First, identify what data is sensitive. Then, set access permissions to limit who can use it. Next, encrypt data to keep it safe from unauthorized reading. Enable logging to track activity and detect problems. Respond quickly to any security alerts. Finally, review and improve security continuously to stay safe.