A developer wants to custom-script every control test on day one of a county IRM rollout. What approach should the implementer prefer first?
Select an answer to reveal the explanation.
Short Explanation
Day one is for flipping the built-in switches—attestations, indicators, item generation—not for a custom-code carnival. Scripting every test up front is like welding a new engine when the car already starts. Use configuration first; code only when the product truly cannot express the need.
Full Explanation
CIS-RC implementation emphasizes configuration of IRM capabilities—attestations, indicators, and generated control/risk items—before broad custom development. CAD-style scripting is not the core of Risk and Compliance implementation and should address residual gaps after out-of-box patterns are exhausted. Starting with custom Script Includes for every test increases cost and bypasses the product’s designed operating model.