Security Architecture Flashcards

(40 cards)

1
Q

Outlines the division of responsibility between the cloud service provider and the customer

A

Responsibility Matrix

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

Provide specialized services that end efficiency of cloud solutions

A

Third-Party Vendors

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

Combine on-premise infrastructure, private cloud service, and public cloud services

A

Hybrid Solution

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

Computing infrastructure that’s physically located on-site at a business

A

On-premise Solutions

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

System’s ability to be accessed when needed

A

Availability

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

System’s ability to recover from failures and continue to function

A

Resilience

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

It’s essential to consider both the immediate and long-term costs of cloud adoption

A

Cost

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

Speed at which the system can adapt to changes in demand

A

Responsiveness

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

Cloud services are easier to deploy than on-premise solutions

A

Ease of Deployment

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

When using the cloud services, some risks are transferred to the provider

A

Risk Transference

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

Cloud service providers regularly release patches to fix vulnerabilities

A

Patch Availability

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

Businesses might not be able to apply patches due to compatibility issues

A

Inability to Patch

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

Customers don’t have to worry about power consumption

A

Power

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

Amount of computational resources that a customer can use

A

Compute

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

Can lead to vulnerabilities if one user’s data is compromised

A

Shared Physical Server Vulnerabilities

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

Can lead to unauthorized access, data breaches, and other security incidents

A

Inadequate Virtual Environment Security

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

Can lead to unauthorized access to sensitive data and systems

A

User Access Management

18
Q

Can lead to leaving the system vulnerability to new threats

A

Lack of Up-to-date Security Measures

19
Q

Can lead to a complete system outage affecting all users

A

Single Points of Failure

20
Q

Can lead to allowing unauthorized users to gain access to cloud systems

A

Weak Authentication and Encryption Practices

21
Q

Lack of clear guidelines or procedures for various security aspects

A

Unclear policies

22
Q

Residual data left behind after deletion or erasure processes

A

Data Remnants

23
Q

Technology that allows for the emulation of servers

A

Virlualization

24
Q

Lightweight alternative to full machine virtualization

A

Containerization

25
Known as a bare metal or native hypervisor, it runs directly on the host hardware and functions similarily to an operating system
Type 1
26
Operates within a standard operating system, such as Windows, MAC, or Linux
Type 2
27
Occurs when an attacker is able to break out of one of these normally isolated virtual machines
Virtual Machine Escape
28
Occurs when a user is able to gain the ability to run functions as a higher level user
Privilege Elevation
29
When a virtual machine needs to move from one physical host to another
Live Migration of Virtual Machines
30
Concept in computing where system resources like memory or processing power are reused
Resource Reuse
31
Model where the responsibility of managing servers, databases, and some application logic is shifted away from developers
Serverless
32
One of the most significant risks of serverless computing
Vendor Lock-in
33
A software architecture where large applications are broken down into smaller and independent services
MicroServices
34
Isolation of a network by removing any direct or indirect connections from other networks
Physical Separation/Air Gapping
35
Creates boundaries within a network, restricting access to certain areas
Logical Separation
36
Enables efficient network configuration to improve performance and monitoring
SDN
37
Also called the forwarding plane that is responsible for handling packets and makes decisions based on protocols
Data Plane
38
The brain of the network that decides where traffic is sent and is centralized in SDN
Control Plane
39
The plane where all network applications interacting with the SDN controller reside
Application Plane
40
A configuration that lacks consistency that might introduce risks, so it has to be eliminated
Snowflake System