Identity Science
Maya N. has a diverse work experience in the technology industry. Maya is currently working as the VP of Technical Services at Identity Science, a company that focuses on managing and prioritizing risks introduced by developers. Prior to this, Maya was a Principal PM Manager at Microsoft, where they worked until October of 2022. Maya also has experience at CloudKnox Security, where they were a founding team member and Head of Customer Success, Partner Success, and Customer Support. Before that, Maya worked at Oracle as a Senior Staff Engineer, where they were involved in designing and developing SAML 2.0 microservices. Maya has also worked as a Sr Software Engineer at Covigna Inc and as a Software Engineer at Peregrine Systems. Additionally, Maya worked as a consultant at Visa Inc and Goldman Sachs, where they held the role of Sr Systems Analyst. Overall, Maya has a strong background in technical roles and has held positions at various companies in the technology industry.
Maya N. completed their high school education at St Thomas Residential School from 1990 to 1992. Following this, they attended the Indian Institute of Technology, Bombay from 1992 to 1996, where they pursued a degree in Civil Engineering.
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