Identity Science
Guruprasad Ramprakash has a diverse work experience in the technology industry. Guruprasad is currently working at Identity Science as a Senior Product and UI Manager since May 2023. Prior to that, they worked at Microsoft from August 2021 to May 2023, starting as a Software Engineer and later transitioning to the roles of Product Manager and Senior Product Manager. At Microsoft, they played a crucial role in integrating CIEM software into the Microsoft environment and provided demos and support to employees. Before Microsoft, Guruprasad worked at CloudKnox Security Inc as a Lead Software Engineer from May 2019 to August 2021, where they were responsible for architecting and developing user-facing features for their SAAS offering. Guruprasad'searlier experience includes working at Carma Networks, Inc as a Software Engineer from August 2015 to February 2019, focusing on V2X integration and frontend applications. Guruprasad also worked as a Software Engineer Intern at ANPI from August 2014 to March 2015, where they developed web applications using Ruby-On-Rails and Javascript.
Guruprasad Ramprakash completed their education at the College of Engineering, Guindy from 2010 to 2014. During this time, they pursued a Bachelor of Engineering (B.E.) degree in Electronics and Communication Engineering. In August 2020, Guruprasad obtained a certification called "Master the OWASP Top 10" from LinkedIn.
This person is not in any teams
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