#321 Forward deployed engineer interviews 5.9 min
Support Bundle Without Secrets: Redact and Check It
The obvious redaction rule found nothing, and five secrets were still in the support bundle.
Break the IP address rule
Copy the code folder first. In bundle.py delete the line in RULES that matches IP addresses. Predict what the 'full rules' line and the line below it will say, then run python run.py to check.
A hint
Look at the 'full rules' line of the output. The check names the kind of secret, never its value.
Remove the rule for the app's password
Put the IP line back, then in bundle.py delete the line in RULES that has the comment about the app's password in a log message. The same password also sits inside the database address. Predict whether the check will report a leak. Run python run.py.
A hint
One rule can remove a secret from one place and leave it in another. I saw 1 leaked, a database password.
Add one more log line
Put the rule line back, then in machine.py add this line to LOG_LINES, after the retry line: '2026-03-04 10:01:50 INFO invoice sent to user@example.com'. Predict the first line of the output and how many lines are listed as changed. Run python run.py. Then explain why the check would not notice if this new address were missed by the rules.
A hint
The check compares only the PLANTED values. I saw 14 lines in the bundle and 8 changed lines.
These tasks are for you to try on your own machine. Nothing is checked or saved.
What this does not show
A made-up machine with five planted secrets; the rules were written for them and the check finds only planted secrets; a person must still review a real bundle.
Up next in Forward deployed engineer interviews
More in Forward deployed engineer interviews
- #302 Forward Deployed Engineer Interview: What Is Tested
- #303 The FDE Decomposition Round: Vague Ask to a Plan
- #304 Scope an AI Pilot: Metric, Baseline and Stop Rule
- #305 Retry a Flaky API Without Duplicates: Idempotency Keys
- #306 Webhooks Done Right: Signatures, Retries and Replays
- #307 Schema Drift: Map a Customer's Data and Catch Changes
Related videos
- #151 Regex for Data Cleaning: Extract IDs and Phones in Python Python for data
- #204 Tag PII Columns in Python, Including a False Positive Data governance
- #98 Audit Logs for AI Apps: Tamper-Evident Logging in Python AI security and governance
- #302 Forward Deployed Engineer Interview: What Is Tested Forward deployed engineer interviews
