A municipal NFS export is world-readable and contains SSH private keys. What connection should the report emphasize?
Select an answer to reveal the explanation.
Short Explanation
An open NFS share holding SSH keys is a lost keyring left on a park bench. Anyone who mounts it may walk into systems that trust those keys. Share permissions and secret storage fail together here—say so plainly.
Full Explanation
A municipal NFS export that is world-readable and contains SSH private keys should emphasize that over-permissive file-share exports can disclose secrets enabling further authenticated access. Framing NFS misconfiguration as only a disk-capacity issue misses the credential disclosure path entirely. Accepting world-readable exports because keys are passphrase-less for convenience doubles the mistake: missing passphrases make stolen keys immediately usable. Claiming SSH keys on shares are safer than passwords so export permissions can stay open confuses key-versus-password debates with share ACL failure; a readable private key is still a secret. Exam caveat: secret-bearing shares are high severity even when the share was intended for “internal convenience.” Operational check: document export path and permissions, prove key material readability under authorization without pasting full key bodies into the main report, recommend tightening exports, rotating affected keys, and moving secrets into a vaulted distribution method for city admins. In municipal operations, record the rationale in the engagement notes so future testers and city defenders understand which approach was chosen and which failure modes the rejected options would create for civic services.