Best practice for OOTB Security Incident Calculator Groups?

Joel Pomales1
Tera Contributor

Team,

 

What's the best practice to handle the out of the box Security Incident Calculators Groups? The group can't be toggled inactive, but the calculators within can. What if a customer wants to customize them? Disable the calculators so they don't run?

 

Looking for a perspective here, since I see some scripts and script includes running and maybe a customer would like to customize them. Maybe simplify them?

1 ACCEPTED SOLUTION

Nikan Keyhani
Mega Guru

Hey Joel, 

 

I typically deactivate the OOTB calculators and create a new calculator group, to match the exact needs, rather than configuring the OOTB calculators. 

 

If we are talking about making changes to a script include, I would recommend setting the OOTB one to inactive, creating a duplicate and working on the duplicate.

View solution in original post

2 REPLIES 2

Nikan Keyhani
Mega Guru

Hey Joel, 

 

I typically deactivate the OOTB calculators and create a new calculator group, to match the exact needs, rather than configuring the OOTB calculators. 

 

If we are talking about making changes to a script include, I would recommend setting the OOTB one to inactive, creating a duplicate and working on the duplicate.

Joel Pomales1
Tera Contributor

I thought as much. Makes sense to build something around what you fully understand.