Question 420
A core network change board wants to avoid: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs. Which ongoing safeguard fits best?
Explanation
Correct Answer
Run secret-scanning checks against network automation and management proxy logs. This helps prevent recurrence of the issue: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs. Acceptance evidence should be: A controlled request succeeds with credentials absent from URLs and audit logs.
Incorrect Answers
Test AAA failure behavior and accounting completeness at scheduled intervals. That is a sensible control for ANOTHER scenario: TACACS+ accounting records disappear after a redundant server failover and the team continues privileged changes with no traceable command logs. It is less targeted to this issue than: Run secret-scanning checks against network automation and management proxy logs.
Inventory exposed management listeners after each platform upgrade. That is a sensible control for ANOTHER scenario: A provider's router management API is reachable from the public internet using a broad admin token, even though the operations team uses a dedicated management VRF. It is less targeted to this issue than: Run secret-scanning checks against network automation and management proxy logs.
Require postboot image attestation and rollback readiness in change acceptance. That is a sensible control for ANOTHER scenario: After an IOS XE image update, the route processor boots but a router retains an old package set because the team updated the boot variable without verifying install mode. It is less targeted to this issue than: Run secret-scanning checks against network automation and management proxy logs.