Zero Trust Flashcards
What is trust?
a vulnerability
What shouldn’t be trusted and always verified? (4)
- packets
- identities
- devices
- services
What does eliminating trust help to achieve? (3)
- prevent successful data breaches
- simplify operations through automation and a reduced rulebase
- simplify regulatory compliance and audits because Zero Trust environments are designed for compliance and easy auditing
What does DAAS stand for?
- Data
- Applications
- Assets
- Services
What question needs to be asked when it comes to data?
What data needs to be protected?
proprietary code or processes, personally identifiable information (PII), payment card information (PCI), and personal health information (PHI) such as Health Insurance Portability and Accountability Act (HIPAA) information
What questions needs to be asked when it comes to applications? (2)
- Which applications consume sensitive information?
- Which applications are critical for business functions?
What question needs to be asked when it comes to assets?
Which assets are the most sensitive?
Supervisory Control and Data Acquisition (SCADA) controls, POS terminals, medical equipment, manufacturing equipment, and groups of critical servers
What question needs to be asked when it comes to services?
Which services can attackers exploit to disrupt IT operations and negatively impact the business?
What are the 5 steps of Zero Trust?
- Define your protect surface
- Map the protect surface transaction flows
- Architect a Zero Trust network
- Create the Zero Trust Policy
- Monitor and maintain the network
What is the protect surface?
what is valuable to the business—DAAS elements that need to be protected to ensure normal business operations
Why is defining the protect surface important?
enables to focus on defending what really matters to the business instead of trying to identify and protect the entire attack surface or focusing on just the perimeter
Why is the protect surface easier to protect than the perimeter?
it is much smaller than the perimeter
What does mapping the protect surface transaction flows entail?
mapping the transaction flows or interactions between critical DAAS elements and users to understand their interdependencies - who has business reasons to access each element, in what manner, and at what time
Why is mapping the protect surface transaction flows important?
helps to understand how to create a Security policy that allows only authorized users access to specific data and assets using the specified applications - helps to enforce the principle of least privilege
What are the ways to map the transaction flows? (9)
- leverage existing flow diagrams if available
- work with application, network, and enterprise architects, as well as business representatives, to understand the purpose of applications and the transaction flow they envision
- insert one or more FWs transparently into network in virtual wire mode to gain visibility into traffic
- use third-party tools from Palo Alto Networks integrated partners
- use log information from the Cortex Data Lake to gain visibility into, and map, transaction flows
- map the flow of application data across the network, the computing objects required for each application, and who uses each application
- find out who uses the data, where you collect, store, use, and transfer the data, and how the data is stored, encrypted, archived, or destroyed after use
- for each asset, find out its location, who uses it, when they use it, and where the asset fits into workflows
- map the service workflows across the environment