Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

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

Isaca Exam CRISC Topic 5 Question 89 Discussion

Actual exam question for Isaca's CRISC exam
Question #: 89
Topic #: 5
[All CRISC Questions]

Which of the following would MOST effectively reduce the potential for inappropriate exposure of vulnerabilities documented in an organization's risk register?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Madalyn at Oct 24, 2024, 06:21 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Margurite
30 days ago
I'm going with option C. Gotta love that role-based access - it's like a VIP pass for the vulnerability club.
upvoted 0 times
...
Shaun
1 months ago
Encrypting the risk register? Sounds like a job for the Enigma machine!
upvoted 0 times
...
Tatum
1 months ago
Option A is like putting a lock on the barn door after the horse has already bolted. Limiting access to senior management won't do much if the register is already compromised.
upvoted 0 times
...
Malcolm
1 months ago
Requiring users to sign a confidentiality agreement (option D) is a good idea, but it doesn't actually prevent the information from being exposed. It just provides a legal recourse after the fact.
upvoted 0 times
Kate
4 days ago
Regularly updating and reviewing the risk register (option B) can help identify and address vulnerabilities in a timely manner.
upvoted 0 times
...
Tracey
15 days ago
Implementing access controls (option A) would limit who can view the risk register.
upvoted 0 times
...
Shawnda
16 days ago
Regularly reviewing and updating the risk register (option B) can help identify and address vulnerabilities.
upvoted 0 times
...
Tasia
17 days ago
Implementing access controls (option A) would limit who can view the risk register.
upvoted 0 times
...
...
Marisha
2 months ago
I'd go with option C. Implementing role-based access ensures that only those who need to see the risk register can access it. That's a more comprehensive solution than just limiting it to senior management.
upvoted 0 times
Frankie
25 days ago
Definitely, it's important to have a system in place that controls who can view the risk register to prevent any inappropriate exposure.
upvoted 0 times
...
Alton
26 days ago
I agree, limiting access to only those who need it is crucial for protecting the organization's vulnerabilities.
upvoted 0 times
...
Gail
1 months ago
Option C sounds like a good choice. Role-based access is key to keeping sensitive information secure.
upvoted 0 times
...
...
Irving
2 months ago
Hmm, option B seems like the most straightforward way to protect sensitive information. Encrypting the risk register would keep it secure, even if someone gained unauthorized access.
upvoted 0 times
Malcolm
19 days ago
It's important to take all necessary precautions to keep our organization's information secure.
upvoted 0 times
...
Tamie
24 days ago
Encrypting the risk register would definitely reduce the potential for inappropriate exposure of vulnerabilities.
upvoted 0 times
...
Brent
1 months ago
I agree, encryption is key in protecting sensitive information from unauthorized access.
upvoted 0 times
...
Rosina
1 months ago
Option B is definitely the way to go. Encrypting the risk register is a must.
upvoted 0 times
...
...
Bobbie
2 months ago
I think encrypting the risk register could also be effective in reducing inappropriate exposure of vulnerabilities.
upvoted 0 times
...
Ona
3 months ago
I agree with Nenita. Role-based access ensures that only authorized individuals can view the risk register.
upvoted 0 times
...
Nenita
3 months ago
I think implementing role-based access would be the best option.
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