Episode
Course 32 - Checkpoint CCSA R80 | Episode 8: HTTPS Inspection, URL Filtering, and Identity Awareness
- Podcast
- CyberCode Academy
- Published
- May 8, 2026
- Duration seconds
- 1277
- Processing state
not_requested
Actions
POST https://stenobird.com/v1/public/podcasts/cybercode-academy-7578615/episodes/course-32-checkpoint-ccsa-r80-episode-8-https-inspection-url-filtering-and-identity-awareness/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/cybercode-academy-7578615/course-32-checkpoint-ccsa-r80-episode-8-https-inspection-url-filtering-and-identity-awareness.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
In this lesson, you’ll learn about: HTTPS inspection, advanced filtering, and identity-based security in Check Point R801. HTTPS Inspection (Deep Traffic Visibility) In Check Point R80, HTTPS traffic is encrypted → normally invisible to firewalls 🔹 The Problem Malware or attacks can hide inside: SSL/TLS encrypted traffic 🔹 The Solution: HTTPS Inspection Gateway acts as a proxy: Intercepts HTTPS traffic Decrypts it in memory Inspects content Re-encrypts and forwards 🔹 Key Requirements Enable inspection policy Install and trust certificates on client devices 🔹 Verification Use SmartConsole logs Confirm sessions are being inspected 👉 This is critical for detecting: Hidden malware Encrypted attacks 2. Advanced Filtering Actions🔹 Category-Based Filtering Control access based on: Website categories Application types 🔹 Examples Allow: Search engines Restrict: Social media Gambling Malicious sites 3. Interactive Policy Actions🔹 “Ask” Action User sees a warning page Must accept policy to continue 🔹 “Inform” Action User is notified Traffic still allowed 🔹 Why Use Them Enforce company policy Educate users Avoid full blocking 👉 Balance between security and usability4. Identity Awareness (User-Based Security)🔹 The Problem Traditional firewalls rely on: IP addresses ❌ But IP ≠ real user🔹 The Solution Identity-based enforcement in Check Point R80 🔹 Identity Sources Active Directory Captive Portal Endpoint agents 🔹 Access Role Objects Combine: Users Groups Machines Networks 🔹 Example Rule Allow: User “Bob” → access internal app Deny: Others 👉 Much more precise than IP-based rules5. Identity-Based Logging & Visibility🔹 Benefits Logs show: Username (not just IP) 🔹 Use Cases Faster troubleshooting Better auditing Stronger security investigations Key Takeaways HTTPS inspection enables…