security-review-expert

Conduct a security review by applying threat modeling, data flow analysis, and trust boundary checks to backend code and manifests to identify attack surfaces and produce a documented risk report.

Perform threat modeling and trust boundary analysis when auditing newly added features, refactors, deployment architectures, or post-incident reviews to identify tenant isolation gaps and security violations.

Yes, you can check secret management and runtime hardening configurations by reviewing patterns for secret exposures, container hardening gaps, and least-privilege practices across your system architecture.

The best way to map attack surfaces and identify tenant isolation gaps is to analyze data flows, authentication boundaries, and deployment manifests to detect trust boundary violations and unauthorized access paths.

Yes, this approach works for post-incident reviews and architecture decisions by enforcing concrete security checks like supply chain controls, logging review, and compliance validation against least-privilege requirements.

Newly deployed features have secret exposure and authorization vulnerabilities when security reviews miss data flow analysis, trust boundary validation, and secret management checks during the post-implementation audit phase.