Domain 3: Security Architecture Flashcards
Architecture models
Object 3.1
Cloud service models
- three dominant models used in cloud services:
- Software-as-a-Service (SaaS)
- Platform-as-a-Service (PaaS)
- Infrastructure-as-a-Service (IaaS)
- each model provides more or less management on the part of the cloud customer or client
- each model shifts responsibility from cloud to client or from client to cloud
SaaS
-
Software-as-a-Service (SaaS)
- cloud service model where the provider manages the entire cloud infrastructure, including network, servers, operating systems, storage and application capabilities
- Client simply pays for the service and accesses the application, typically via a website or A Program interface (API)
PaaS
-
Platform-as-a-Service (PaaS)
- cloud service model which lies between SaaS and IaaS, where the provider manages all hardware components of the cloud infrastructure (network, servers, storage) and provides a basic web application or data base platform
- in order to turn this platform into a product, software development is required on the part of the cloud client
IaaS
-
Infrastructure-as-a-Service (IaaS)
- cloud service model, which gives the greatest amount of responsibility to the customer. The cloud providers supplies only cloud, infrastructure components (hardware), such as servers, storage and networking.
- clients are responsible for provisioning virtual machines on the hosted servers, creating databases, building applications and everything besides managing the infrastructure components
Cloud deployment models
- a private cloud is one where an organization owns the entire cloud infrastructure and uses it internally. Hosted private means a third-party provides that organization with the cloud infrastructure.
- a public cloud is hosted by a third-party and anyone with an Internet connection can access and subscribe to it
- a hybrid cloud is one that mixes public and private access, combining multiple cloud deployment models into one
- a community cloud is a private cloud that is shared with multiple organizations 
Virtualization
- Operating several virtual machines on one discrete computer
-
Software-defined networking (SDN)
- Firewall, switches and servers were traditionally required hardware. Inside, they are just dedicated computer running software. Why not virtualize them too? By being virtualized, allowing puppies to save on cost in space.
-
Containerization
- Applications can be packaged into a virtual environment, reducing the risk of back in security breaches. Since developers know exactly what environment the application will be running, they are able to easily perform test and thus have a higher level of confidence in the security of the application in the environment.
Infrastructure-as-code
- utilizing automation to create teardown virtual machines and configure/alter software – define networking instances
- Reduces need to be “hands-on” with data center operations
Serverless
- Serverless architecture (also known as serverless computing or function as a service, FaaS) is a software design pattern where applications are hosted by a third-party service, eliminating the need for server software and hardware management by the developer
- Applications are broken up into individual functions that can be invoked and skilled individually
- Hosting an application on the Internet, usually involves managing some kind of server infrastructure. Typically, this means a virtual or physical server that needs to be managed, as well as the operating system and other web server hosting processes required for your application to run

Microservers and APIs
-
Microservices
- architectural style for web applications, where the functionality is divided up across small web services
- software development technique, a variant of the service-oriented architecture (SOA) architectural style structures an application as a collection of loosely coupled services
- Microservices are often connected via API and can leverage some of the same services and tools
-
APIs (A Program Interface)
- Set of subroutine definitions, communication protocols and tools for building software
- framework through which developers can interact with a web application
Network infrastructure
-
physical isolation
- Airgapped
- Logical segmentation
- On-premises
Software – defined networking
- using software to manage a network by separating control and traffic forwarding. Typically utilizes cloud computing.
- Addresses the widespread use of mobile devices, virtualization and cloud computing. The dynamic nature of modern networks makes the traditional hierarchical approach less effective
Embedded systems
Slide 167
- An embedded system is an operating system with a dedicated function, such as a smart washer/dryer, thermostat or traffic light
- embedded systems have traditionally been built with low levels of security, and in users are often unaware of the need for changing default, credentials, and/or performing updates on these types of devices
- Examples of embedded platforms:
- Raspberry Pi
- Arduino
- ESP32
Embedded systems continued
-Industrial Control Systems (ICS)
- Used to monitor, connect and control, large industrial equipment
- If there’s a valve to turn, gauge to read or meter to read, chances are it’s an ICS these days
-SCADA systems
- supervisory control and data acquisition (SCADA) systems
- these devices and their networks should be shielded from outside connections, as they often control systems critical to and areas infrastructure
- ex: the stuxnet worm was used to attack an airgapped SCADA system at the Iranian NATANZ nuclear facility
Embedded systems continued
Slide 170
-
Real-time operating system (RTOS)
- Used to control devices that need to respond in real time and minimize reboot/crashes
- Example: an aircraft autopilot or fly-by-wire controls. If a flight correction is needed, the operating system cannot afford to wait for other process to end. It must immediately make the necessary corrections
-
Special purpose
- Medical devices, vehicles, smart meters and unmanned aerial vehicles (UAVs) are all special-purpose devices
- Like any other device they have firmware/operating systems that could be compromised
- The level of data sensitivity that is compromised can prove disastrous
Embedded architecture considerations
Slide 171
- Availability
- Resilience
- Cost
- Responsiveness
- Scalability
- Ease of deployment
- Ease of recovery
- Patch availability
- inability to patch
- power
- Compute
Enterprise Security
Objective 3.2
Slide 172
Failure modes
- Things go wrong. When something fails, what is the best method for handling the outage?
- two choices when considering security controls:
- Fail-open - allow access in the event of a system failure
- Fail-closed - deny access in the event of the system failure
Inline security
-
Inline detection
- performed by having the packets pass through the detection system
- Allows for active prevention of an attack as it occurs (e.g., NIPS)
-
passive detection
- Inspect traffic from an outside view. System is tapped into the network, but not part of the network connectivity.
- Action taken is reactive, as it must happen after rather than during the detection (NIDS)
Network appliances
• Jump server
• Proxy server
• IDS/IPS
• Load balancer
Jump server or jump box
Slide 176
• System used to manage devices on a separate security zone
• Jump servers are hardened and monitored between separate security zones and provides, and a controlled means between them
• Also known as a jump box or Bastian host
Proxy server
• Proxy
- an application that breaks the connection between client and server
- communications are processed by the proxy when entering or leaving a network and are then forwarded to this recipient if accepted by the proxy
• Forward versus reverse
- A forward proxy is usually referred to simply as a proxy. A proxy proxies for clients, meaning that the proxy makes request and receives responses on behalf of internal clients.
- A reverse proxy does the opposite. Proxies on behalf of the server, receiving request and forwarding responses on behalf of internal servers. 
Proxy server (continued)
• Transparent proxy
- A proxy that receives and for traffic without modifying it (similar to how looking through a clear window does not modify of a view)
- uses include cashing, filtering and acting as a gateway
- conversely, a non-transparent proxy is one which modifies traffics sent through it 
Intrusion detection system (IDS)
• Network Intrusion Detection System (NIDS)
- monitors network, traffic, looking for malicious activity
- If malicious activity is found, a NIDS logs and reports the activity without taking direct action (passive detection)
- essentially a packet sniffer which it identifies and logs, malicious traffic, a NIDS is connected in such a way that it monitors traffic, but traffic does not flow through it
Intrusion Protection System (IPS)
• Network Intrusion Prevention System (IPS)
- monitors network traffic looking for malicious activity and is connected in line, so that traffic must flow through the NIPS device
- Malicious activity is found, a NIPS can take action immediately to remediate the threat, as well as prevent it in the future (inline detection)
Load balancer
• uses a scheduling algorithm to distribute client request among a pool of available servers, ensuring individual servers don’t receive too much traffic
• clients connect to the load balancer, and it chooses which server to assign with the request
• allows for fault tolerance; if one server fails, client request can simply be sent to a different server
Load balancer (continued)
• Round robin
- Method of scheduling where the server notes are set into a certain order and each incoming request is simply passed onto the next server in the list. Once the end of the list is reached, loop back to the beginning of the order.
• Other methods of scheduling
- Select this server, which currently has the fewest number of connections
- select this server which responds fastest