Question 520
A Script Include callable from the client returns confidential HR data because it trusts an arbitrary sys_id parameter. Before changing the configuration, which evidence should the administrator examine FIRST?
Explanation
Correct Answer
Inspect client script invocation, callable Script Include scope, input parameter validation, authenticated user, ACLs, and returned payload shape. Client scripts cannot call every server API directly; supported server endpoints must validate untrusted request parameters independently. The appropriate response is: Use supported asynchronous client-to-server calls such as GlideAjax and scoped Script Includes for required server data, validating inputs and authorization without relying on synchronous browser-side database access. Scenario: A Script Include callable from the client returns confidential HR data because it trusts an arbitrary sys_id parameter.
Incorrect Answers
Inspect entry paths (form, API, import), condition semantics, data policy/ACL coverage, and records written without the browser UI. This evidence is relevant to UI Policy versus server-side data enforcement, not the most diagnostic first check for this failure. Examine: Inspect client script invocation, callable Script Include scope, input parameter validation, authenticated user, ACLs, and returned payload shape. Scenario: A Script Include callable from the client returns confidential HR data because it trusts an arbitrary sys_id parameter.
Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. This evidence is relevant to Business Rule recursion and idempotent side effects, not the most diagnostic first check for this failure. Examine: Inspect client script invocation, callable Script Include scope, input parameter validation, authenticated user, ACLs, and returned payload shape. Scenario: A Script Include callable from the client returns confidential HR data because it trusts an arbitrary sys_id parameter.
Inspect property name/value/type, owning application, upgrade/clone behavior, dependent code, cache effects, and audit history. This evidence is relevant to Instance properties and scoped configuration control, not the most diagnostic first check for this failure. Examine: Inspect client script invocation, callable Script Include scope, input parameter validation, authenticated user, ACLs, and returned payload shape. Scenario: A Script Include callable from the client returns confidential HR data because it trusts an arbitrary sys_id parameter.


