@chetan-maneGovIntel turns AWS reality into board governance. Chetan, Pune
Hi everyone, I'm Chetan Mane, founder of Rajdharma Technologies in Pune. We build GovIntel, a read-only AWS assessment that turns what's actually in an account into a dated, board-ready governance report. There are no agents, no questionnaire and no self-assessment. A customer deploys a CloudFormation template that creates a read-only role, and we return prioritised risks a board can act on. My background is in DevOps, most recently as a lead DevOps engineer and architect at Uniken, and earlier at Hewlett Packard Enterprise and IBM.
I'm building with Lovable, Claude Code, Supabase and Vercel, with Gemini and ChatGPT alongside. What I'm focused on now is turning technical cloud security findings into language executives can use.
What I'd love from this community: an intro to a CISO, board member or risk advisor who would be willing to look at a sample board pack and tell me honestly what they'd change.
Comments2
Welcome to Lounge, Chetan. The read-only CloudFormation role with no agents seems like a smart way to lower the trust barrier for a security buyer. When you translate findings like an open S3 bucket into board language, how do you decide what counts as a board-level risk versus noise?
Thanks, Ryan. That’s an important question. We distinguish board-level risk from technical noise based on business impact, data sensitivity, exposure, and potential consequences for compliance, financial loss, and reputation. An exposed S3 bucket, for example, becomes a board-level concern when it creates a credible path to sensitive data exposure or material business impact. GovIntel prioritises findings based on risk and business context, so executives can focus on decisions that matter rather than raw configuration alerts. I’m working to make that distinction clear and actionable in every assessment.
2 comments
Welcome to Lounge, Chetan. The read-only CloudFormation role with no agents seems like a smart way to lower the trust barrier for a security buyer. When you translate findings like an open S3 bucket into board language, how do you decide what counts as a board-level risk versus noise?
Thanks, Ryan. That’s an important question. We distinguish board-level risk from technical noise based on business impact, data sensitivity, exposure, and potential consequences for compliance, financial loss, and reputation. An exposed S3 bucket, for example, becomes a board-level concern when it creates a credible path to sensitive data exposure or material business impact. GovIntel prioritises findings based on risk and business context, so executives can focus on decisions that matter rather than raw configuration alerts. I’m working to make that distinction clear and actionable in every assessment.