A transit client requests raw password lists be sent over ordinary email. How should the tester handle sensitive evidence delivery?
Select an answer to reveal the explanation.
Short Explanation
Passwords in cleartext email are like mailing house keys on a postcard. Use the secure channel you agreed on, and redact when the full secret is not required.
Full Explanation
When a transit client requests raw password lists over ordinary email, the tester must use approved secure transfer channels and redact where feasible. Ordinary email is an inappropriate control plane for credential evidence in civic engagements.
Emailing full plaintext lists immediately for convenience is unsafe. Posting lists to a public ticket portal without access control is worse. Refusing to share any credentials even via authorized secure channels can block necessary rotation—secure delivery to authorized recipients is the balanced duty.
Exam caveat: prefer hashed/partial indicators when full secrets are unnecessary for remediation.
Operational check: agree on SFTP, encrypted portal, or equivalent; deliver minimized secrets to named transit custodians; confirm receipt and rotation; avoid emailing password corpora. In municipal operations, record the rationale in the engagement notes so future assessors know which control was chosen and which failure modes the rejected options would create for city services. Re-validate after the next maintenance window that the same finding class still applies under the estate's current patch and configuration baseline. In municipal operations, record the rationale in the engagement notes so future assessors know which control was chosen and which failure modes the rejected options would create for city services.