Cyber Monday 2024! 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 31 Discussion

Actual exam question for Netskope's NSK200 exam
Question #: 31
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 Ryan at Oct 19, 2024, 10:20 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Flo
12 days ago
Ha! This is a classic case of 'the DLP is only as good as the setup'. B and D all the way. Gotta love it when developers try to outsmart the security team. Good luck with that!
upvoted 0 times
...
Tamera
14 days ago
B and D, no doubt. If the DLP rule is set too high or there's no API integration, you're not going to catch anything. Might as well just send your credit card info straight to the hackers!
upvoted 0 times
...
Evelynn
15 days ago
Ah, the old 'invalid test data' trick, huh? Classic. But I'm going with B and D - gotta have that API protection and a low enough threshold to catch those sneaky credit card numbers.
upvoted 0 times
...
Chantay
19 days ago
Definitely B and D. Without API protection, the DLP solution can't inspect the Dropbox traffic, and the threshold needs to be sensitive enough to catch the test data. Silly developers, always trying to cheat the system!
upvoted 0 times
Leonardo
3 days ago
B) The DLP rule has the severity threshold set to a value higher than the number of occurrences.
upvoted 0 times
...
...
Eloisa
1 months ago
I think the correct answers are B and D. The DLP rule severity threshold needs to be set low enough to catch the test data, and Dropbox needs API protection configured for the DLP solution to work properly.
upvoted 0 times
Devora
7 days ago
B) The DLP rule has the severity threshold set to a value higher than the number of occurrences.
upvoted 0 times
...
Olen
8 days ago
A) The Netskope client Is not steering Dropbox traffic.
upvoted 0 times
...
...
Hoa
2 months ago
I agree with Viola, but I also think option D could be a factor.
upvoted 0 times
...
Viola
2 months ago
I think option A is causing the issue.
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