Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location PL
Mob_nav_barsMENU

Netskope Exam NSK200 Topic 1 Question 7 Discussion

Actual exam question for Netskope's NSK200 exam
Question #: 7
Topic #: 1
[All NSK200 Questions]

You are using the Netskope DLP solution. You notice flies containing test data for credit cards are not triggering DLP events when uploaded to Dropbox. There are corresponding page events. Which two scenarios would cause this behavior? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: B, C

There are two possible scenarios that would cause the behavior of files containing test data for credit cards not triggering DLP events when uploaded to Dropbox. One scenario is that the DLP rule has the severity threshold set to a value higher than the number of occurrences. This means that the rule will only trigger an event if the number of matches for the sensitive data exceeds the specified threshold. For example, if the rule has a severity threshold of 10 and the file contains only 5 credit card numbers, then no event will be generated. To fix this, you can lower the severity threshold or remove it altogether. The other scenario is that the credit card numbers in your test data are invalid 16-digit numbers. This means that the numbers do not pass the Luhn algorithm check, which is a validation method used by Netskope DLP to detect valid credit card numbers. For example, if the number is 1234-5678-9012-3456, then it is not a valid credit card number and will not be detected by Netskope DLP. To fix this, you can use valid test credit card numbers that pass the Luhn algorithm check. The other options are not valid scenarios for this behavior. The Netskope client is not steering Dropbox traffic is not a valid scenario because there are corresponding page events, which means that the traffic is being steered to Netskope.There is no API protection configured for Dropbox is not a valid scenario because API protection is not required for DLP detection on file uploads, which are handled by real-time protection.Reference:DLP Rule Settings1,Credit Card Number Detection2


by Virgina at Dec 13, 2023, 08:15 PM

Limited Time Offer

25%

Off

Get Premium NSK200 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Kaitlyn
24 days ago
Hmm, the client not steering Dropbox traffic also seems like a possible explanation. Maybe the Netskope client is just not configured to handle Dropbox properly.
upvoted 0 times
...
Colette
25 days ago
I'm not sure about the credit card numbers, but the lack of API protection for Dropbox sounds like a likely culprit. Without that, the Netskope client might not be able to properly monitor the traffic.
upvoted 0 times
Tammara
11 days ago
D) There is no API protection configured for Dropbox.
upvoted 0 times
...
Krystal
12 days ago
B) The DLP rule has the severity threshold set to a value higher than the number of occurrences.
upvoted 0 times
...
...
Lorean
26 days ago
Yeah, the credit card numbers could be the problem. If they're not valid 16-digit numbers, the DLP solution won't be able to recognize them. And I agree, the severity threshold could also be an issue.
upvoted 0 times
...
Whitley
27 days ago
Hmm, this is an interesting one. I'm guessing the issue is with the DLP rule configuration. Maybe the severity threshold is set too high, or the credit card numbers are not being detected properly.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77