How should IAM and AppSec teams work together on OWASP Top 10 findings?

Why This Matters for Security Teams

When OWASP Top 10 findings touch both application code and access pathways, the failure is rarely just a vulnerable control in isolation. AppSec can show where a secret is exposed, where a workflow accepts unsafe input, or where a component inherits more reach than it should. IAM has to answer the harder question: who or what can actually use that exposure, and whether the access is stale, excessive, or borrowed from a third party. That joint view is what turns a finding into a real risk decision, especially when the issue sits across build pipelines, runtime services, and cloud permissions. Current guidance suggests treating secrets and entitlement sprawl as one problem, not two. The The State of Secrets in AppSec research is especially relevant here because it shows how fragmented secrets handling and delayed remediation undermine confidence. The OWASP view of this problem is also evolving through the OWASP Non-Human Identity Top 10. In practice, many security teams discover the access path only after the finding has already been exploited or inherited by another team’s control gap.

How It Works in Practice

The most effective operating model is a shared triage workflow. AppSec starts by classifying the finding: exposed secret, hardcoded credential, broken authorization, over-permissive service account, or supply-chain inherited access. IAM then validates the identity side of the same issue by checking effective permissions, ownership, lifecycle state, and whether the access is still needed. That means looking beyond the policy document to actual runtime entitlements, token scopes, and whether the principal is human, service, workload, or third party. A practical handoff usually includes:

• the exact asset or repository path where the issue was found;
• the identity or workload that can exploit it;
• the current permission set and inheritance chain;
• the expected owner for rotation, revocation, or re-approval;
• the TTL or rotation path for any secret, key, or token involved.

For NHI-heavy environments, this should map to the controls described in the OWASP NHI Top 10 and align with the operational guidance in Top 10 NHI Issues. The external standards lens matters too: the OWASP Non-Human Identity Top 10 and related AppSec guidance help define where the code boundary ends, while IAM confirms whether the entitlement boundary was ever enforced. Where possible, teams should also use workload ownership records, secret inventory, and event logs to verify whether a finding is active or merely historical. These controls tend to break down in multi-cloud environments with inherited service accounts and unmanaged third-party integrations because effective access is spread across systems that no single team fully controls.

Common Variations and Edge Cases

Tighter joint review often increases remediation overhead, requiring organisations to balance faster fix times against the cost of deeper access validation. That tradeoff becomes visible when the finding is not a clean “fix the code” issue. A leaked secret may be invalidated quickly, but a long-lived token embedded in a CI/CD pipeline can require coordinated changes across developers, platform engineers, and IAM owners. Best practice is evolving here, and there is no universal standard for how much evidence is enough before revocation, especially when production dependencies are unclear. A few edge cases matter:

• Third-party and contractor access may be technically valid but operationally unmanaged.
• Shared service principals often hide the true blast radius of an OWASP finding.
• Ephemeral workloads can appear low risk while still holding privileged runtime scopes.
• Automated fixes can fail if IAM is not consulted before secret rotation or role removal.

Security teams should treat the finding as unresolved until both the application flaw and the access reality are reconciled. That approach fits the broader Ultimate Guide to NHIs — Key Research and Survey Results and the external framing in OWASP Agentic AI Top 10, where runtime behaviour can widen the impact of a small access mistake. The hardest cases are legacy systems with opaque ownership and no reliable record of who can still assume the credential.

Related resources from NHI Mgmt Group

• How can IAM and compliance teams work together on Salesforce governance?
• How do IAM and network security teams work together on privileged access?
• Why do SaaS management and IAM teams need to work together?
• How do IAM and fraud teams work better together on identity proofing?