PTIR — Daily Briefing — November 10, 2026
by
Executive Summary
ISC2 is hosting a free, 30-minute webinar today on a practical identity-security gap: credentials entered in browsers outside single sign-on and beyond the visibility of conventional identity, endpoint, and email controls. The session begins at noon Central and offers 0.5 Group A CPE. It is sponsored by Dashlane, so its product framing should be evaluated critically, but the underlying question—what security teams can observe at the point where a credential is used—is useful for both workforce security and classroom discussion.
Action Queue
Register for ISC2’s browser-credential briefing before noon Central
The Browser Security Blind Spot: Why Credentials Continue to Cause Breaches is a live ISC2 webinar featuring Kevin Bardos, Dashlane’s vice president of product management. The stated agenda covers weak or compromised credentials on work devices, logins that occur outside SSO, and real-time detection at the point of login.
Recommended action: register before the session begins, attend the 30-minute briefing, and capture three notes: which browser events are observable, which control owns the response, and which claims are supported independently rather than only by vendor data. Use those notes to update a credential-security checklist or a short classroom example contrasting identity-provider, endpoint, email, and browser visibility.
Urgency: Immediate
Importance: ★★★★☆
Verified active: November 10, 2026
Deadline: November 10, 2026, noon Central (1:00 p.m. Eastern)
Cost: Free registration; no regular price. The session offers 0.5 Group A CPE
Requirements: Online registration; browser and audio access; an ISC2 or BrightTALK account may be requested for registration or CPE tracking. No ISC2 certification is required to watch
Official registration: ISC2 Security Briefings on BrightTALK
Teaching Corner
A compact follow-up discussion can ask students to map four controls—IdP/SSO, EDR, email security, and browser-level protection—to the credential attacks each can and cannot see. The key lesson is not that one product closes every gap, but that visibility depends on where authentication is initiated, where secrets are entered, and which telemetry is actually collected. This is a short discussion prompt rather than a standalone lab.
PKb Candidates
- Credential-use visibility map: authentication path, control owner, available telemetry, response action, retention period, and privacy boundary.
- Vendor-webinar evidence filter: separate independently supported risk claims, vendor telemetry, product capabilities, and unanswered implementation questions.