
Discover why enterprise leaders are moving beyond "vibe coding" to hardened SaaS governance. This blog explores the 2025 security trends for ServiceNow and Salesforce, highlighting how automated approval gates and real-time scanning remediate thousands of IAM, AppSec, and data confidentiality risks. Learn to manage "agentic AI" and shift-left governance to eliminate security debt before it reaches production.

In April 2025, Patrick Opet, the Chief Information Security Officer of JPMorgan Chase, issued a stark open letter that reverberated across every enterprise boardroom. His message was a clarion call for a fundamental shift in the software supply chain: “Security must be built in by default.”
For organizations running massive platforms like ServiceNow and Salesforce, the risks Opet highlighted—SaaS sprawl, opaque third-party integrations, and the erosion of traditional security boundaries—are no longer theoretical. As we move toward an AI-native development lifecycle, where AI agents and “vibe coding” (accelerated, intent-based development) push changes to light-speed, the “Shared Responsibility Model” is being pushed to its breaking point.
The SaaS Security Paradox: Visibility vs. Velocity
The rapid adoption of enterprise SaaS has delivered immense value, but it has also quietly introduced dangerous concentration risk. The complexity of managing thousands of custom integrations, complex Access Control Lists (ACLs) in ServiceNow, or sprawling Permission Sets and Profiles in Salesforce has made traditional, annual compliance checks obsolete.
Our data from 2025 reveals a significant trend: Security debt is accumulating in pre-production. While production environments are often hardened, development and sandbox environments—where the actual “building” happens—are frequently left with lax governance. This creates a “phantom” attack surface where insecure configurations are born and eventually promoted.
Moving from Best Practices to Hardened Governance
Security in SaaS is often mistaken for a simple checklist of “best practices.” In reality, true security requires enforceable governance.
Quality Clouds enables organizations to go beyond code scanning by baking governance into the workflow. Whether it is ServiceNow ACLs or Salesforce Permission Set Groups, any change to the security fabric can be subjected to automated approval gates.
For Salesforce specifically, this means hardening the perimeter through strict IP controls. Our platform ensures:
Enforced Login Ranges: Verifying that IP addresses in login ranges are enforced at the user level.
Network Perimeter Integrity: Flagging trusted IP ranges that are defined too widely, preventing unauthorized lateral movement.
Deployment Guardrails: Preventing the deployment of Profiles that lack defined IP ranges.
By the Numbers: What we caught in 2025
Quality Clouds monitored and helped remediate thousands of issues last year across global enterprise instances. The breakdown shows that security is rarely about a single “big” bug, but a thousand small openings.
ServiceNow Security Remediation
Salesforce Security Remediation
Managing the “Agentic” Future
One of the most urgent calls in the JPMC letter is to “manage third-party integrations carefully.” In the modern ecosystem, this is compounded by the rise of Agentic AI—tools like Now Assist or Agentforce that don’t just suggest code but actively modify logic.
When an AI agent or a “citizen developer” modifies an access rule or creates a new Scripted REST API, they often prioritize functionality over the “Principle of Least Privilege.” Quality Clouds acts as the deterministic “brakes” (or enabler) for this high-velocity engine.
Moving Beyond Annual Compliance
Companies demand “demonstrable evidence that controls are working effectively” in real-time. Quality Clouds provides this continuous assurance by:
Continuous Enforcement: Moving from “point-in-time” audits to real-time policy enforcement.
Preventing “Implicit Trust”: Flagging integration accounts using admin roles and identifying jobs without dedicated integration users.
Shift-Left Governance: In 2025 alone, our real-time scanning tools prevented over 62,000 issues from entering codebases, saving an estimated 500+ days of technical debt remediation.
The Bottom Line for Leadership
Governance shouldn’t be a bottleneck; it should be the foundation that allows you to innovate with AI and low-code safely. If your security posture relies on manual reviews of a thousand moving parts, you aren’t governing—you’re hoping.
Quality Clouds provides the automated, independent oversight needed to ensure your SaaS platforms remain secure assets, not systemic risks.
Ready to see the invisible risks in your instance?
Start scanning your ServiceNow and Salesforce environments today and get immediate visibility into your security governance

Albert Franquesa
Co-Founder & CSO, Quality Clouds
Related articles
Stay ahead of the curve

How do I build thee (with AI)? Let me count the ways

Ignacio Sales
11 min read
Seven ways to build on ServiceNow with AI, three places the code lands, and where Quality Clouds for ServiceNow checks each one.

ServiceNow and GitHub: how to govern pull requests when your apps move to source control

Taher Dohadwala
6 min read
ServiceNow source control works per application and the diff is XML. Here's what that means for pull requests, update sets, and where to put the gate.

Norma Analytics: how much of your code was checked before commit

Albert Franquesa
4 min read
How much of your committed code was checked in the editor first, which client checked it, and what got fixed before it landed.