The Netskope predefined identifier "Card Numbers (Major Networks; all)" is designed to minimize false positives by incorporating validation checks. It uses the Luhn algorithm (mod 10 checksum) to verify that a detected number is a mathematically valid credit card number. If the data used for testing contains number sequences that resemble credit card numbers but do not pass this algorithm, the DLP engine will not classify them as a match. Therefore, for a policy hit to be observed, the test data must contain credit card numbers that are valid in their structure and pass the checksum.

A. DLP policies can be applied to real-time traffic from various steering methods (e.g., Netskope Client, tunnels), not exclusively through API protection for data-at-rest.
C. The Netskope DLP engine can detect card numbers in various formats, including those with spaces or dashes, and does not require manual data normalization.
D. The Netskope Client is one of several methods for DLP inspection; it is not a mandatory requirement. Optical character recognition (OCR) is irrelevant for detecting card numbers in text.

1. Netskope Official Documentation, "Predefined Data Identifiers": This document details the predefined identifiers available in Netskope DLP. For sensitive identifiers like Credit Card Numbers, it specifies that validation, such as the Luhn algorithm, is used to increase detection accuracy. (Accessed via Netskope Support Portal, specific document ID varies with version, but the content is standard in the DLP section).

2. Netskope Official Documentation, "About Data Loss Prevention": This documentation explains that Netskope DLP inspects content from multiple traffic sources, including the Netskope Client for managed devices, secure web gateway for unmanaged devices, and API connectors for SaaS applications. This confirms that neither the client nor API protection is the sole method for DLP. (Found under the "Data Loss Prevention" section in the main product documentation).