A comprehensive security approach uses:
- User-ID for identity-based policies
- App-ID for application-based security
- Decryption to inspect encrypted traffic
- Security profiles to enforce protections
- Dynamic updates to ensure up-to-date threat coverage
For comprehensive security, combine User-ID, App-ID, decryption, and security profiles. Keep the firewall updated with dynamic content updates to maintain the strongest security posture.
This ensures real-time, identity-aware, and application-centric security enforcement.

To minimize disruptions, it is recommended to perform Prisma Access upgrades during non- business hours and in a phased manner, starting with less critical sites to validate the process before moving to critical locations. Backup configurations and validate the system's readiness to avoid data loss and maintain service continuity.

When using AWS centralized deployments for Cloud NGFW, the service deploys NGFW instances into selected VPCs as additional workloads to secure that traffic.
In centralized deployments, Cloud NGFW instances are deployed as security appliances within the selected VPCs, ensuring consistent traffic inspection and protection.
This approach minimizes complexity and ensures direct security policy enforcement within AWS.

Content-ID is the core of Palo Alto Networks' prevention architecture, providing single-pass application layer inspection to deliver real-time threat prevention across all traffic.
Content-ID uses a single-pass architecture to perform application-layer (Layer 7) traffic inspection and real-time threat prevention. Unlike traditional firewalls that rely on multiple scans, Content-ID inspects traffic once to enforce multiple security controls simultaneously.
By consolidating security functions in a single pass, it ensures both efficiency and comprehensive security.

Blocking non-compliant SSH versions and failing certificate validations are fundamental security measures:
Block sessions when certificate validation fails
The SSH Proxy profile should block sessions that fail certificate validation to ensure that only trusted hosts are allowed.
Block connections using non-compliant SSH versions
Older SSH versions may have vulnerabilities or lack modern encryption algorithms.
To enforce stronger security, block SSH sessions that use older or deprecated versions of the SSH protocol that do not comply with your security posture.