Secrets management: where should passwords live?

FintechBy: Mahdi Mansour Samaei2 min readSource: OWASP
Secrets management: where should passwords live?

1Introduction

Hard-coded secrets in code or config are a top cause of leaks.

2Discussion

Separate secrets via environment variables and add pre-commit secret scanning.

Use a vault (HashiCorp Vault, cloud KMS) with encryption, role-based access and audit logs.

Rotate secrets regularly, ideally automatically, or use short-lived credentials.

3Conclusion

If a secret leaks, revoke and replace it — history keeps the old one.

Share:TelegramWhatsAppLinkedIn

Sources

  1. OWASP ↗
  2. NIST ↗
همفکران فناوری شریفThis article summarises the official sources cited, prepared by the Hamfekran Fanavari Sharif team for finance leaders.
Want to see these solutions in your organisation?Book a free demo

Related articles

FintechThreat hunting: finding attackers who triggered no alertHunting assumes compromise and actively searches for evidence instead of waiting for alerts.FintechAutomated bank reconciliation: ending manual finance workMatching bank statements to books is one of finance’s most time-consuming tasks — and ideal for automation.FintechDigital strategy for executives: where to startDigital transformation starts with a clear business question, not a software purchase.FintechObservability: beyond simple monitoring in modern systemsIn distributed systems you must know why and where an error happens, not just that it did.