How to: netskope classic forensics destination matrix

Use this local guide before 2026-10-31. Re-check official vendor documentation for authoritative dates. This site does not call vendor APIs or store tokens.

1. Step 1. Confirm Classic Forensic Storage ceases Oct 31 2026 on Netskope EOL announcements
2. Step 2. Inventory tenants still pointing DLP forensics at classic destinations
3. Step 3. Create a Next Gen forensic profile for S3, Box, Google Drive, Azure Blob, or SharePoint
4. Step 4. Enable Next Gen forensics with minimum permission scopes (decoupled from classic API DP)
5. Step 5. Remember one forensic destination per tenant — plan the cutover as all-or-nothing
6. Step 6. Keep classic instances until incident retention (~90 days) so old evidence stays downloadable
7. Step 7. Do not delete classic forensic instances early or historical evidence becomes unreadable
8. Step 8. Export matrix pack with EOL + Next Gen Forensics URLs into the security change ticket

Related: FAQ · Use cases · Home tool. Always prefer official vendor documentation for authoritative dates. Export your Markdown pack into the change ticket with the official URLs listed on the home page.

Context for operators: Netskope Classic Forensic Storage Destinations cease Oct31 2026; migrate to Next Gen profiles (DLP forensics domain). The gap this wedge fills: EOL 公告列目的地；缺 Classic→Next Gen 可编辑对照矩阵+90 天保留勾选。不做 Netskope 控制台 SaaS。 Keep owners assigned on every residue row so nothing silently slips past the deadline. When in doubt, re-open the official source pages rather than trusting a cached screenshot.