Question 630
At Cobalt Mobility, an API platform team is improving partner integration after a knowledge-policy revision (SF-P06-02). The administrator observes that business users have broad template modification rights merely to generate existing sales drafts. Any fix must ensure that partner authentication and least privilege are maintained. Which continuing control best prevents this issue from recurring?
Explanation
Correct Answer
The preventive control directly addresses repeat failures: Review prompt asset permissions during quarterly access certification; require the check in the next release review at Cobalt Mobility (SF-P06-02). It complements the corrective action, separate template builders from template consumers and reduce grants to the required use capability, and protects the explicit condition that partner authentication and least privilege are maintained.
Incorrect Answers
This safeguard, “Test both template invocation and source-record authorization after role changes; review it as part of periodic access and quality reviews”, reduces a different source-defined risk: A service representative can see a generated-content feature but the template run is denied. The correction must ensure that escalations preserve only the needed guest context. That risk depends on: Template access alone does not erase record and field permission boundaries. The recurring problem here is business users have broad template modification rights merely to generate existing sales drafts. The correction must ensure that partner authentication and least privilege are maintained. The originally selected control “Review prompt asset permissions during quarterly access certification; review it and confirm the control remains effective after release” is more specific because least privilege applies independently to template creation, activation, and execution.
This safeguard, “Audit template management grants and remove unnecessary author privileges; review it and retest after dependent metadata changes”, reduces a different source-defined risk: An analyst needs to build new production prompt templates but has only permission to use existing ones. The correction must ensure that guest profile fields are used only with permitted access. That risk depends on: Creating templates and using templates are distinct authorization responsibilities. The recurring problem here is business users have broad template modification rights merely to generate existing sales drafts. The correction must ensure that partner authentication and least privilege are maintained. The originally selected control “Review prompt asset permissions during quarterly access certification; review it and confirm the control remains effective after release” is more specific because least privilege applies independently to template creation, activation, and execution.
This safeguard, “Add negative tests with absent source fields; review it with audit evidence from regression testing”, reduces a different source-defined risk: A generative service reply fills missing delivery dates with invented estimates. The correction must ensure that financial identifiers are masked outside authorized roles. That risk depends on: Prompts need explicit abstention behavior when grounding does not supply an answer. The recurring problem here is business users have broad template modification rights merely to generate existing sales drafts. The correction must ensure that partner authentication and least privilege are maintained. The originally selected control “Review prompt asset permissions during quarterly access certification; review it and confirm the control remains effective after release” is more specific because least privilege applies independently to template creation, activation, and execution.