Is Your GRC Team Technical Enough? (Probably Not...) ft. Jeevan Singh @ Rippling

Ever wondered if your GRC team should be writing code? (Spoiler alert: Jeevan thinks they probably should.) In this eye-opening episode of Security & GRC Decoded, Jeevan Singh, Director of Security Engineering at Rippling, joins Raj to challenge traditional views of Governance, Risk, and Compliance (GRC). Jeevan passionately argues why GRC teams must become more technical, automated, and deeply integrated into engineering processes to truly protect and enable businesses. Drawing from his experience at Segment and Rippling, he provides actionable insights and real-world examples to transform compliance from a bureaucratic burden into a proactive, engineering-driven function. Key Takeaways: ✅ Why having technical GRC teams leads to dramatically stronger security outcomes ✅ How automating compliance tasks can eliminate toil and boost productivity ✅ Practical steps to shift your compliance culture from reactive to proactive ✅ The real difference between CVSS and CWSS vulnerability scoring systems ✅ Strategies for fostering productive friction between GRC and engineering teams Take Action: Assess your own GRC team’s technical depth: Could automation improve your compliance posture? Discuss these insights with your security and engineering leaders Share this episode with your team and spark important conversations around GRC innovation 👉 Follow Security & GRC Decoded to stay ahead on the latest insights and trends in security, compliance, and risk management. 🎙️ Security & GRC Decoded is brought to you by ComplianceCow. Learn how ComplianceCow can elevate your GRC team today! 🚀 Enjoying The Show? Rate and review the podcast to support the show and let us know you're enjoying the content! 💬 Connect with Jeevan Singh:  💼 LinkedIn: https://www.linkedin.com/in/jeevansecurity/ 🌐 Company: https://www.rippling.com/