Identity Science
Eric Mowry currently serves as the Chief Information Security Officer and Vice President of Platform Engineering at BlueFlag Security since August 2022. Prior to this role, Mowry was the Senior Director at Data Intensity from January 2022 to August 2022. Mowry's extensive experience includes a long tenure at Secure-24 from September 2007 to July 2021, where Mowry held several leadership positions, including Vice President of Engineering and Director of Technology, focusing on building cross-functional engineering teams and enhancing operational processes. Earlier in Mowry's career, Mowry worked as a Senior Systems Administrator at FMF Capital LLC from February 2005 to May 2007.
This person is not in any teams
This person is not in any offices
Identity Science
Identity Science is an identity-based SDLC security company. Product Agentless security platform to manage developer security posture, entitlements, risky behaviors, and open-source software risk from code-to-deployment Customer Value With the Identity Science platform, security teams can manage a Zero Trust SDLC process via integrated visibility, monitoring, and automated remediation capabilities. The platform provides organizations consolidated executive level and detailed dashboards to manage and prioritize their SDLC risks in real time. Why is this important? 1) The SDLC process is an identity centric process which is highly complex and has significant inherent risk through disjointed software development processes and tools 2) Security teams are grappling with the lack of visibility, inability to monitor and control risks in these highly dynamic developer environments. Examples of challenges: a. Overprivileged Developer Entitlements: Developers, service accounts typically have admin permissions across tools and broad scope access across assets b. Weak Security Posture: Misconfigurations across SDLC tools and services. c. Risky Developer Behavior: Anomalous activity due to external or malicious insider users leading to security breaches like stolen source code, critical vulnerabilities in software assets d. Secrets/Tokens Leakage Detection: Undetected password and secret credentials leaks through code & software release pipelines e. Open-Source Supply Chain Risk: Critical Vulnerabilities through risky external packages f. Lack of Continuous Compliance: Security best practices, guardrails and standards to ensure the SDLC process is Secure by Design (Federal Cybersecurity Strategy mandate - April 23, 2023) g. Integrated SDLC Risk Visibility and Remediation Framework: Lack of consolidated risk dashboard, alert fatigue from multiple disconnected security tools unaware of organizational context and lack of prioritized remediation