+2Why is ControlMap showing out of scope requirements in assessment questions? This is causing confusion with clients and our assessors. Is there a way to get the system to correct this as this also shows up in assessment reporting? I have attached a sample screenshot to show you which requirements I specifically set to out of scope in the system and how they are still showing up here in the “Applies to” section. Only one of these requirements is truly in scope.
+1Thanks for the detailed feedback, to resolve this we would want the mappings to continue to exist but the out of scope controls or objectives to possibly greyed out. Reporting and scoring should already be updated to show out of scope controls / objectives but will double check this.
+2The greying out of out of scope would be helpful.
The Common Assessment report is one that comes to mind that still shows the out-of-scope requirements in the “Applies to” column. We would not want those shown.
+1That helps! The common assessment is the XLS report, I’ll see if we can make a column for out of scope and make it optional. We already configured the word doc “Assessment Report” to account for this which is what I was thinking off.
+2...this would also exist in any “export” off the assessments screen in a given tenant. Thanks again!
+2Do I need to submit this as a feature or is this issue being worked on in some roadmap? We are finding this to be labor intensive with trying to guess which requirements are in scope or not when looking at assessment question or any reports that include framework requirements as an export field.
Already have a ScalePad Community account? Sign in
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
