In this section of the course,
we're going to cover security architecture.
Now, security architecture refers
to the design, structure and behavior
of an organization's information security environment.
It encompasses various components such as hardware,
software, processes and people,
to protect the organization's information assets.
So in this section of the course,
we'll be covering Domain 3 and Domain 4,
specifically focused on objective 3.1 and objective 4.1.
Objective 3.1 states that you must be able
to compare and contrast security implications
of different architecture models.
And objective 4.1 states
that given a scenario you must be able
to apply common security techniques to computing resources.
Now, first we're going to cover on-premise
versus cloud deployments.
On-premise refers to the traditional method
of setting up infrastructure and services locally
within an organization's own premises.
Now this includes servers,
data centers and related hardware.
Cloud computing, on the other hand,
involves delivering computing services over the internet.
This includes your servers, your storage,
your database, your networking, your software,
your analytics and much more.
Next we're going to jump into a discussion on cloud security
and in that lesson,
we'll be covering all the security considerations
when utilizing the cloud
including shared physical server vulnerabilities,
inadequate virtual environment security,
user access management,
lack of up-to-date security measures,
single points of failure,
weak authentication and encryption practices,
unclear policies and data remnants.
Then, we're going to talk about virtualization
and containerization.
And we'll be discussing different virtualization types,
containerization, the benefits and risks of utilizing both,
and we'll also go over some of the vulnerabilities
like VM escape and resource reuse.
After that, we're going to be discussing serverless.
Now, serverless computing is a model
where the cloud provider dynamically manages the allocation
and provisioning of your servers.
Developers don't need to worry about the server management
and the capacity planning.
Instead, they just focus on writing their code.
Next, we'll discuss microservices.
And microservices are an architectural style
that structures an application as a collection
of small autonomous services,
and each one performs a specific business function.
Then, we'll take a look at network architecture
and we'll go over the use of physical separation
like air gaps versus logical separation
and things like that, as well as subnetting.
After that, we'll dive into the software-defined networking
space covering SDNs.
Now, SDNs are an approach to network management
that allows dynamic, programmatic,
efficient network configurations in order
to improve network performance and monitoring.
Next, we're going to go over infrastructure as code or IaC.
Now, IaC is a type of IT setup wherein developers
or operations teams can automatically manage
and provision the technology stack for an application
through software rather than using a manual process
to configure discrete hardware devices
and operating systems.
Then, we'll talk about centralized
versus decentralized architectures
by discussing the benefits and risks
of centralized and decentralized architectures.
After that, we'll go over the internet of things,
known as IoT.
Now the internet of things refers to networks
of physical devices, vehicles, appliances
and other items that are embedded
with sensors, software and network connectivity
that enables these objects to connect
and exchange data in near real time.
Next, we'll talk about ICS and SCADA.
Now ICS stands for the industrial control systems
and they're types of control systems
used in industrial production including manufacturing,
transportation, energy and utilities.
SCADA on the other hand,
stands for the supervisory control and data acquisition,
and it's a subset of ICS.
SCADA systems are used to control
and monitor physical processes such as
electricity transmission, gas transportation,
water distribution and wastewater collection.
Then, we'll cover embedded systems.
Now an embedded system is a dedicated computer system
that's designed for one or two specific functions.
This system is embedded as part of a complete device system
that includes hardware such as electrical
and mechanical components too.
And finally, we'll take a short quiz
to see what you learned during this section of the course
and review each of those quiz questions fully
to ensure you can explain why each right answer was right.
So let's go ahead
and jump into the security architecture section
of this course.