# Security

Security is the protection of systems, data, and operations against unauthorized access, misuse, disruption, and loss.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/security

> Security combines technical controls, operational processes, and clearly assigned responsibilities to preserve confidentiality, integrity, and availability. In the cloud, providers secure the underlying infrastructure while customers configure and operate their workloads securely, using capabilities such as identity controls, encryption, network protection, and threat detection.

Practice exams covering Security: [AIF-C01 AWS Certified AI Practitioner](https://blowstack.com/practice-exams/aws-certified-ai-practitioner), [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner).

## 7 key aspects of Security

Effective security combines clear responsibilities, least privilege, encryption, layered protection, continuous monitoring, and verifiable governance.

1. **Confidentiality, integrity, and availability**: Protect information from unauthorized disclosure and modification while keeping required systems accessible. Evaluate controls against all three goals, because a control that protects data but prevents legitimate access can still harm the workload.
2. **Shared responsibility**: Separate provider infrastructure duties from customer workload duties. Document who manages operating systems, identities, data, and configurations for each service rather than assuming all managed services have the same responsibility boundary.
3. **Least-privilege access**: Grant only the actions and resource access needed for a specific task. Prefer temporary credentials, protect human access with multifactor authentication, and remove permissions that are no longer required.
4. **Encryption and key management**: Protect stored data and network traffic with appropriate encryption. Control access to encryption keys and plan their lifecycle carefully, because lost or deleted keys can affect data availability.
5. **Defense in depth**: Combine identity, network, application, and data controls so that one failure does not expose the entire workload. For example, restrict database connectivity even when application authentication is already enforced.
6. **Continuous detection and response**: Collect relevant activity records, assess vulnerabilities, and investigate suspicious behavior. Assign ownership for alerts and test response procedures instead of treating enabled monitoring as a completed security program.
7. **Governance and verifiable controls**: Translate organizational requirements into enforceable policies and repeatable configurations. Maintain evidence that controls operate correctly; provider compliance documentation supports this process but does not replace customer validation.

## Cloud services for Security

These services address complementary security needs. IAM limits who can access resources, while AWS KMS controls the keys used to protect encrypted data. AWS WAF filters application requests, and AWS Shield helps protect availability against distributed denial-of-service attacks. CloudTrail supplies activity records for auditing and investigation, while GuardDuty identifies potential threats from supported data sources. Engineers connect these capabilities through carefully scoped permissions, protected log storage, alert routing, and tested response workflows. No single service secures an entire workload: customers must configure the controls, review findings, and verify that their applications and operational practices remain secure.

- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: CloudTrail records supported AWS account activity for auditing and investigation. Event history provides the last 90 days of management events in each AWS Region; trails or event data stores support broader retention and collection, while data events require appropriate configuration.
- **[Amazon GuardDuty](https://blowstack.com/tools/cloud-services-hub/amazon-guardduty)**: GuardDuty analyzes supported AWS data sources to detect potential threats such as suspicious API activity and signs of compromised workloads. Findings support investigation and response but do not automatically resolve every detected issue.
- **[AWS WAF](https://blowstack.com/tools/cloud-services-hub/aws-waf)**: AWS WAF applies rules to HTTP and HTTPS requests reaching supported resources. Engineers use it to filter unwanted traffic, rate-limit requests, and reduce exposure to common web attacks; it does not replace secure application code.
- **[AWS Shield](https://blowstack.com/tools/cloud-services-hub/aws-shield)**: AWS Shield provides distributed denial-of-service protection for AWS resources. Shield Standard is automatically included at no additional charge, while Shield Advanced is a paid subscription offering additional protections and response capabilities for eligible resources.

## Security exam questions

Real practice exam questions on Security, with the correct answer and its explanation.

### Question 1 (AIF-C01)

**Question:**

A company runs a generative AI document-summarization application on an Amazon EC2 instance. The application must read source documents from one designated Amazon S3 bucket. The security team requires that the application receive only the necessary read permissions and that no long-term AWS access keys be stored or managed for the application. Which solution best meets these requirements?

**Correct answer:** Attach an IAM role to the EC2 instance that allows only the required read operations on source documents in the designated bucket.

**Explanation:** An IAM role attached to the EC2 instance provides automatically managed temporary credentials. Limiting the role's permissions to the required read operations and documents also follows the principle of least privilege.

### Question 2 (CLF-C02)

**Question:**

A company encrypts its customer records at rest and uses HTTPS when transmitting them. To reduce costs, a manager proposes removing the company's backups because the records are already protected by encryption. The company must be able to recover records that employees accidentally delete. Which assessment should guide the company's decision?

**Correct answer:** Backups should be retained because encryption protects the confidentiality of records but does not recover deleted records.

**Explanation:** Encryption helps prevent unauthorized parties from understanding data. Recoverable backups address a different security need: restoring data after deletion or loss.

## Practice Security in a full exam

Questions on Security in each practice exam, with every answer option and an explanation for each:

- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 3 questions
- [AIF-C01](https://blowstack.com/practice-exams/aws-certified-ai-practitioner): 1 question

## What is Security

Security protects the confidentiality, integrity, and availability of information and systems. Confidentiality means only authorized parties can access information; integrity means information and configurations are protected against unauthorized changes; availability means systems remain accessible when needed. Engineers apply security by identifying valuable assets and likely threats, selecting controls, and checking that those controls remain effective as workloads change.

Cloud security follows a shared responsibility model. AWS is responsible for security of the cloud, including physical facilities and the infrastructure supporting its services. Customers are responsible for security in the cloud, including their data, access permissions, and workload configurations. The boundary depends on the service: customers patch the guest operating system on an Amazon EC2 instance, while AWS handles more of the underlying platform maintenance for managed services. Using a managed service reduces some operational duties but does not remove responsibility for access controls or data protection.

Identity is a primary security boundary. Grant people and applications only the permissions needed for their tasks, use temporary credentials where possible, and require multifactor authentication for sensitive human access. For example, an application that reads invoices should receive permission to read the required storage objects, not administrative access to the entire account. Avoid using root credentials for routine work, and review permissions as job roles and application requirements change.

Encryption is an important benefit of cloud security capabilities. Encryption at rest protects stored information, while encryption in transit, commonly implemented with TLS, protects information moving between endpoints. Managed key services can simplify key protection, access control, and auditing. However, encryption does not prevent an authorized identity from reading data, fix excessive permissions, or secure a compromised application. Key permissions and lifecycle decisions also matter: disabling or deleting a required key can make encrypted data unavailable.

Network and application controls provide additional protection. Security groups filter traffic to associated resources, while network ACLs provide subnet-level filtering. Web application firewalls inspect supported HTTP and HTTPS traffic for unwanted requests, and distributed denial-of-service protections help maintain availability during attacks. For a public application, engineers might expose only its load balancer, restrict database access to the application tier, and apply web filtering at the entry point. A private subnet alone does not guarantee that a workload is secure.

Detection and response complement preventive controls. AWS provides capabilities for API activity auditing, threat detection, vulnerability assessment, and configuration evaluation. AWS CloudTrail records supported account activity, Amazon GuardDuty analyzes supported data sources for suspicious behavior, Amazon Inspector assesses supported workloads for vulnerabilities, and AWS Config can evaluate resource configurations against rules. These tools have different purposes: an audit log is not automatically a threat detector, and a finding is not proof that remediation has occurred. Teams must route findings, investigate them, and maintain tested response procedures.

Cloud platforms make security controls easier to deploy consistently through APIs, infrastructure as code, and centralized policies. Provider compliance reports, available through resources such as AWS Artifact, can support customer assurance and audit work, but a provider's certification does not automatically make a customer workload compliant. Customers still need appropriate configurations, evidence, and operating procedures. Security also has trade-offs: detailed logging creates storage and analysis costs, restrictive controls can disrupt legitimate operations, and stronger isolation can increase architectural complexity. Effective security uses layered controls proportional to risk, tests changes, and regularly verifies that protection remains in place.

## Learn Security in lessons

3 short lessons on Security in 2 certification courses.

- AIF-C01: AWS Compliance versus Security (Premium), https://app.blowstack.com/lessons/aws-compliance-versus-security-aif-c01
- CLF-C02: Security: layered protection in AWS (Premium), https://app.blowstack.com/lessons/security-layered-protection-in-aws-clf-c02
- AIF-C01: Security: layered protection for generative AI (Premium), https://app.blowstack.com/lessons/security-layered-protection-for-generative-ai-aif-c01
