A new catalog crawler is configured with production database passwords stored in its admin UI and broad access to export connection secrets. What protection principle should stop that design?
Select an answer to reveal the explanation.
Short Explanation
A catalog that hoards production passwords is a skeleton key hung on a lobby hook. Harden the metadata platform—use vaulted secrets, least privilege, and no casual credential export. Convenience that creates a new vault of keys is not progress.
Full Explanation
Metadata platforms must be secured so catalogs do not become repositories of production credentials or sensitive sprawl. Connection secrets should use vault patterns, least privilege, and controlled administration—not plaintext UI storage with broad export. Public password pages and disabled authentication amplify risk. Protection of the metadata estate is part of Domain 4 practice, not an afterthought.