Cloudanix Achieves AWS Security Competency Status for Its CNAPP+ Platform and Just-in-Time Access Engine

Cloudanix – Your Partner in Cloud Security Excellence

How Often Should You Pentest? Treat Penetration Testing as a Portfolio

  • Purusottam Mupunu Purusottam Mupunu
  • Thursday, Nov 19, 2026

“How often should we pentest?” is one of the most common questions in security, and one of the least satisfying to answer. Once a year? Every release? After every big change?

Matthew Moog sent us exactly this question for our Scale To Zero episode with Raj Handa, Senior Cybersecurity Engineer in offensive security at Workday, where he leads the pentest program. Matthew asked how often you should pentest, and how to decide the mix between internal teams, external vendors, and continuous automated testing.

Raj’s answer reframed the question.

The Trap: Pentesting as a Calendar Event

“When you operate an offensive security program at enterprise scale, the biggest trap is treating penetration testing or red teaming as a single calendar event.”

It isn’t a checkbox you tick once a year, he said. “It’s actually an offensive portfolio. So you have to match the right adversarial tool to the right risk.” Get the match wrong and the cost is real:

“You’ll end up wasting a lot of dollars having elite hackers run your glorified vulnerability scan.”

Raj decides the mix using three distinct layers: velocity, context, and an unbiased perspective.

Layer 1: Continuous Automation (Velocity)

The first layer runs 24/7. Raj called it “your baseline hygiene.” It includes SAST scanning, external attack surface monitoring, and continuous CI/CD pipeline checks.

This layer answers the “how often” question for known, repeatable issues: always. It is also what frees your humans to do work only humans can do. If you are building out this layer, our post on shift-left security in practice covers where those checks sit in the pipeline.

Layer 2: The Internal Team (Context)

The second layer is your internal offensive security team, working continuously and leaning on threat modeling. Its schedule is not the calendar.

“Our internal engineers don’t really operate on an arbitrary schedule. They actually operate on architectural risk.”

When a product team redesigns a core tenant isolation boundary or rolls out a new AI agent, the internal red team is embedded right there.

“The superpower, I feel, of an internal team is the deep business context.”

Raj pointed out that an outside consultant can spend two weeks just learning how internal microservices talk to each other. The internal team already knows. They know the architectural shortcuts taken years ago, the business logic, and the data flows. That is how they break the features that are unique to your platform.

So for this layer, the trigger is change. A meaningful architectural change is the moment to test.

Layer 3: External Vendors (Unbiased Perspective)

The third layer is third-party penetration testing on a more structured, periodic cadence. At Workday, Raj said, external partners are rotated on a scheduled basis, “typically biannually or annually, depending on what you are testing,” and/or as a requirement before any major flagship release.

He brings in vendors for two reasons:

  • Regulatory. Every enterprise has compliance frameworks, and a third-party report serves as the control artifact.

  • Blind spots. External testers find what the internal team missed, and bring niche tradecraft. His examples: adversarial machine learning, model inversion, and bespoke hypervisor breakout techniques.

Why Rotate Testers?

I asked whether rotating vendors was a regulatory requirement. Raj said not necessarily. Some financial audits require rotating audit firms, but from a security standpoint the point is fresh eyes. That can even mean the same firm rotating its engineers on your project.

If the same person retests your application, they bring the same skill set as last time. A new tester brings a different way of looking at things.

“It’s an art at the end of the day. The more eyes you can get on your attack surface, the more blind spots you’ll be able to discover.”

How the Layers Feed Each Other

The point of a portfolio is that each layer makes the others better. As Raj put it, “each layer basically feeds into each other,” and “it’s not one solution fits all, but a mix and combination of all these various approaches.”

In a separate answer, he described what that looks like over time. In year one, findings might be basic configuration issues or missing headers. By year two or three, your automated pipeline should be catching that noise, and human testers should be finding business logic bypasses, complex tenant boundary hops, or tool-use escalation in AI agents. If they are not, your testing needs a second look. We cover that metric in Never Pay for the Same Bug Twice.

So, How Often?

Putting Raj’s answer into one line each:

LayerWhat it coversWhen it runs
Continuous automationBaseline hygiene: SAST, external attack surface, CI/CD checksAlways on
Internal teamBusiness logic, architecture, platform-specific featuresOn architectural change, such as a new tenant boundary or AI agent
External vendorsCompliance artifact, blind spots, niche tradecraftScheduled (biannually or annually) and before major releases

Pentest Portfolio Checklist

  • Baseline automation (SAST, attack surface monitoring, pipeline checks) runs continuously.

  • Internal testers are pulled in by architectural change, not a calendar.

  • New AI agents and tenant isolation changes trigger internal testing.

  • External tests are scheduled and also required before flagship releases.

  • Testers rotate, across firms or within one firm.

  • Each year’s findings are compared with last year’s: are basic issues moving to automation?

  • Each external finding is checked against what the internal team and automation should have caught (my addition).

Listen to the Full Episode

Thanks again to Matthew Moog for the question. Raj also covers extension confusion in AI editors, bug bounty in the age of AI-generated reports, and onboarding acquisitions safely. The extension confusion part has its own write-up: Extension Confusion: The IDE Supply Chain Risk Hiding in Your AI Editor.

Scale To Zero is the security podcast we run at Cloudanix. If you have a question you want a guest to answer, send it our way. Matthew’s turned into this whole post.

People Also Read

What Our Users Are Saying

Customer Reviews

Cloudanix is trusted by security leaders worldwide to deliver proactive, reliable, and cutting-edge cloud security.

One day, I changed the password of a root account, and my CTO called me within less than a minute to confirm if I did so. I was not expecting a reaction this quick. He told me Cloudanix alerted him of this password change and that he wanted to confirm as it was a critical security notification. I couldn't believe it!

Ritesh Agarwal
Ritesh Agarwal
CEO, Airgap Networks

Compliance is one way of staying secure, but what I want is the ability to go deeper and attain 'true security.' Cloudanix provides us the capability to do so.

Vishal Madan
Vishal Madan
Head of Engineering, iMocha

Cloudanix is building for the future of the cloud, which makes the product all the more desirable.

Ritesh Agarwal
Ritesh Agarwal
CEO, Airgap Networks

Cloudanix gave us the visibility we were missing. Being able to move from permanent access to a robust Just-In-Time (JIT) workflow has fundamentally changed our security posture without slowing down our engineering velocity.

Pavan Kumar Lekkala
Pavan Kumar Lekkala
SRE Lead, HugoHub

We are excited to leverage Cloudanix's comprehensive multi-cloud DevSecOps solution to secure our production workloads on AWS. Cloudanix has demonstrated that it can solve many challenges that DevSecOps teams face while continually adding new features such as SOC2 compliance and drift detection.

Satish Mohan
Satish Mohan
Co-founder & CTO, Airgap Networks

Managing third-party partner access was once a major concern for our security posture. With Cloudanix JIT Cloud, we've effectively achieved zero third-party risk. We can now grant access confidently, knowing that it is temporary, audited, and automatically revoked, resulting in a 100% reduction in our privileged access exposure.

Okesh Badhiye
Okesh Badhiye
Head of Technical Engineering, Finfinity

The snooze feature and responsible alerts have helped us save time and prioritize what to tackle first.

Satish Mohan
Satish Mohan
Co-founder & CTO, Airgap Networks

Implementing Cloudanix JIT internally allowed us to practice what we preach. By eliminating permanent access to our own clouds and databases, we've neutralized the risk of standing privileges, ensuring our own 'keys to the kingdom' are never left exposed.

Girish Manghnani
Girish Manghnani
Managing Partner, Tech Inspira

The problem with permissions is a lot of times, the gaps are left open due to oversights from inside the organization itself. With Cloudanix's CIEM, we get a complete view of user permissions and access. This enables us to update the permissions, reducing the attack surface.

Nilesh Pethani
Nilesh Pethani
Application Architect, iMocha

In the world of Fintech, trust is our currency. Cloudanix provided the frictionless visibility we needed to secure our EKS workloads across AWS, ensuring we stay audit-ready for SOC2 and GDPR without slowing down our engineering velocity.

Amol Naik
Amol Naik
Head of Security & Infrastructure, HugoHub

Cloudanix delivered value within 5 minutes of onboarding. Continuous monitoring, timely detection, and excellent documentation helped us attain a great cloud security posture.

Divyanshu Shukla
Senior DevSecOps, Meesho

Technology strategies and business strategies are in a state of constant change which includes centralization and decentralization of responsibilities. Regardless of strategic shift, we still have intellectual property to protect. Cloudanix are critical partners for us in our public cloud security posture across our three cloud providers.

Jerry Locke
Jerry Locke
Senior Director Global Solutions Engineering, Eversana

Cloudanix has been amazing. They opened up a common Slack channel with us — and it feels like we are talking to our own team and getting things done with Cloud security. The support team is always available, friendly, helpful, and ready to go out of their way.

Satish Mohan
Satish Mohan
CTO, Airgap Networks

Beyond just access management, Cloudanix CSPM has given us a unified view of our AWS environment. The real-time alerting and anomaly detection allow us to prevent any untoward activity before it happens, which is critical for a marketplace connecting 50+ financial institutions.

Okesh Badhiye
Okesh Badhiye
Head of Technical Engineering, Finfinity

For a Fintech company, data is our most valuable — and most sensitive — asset. Cloudanix DAM hasn't just improved our visibility; it has given us control. The ability to mask data and prevent unauthorized queries in real-time is a game-changer for our compliance and customer trust.

Jiten Gala
Jiten Gala
President Engineering and Product, Kapittx

Our clients, especially in the Middle East financial sector, demand absolute accountability. Cloudanix JIT Cloud has been a competitive differentiator for us, allowing us to provide secure, governed access to customer accounts that meet their strictest audit and compliance requirements.

Girish Manghnani
Girish Manghnani
Managing Partner, Tech Inspira

Cloudanix is always on my team's lips because of its exceptional support. Be it a small or big query, Cloudanix has gone above and beyond to resolve them. This one's a keeper for us.

Sujit Karpe
Sujit Karpe
CTO, iMocha

For a long-lasting partnership, great support goes a long way. Cloudanix has delivered exceptional support whenever required. Their edge is their team is always ready to go beyond to solve any issues that we have. This speaks volumes about the culture at Cloudanix.

Akash Maheshwari
Akash Maheshwari
Co-founder, MoveInSync

Beyond the technology, Cloudanix feels like an extension of our own team. Their willingness to stand up a dedicated Middle East tenant for us and provide exceptional support at a sensible price makes them a long-term partner for Hugosave.

Surya Tamada
Surya Tamada
CTO, HugoHub

The real-time notifications that Cloudanix provides are a real lifesaver. Their adaptive notifications ensure that my team stays productive and doesn't get interrupted all the time.

Digvijay Singh
Staff Security Engineer, Meesho

The whole point in technological evolution is to help improve the world we live in. We must protect that and to do so requires an effective and efficient security strategy. The Cloudanix team helped make our public cloud security posture management strategy a reality. The symbiotic relationship we have allows for a continuous feedback loop which is how business should operate.

Larry Wheat
Larry Wheat
Staff Solutions Engineer, Eversana

Ready to see your graph?

Connect a cloud account in under 30 minutes. See every finding rooted in identity, asset, and blast radius — with a fix path attached.

Book a Demo