Domain 3 – Security Architecture & Engineering
DomainStudy
3 –Guide.pdf
Security Architecture & Engineering
DomainStudy
3 –Guide.pdf
Security Architecture & Engineering Study Guide.pdf
Domain 3 – Security Architecture &
Engineering Study Guide
Guidehttps://www.stuvia.com/dashboard!@_)#*)(@$)($@*($@)($@*_
Domain 3 – Security Architecture & Engineering
DomainStudy
3 –Guide.pdf
Security Architecture & Engineering
DomainStudy
3 –Guide.pdf
Security Architecture & Engineering Study Guide.pdf
,Domain 3 - Security Architecture & Engineering.pdf Domain 3 - Security Architecture & Engineering.pdf Domain 3 - Security Architecture & Engineering.pdf
Terms in this set (70)
Zero Trust Security Addresses legacy perimeter-based security model.
Treats user idenity as the control plane (new-perimeter)
Verify Identity - Manage Devices - Manage Apps - Protect Data
Privacy by Design Making privacy an integral part of every system, technology, policy, and
design process.
1. Proactive - Privacy is the default - not reactive
2. Privacy must be embedded in the design
3. Positive-sum approach not zero-sum (needs of everyone involved are
met aka win-win)
4. Data protecting from End to end of life-cycle
5. Visibility and transparency (Privacy Policy)
7. Keep privacy user-centric
Domain 3 - Security Architecture & Engineering.pdf Domain 3 - Security Architecture & Engineering.pdf Domain 3 - Security Architecture & Engineering.pdf
, Domain 3 - Security Architecture & Engineering.pdf Domain 3 - Security Architecture & Engineering.pdf Domain 3 - Security Architecture & Engineering.pdf
Micrsoservices are fine-grained services with a discrete function (modern version of SOA
which are discrete services access by users in a blackbox function)
Containerization Lightweight, granular, and portable way to package applications for
multiple platforms - reduces overhead of server virtualization by enabling
containerized apps to run on a shared OS kernel - containers don't have
their own OS.
Containerization is commonly done through Kubernetes or Docker. Still
requires isolation for security reasons.
Domain 3 - Security Architecture & Engineering.pdf Domain 3 - Security Architecture & Engineering.pdf Domain 3 - Security Architecture & Engineering.pdf
DomainStudy
3 –Guide.pdf
Security Architecture & Engineering
DomainStudy
3 –Guide.pdf
Security Architecture & Engineering Study Guide.pdf
Domain 3 – Security Architecture &
Engineering Study Guide
Guidehttps://www.stuvia.com/dashboard!@_)#*)(@$)($@*($@)($@*_
Domain 3 – Security Architecture & Engineering
DomainStudy
3 –Guide.pdf
Security Architecture & Engineering
DomainStudy
3 –Guide.pdf
Security Architecture & Engineering Study Guide.pdf
,Domain 3 - Security Architecture & Engineering.pdf Domain 3 - Security Architecture & Engineering.pdf Domain 3 - Security Architecture & Engineering.pdf
Terms in this set (70)
Zero Trust Security Addresses legacy perimeter-based security model.
Treats user idenity as the control plane (new-perimeter)
Verify Identity - Manage Devices - Manage Apps - Protect Data
Privacy by Design Making privacy an integral part of every system, technology, policy, and
design process.
1. Proactive - Privacy is the default - not reactive
2. Privacy must be embedded in the design
3. Positive-sum approach not zero-sum (needs of everyone involved are
met aka win-win)
4. Data protecting from End to end of life-cycle
5. Visibility and transparency (Privacy Policy)
7. Keep privacy user-centric
Domain 3 - Security Architecture & Engineering.pdf Domain 3 - Security Architecture & Engineering.pdf Domain 3 - Security Architecture & Engineering.pdf
, Domain 3 - Security Architecture & Engineering.pdf Domain 3 - Security Architecture & Engineering.pdf Domain 3 - Security Architecture & Engineering.pdf
Micrsoservices are fine-grained services with a discrete function (modern version of SOA
which are discrete services access by users in a blackbox function)
Containerization Lightweight, granular, and portable way to package applications for
multiple platforms - reduces overhead of server virtualization by enabling
containerized apps to run on a shared OS kernel - containers don't have
their own OS.
Containerization is commonly done through Kubernetes or Docker. Still
requires isolation for security reasons.
Domain 3 - Security Architecture & Engineering.pdf Domain 3 - Security Architecture & Engineering.pdf Domain 3 - Security Architecture & Engineering.pdf
