Question 540
A browser OAuth app ignores CSRF state and accepts a callback from an unrelated authorization request. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Protect OAuth state, PKCE where appropriate, sensitive token storage and registered redirect validation. Verification: Test state mismatch, invalid verifier, exposed-token handling and safe support logs. Boundary: A trusted Salesforce endpoint does not make insecure client-side token or redirect practices safe” addresses the access-design responsibilities in a browser OAuth app ignores CSRF state and accepts a callback from an unrelated authorization request Test against test state mismatch, invalid verifier, exposed-token handling and safe support logs; a trusted Salesforce endpoint does not make insecure client-side token or redirect practices safe.
Incorrect Answers
“Action: Use a login flow for approved post-authentication business steps without replacing core authentication controls. Verification: Test state mismatch, invalid verifier, exposed-token handling and safe support logs. Boundary: Disabling future logins alone may not prove all previously issued sessions and grants are unusable” may apply to a related identity task, but it does not establish test state mismatch, invalid verifier, exposed-token handling and safe support logs for a browser OAuth app ignores CSRF state and accepts a callback from an unrelated authorization request The controlling boundary is: A trusted Salesforce endpoint does not make insecure client-side token or redirect practices safe.
“Action: Protect OAuth state, PKCE where appropriate, sensitive token storage and registered redirect validation. Verification: Rehearse IdP outage, alternative admin login, credential custody and post-use review. Boundary: Availability and retention of enhanced event data depend on current product entitlements and configuration” may apply to a related identity task, but it does not establish test state mismatch, invalid verifier, exposed-token handling and safe support logs for a browser OAuth app ignores CSRF state and accepts a callback from an unrelated authorization request The controlling boundary is: A trusted Salesforce endpoint does not make insecure client-side token or redirect practices safe.
“Action: Preserve Setup Audit Trail and relevant configuration-change evidence with approved retention. Verification: Validate login flow assignment, post-login screen, cancel behavior and emergency access paths. Boundary: A trusted Salesforce endpoint does not make insecure client-side token or redirect practices safe” may apply to a related identity task, but it does not establish test state mismatch, invalid verifier, exposed-token handling and safe support logs for a browser OAuth app ignores CSRF state and accepts a callback from an unrelated authorization request The controlling boundary is: A trusted Salesforce endpoint does not make insecure client-side token or redirect practices safe.