Project Name

From 115 Security Vulnerabilities to a Governed MuleSoft Roadmap: Salesforce Advisory for a Global Nonprofit

From 115 Security Vulnerabilities to a Governed MuleSoft Roadmap: Salesforce Advisory for a Global Nonprofit
Industry
Non-Profit
Technology
Salesforce

Loading

From 115 Security Vulnerabilities to a Governed MuleSoft Roadmap: Salesforce Advisory for a Global Nonprofit
Overview

A globally operating nonprofit managing wish fulfilment, fundraising, and donor communications on Salesforce NPSP had been building on the platform for five years. Integrations were added to meet deadlines. Managed packages accumulated without licence governance. Business-critical automations ran through Zapier with no retry logic, no audit trail, and no error handling. No one had ever fully mapped what was running or what it connected to.

 

Ksolves was engaged to provide Salesforce consulting services: producing a complete integration map, identifying every risk, and designing the architecture the organisation needed to move forward safely. What the engagement produced was a complete integration inventory across 120+ endpoints, a prioritised security and risk register covering 2,452 Apex findings, and a four-phase MuleSoft integration modernisation roadmap that the organisation could take directly to its board.

Challenges
  • No Integration Map Existed: The org had accumulated 50+ inbound connected apps and 70+ outbound remote site settings, all point-to-point, with no central registry, no ownership model, and no documentation of what each integration did or who was responsible for it.
  • 115 Active Security Vulnerabilities: PMD static analysis across 139 custom Apex classes produced 2,452 code findings. Of these, 115 were ApexCRUDViolation findings where DML and SOQL operations executed without field-level security or CRUD enforcement, creating active data exposure risks across live business processes.
  • Governor Limit Exposure at Scale: SOQL queries and DML statements inside loops were present throughout the wish management codebase. During high-volume donation campaigns or wish intake surges, these patterns represented a scalability risk capable of causing transaction failures at the worst possible moment.
  • Expired Managed Package in Production: Conga Composer was operating on an expired licence with no documented migration pathway to the Conga Platform. Document generation across multiple business processes was running on borrowed time with no contingency in place.
  • Zapier Running Business-Critical Processes: Workflow automations the organisation depended on daily were executed through Zapier with zero observability, zero retry logic, zero audit trail, and zero error handling. A single silent failure would have caused process breakdowns with no visibility into what had gone wrong or why.
  • No Async Fallback Architecture: Every integration was synchronous. No Platform Events or Change Data Capture patterns were in place. Any downstream system outage propagated failures directly into Salesforce with no buffering and no graceful degradation.
Solution

Ksolves delivered the Salesforce Org Assessment across four structured stages: Discover (stakeholder interviews, metadata extraction, integration baseline), Analyse (pattern analysis, security review, DevOps posture), Synthesise (risk rating, roadmap sequencing), and Deliver (final report, executive presentation, Q&A). AI-assisted metadata extraction and pattern analysis across 139 Apex classes and 120+ integration endpoints compressed the analysis phase by approximately two weeks versus a conventional manual audit approach.

  • Complete Integration Inventory: All 50+ connected apps and 70+ remote site settings were catalogued, risk-rated, and mapped across 12 integration categories: Finance (Intacct), CMS (Drupal), Payments (Stripe), Communications (Twilio, Ortto), Document Generation (Conga, Formstack), Surveys (GetFeedback, SurveyMonkey), LMS (Litmos), Mapping (Salesforce Maps, HERE, Google, ESRI), and ad-hoc automation (Zapier). The output was a reusable, as-is System Landscape Diagram that the organisation had never had before.
  • Prioritised Risk Register: Every identified issue was rated by severity and assigned a remediation timeframe. The 115 ApexCRUDViolation findings, expired Conga licence, and Zapier dependency were classified as immediate actions (0 to 30 days). Governor's limit exposure was classified as short-term (1 to 3 months). Integration architecture modernisation was classified as a strategic investment (3 to 12 months).
  • Intacct and Drupal Deep-Dive: The two highest-risk data flows received detailed analysis. The Intacct managed package handling donation GL posting was identified as business-critical with no redundancy or observability. The Drupal wish intake flow was a CMS push with no error handling or data validation. Both were designated as Priority 1 MuleSoft API-led connectivity candidates.
  • Four-Phase MuleSoft Modernisation Roadmap: The to-be architecture places MuleSoft Anypoint Platform as the central governed middleware layer, replacing all point-to-point integrations with versioned REST APIs and adding Platform Events and Change Data Capture for event-driven async processing. The roadmap sequences Phase 2 (MuleSoft integration modernisation, Intacct and Drupal migration, Zapier retirement), Phase 3 (full Apex, Flow, and Data audit addressing all 2,452 PMD findings), and Phase 4 (Apex remediation, Conga Platform migration, DevOps maturity uplift, and Salesforce Data Cloud and Agentforce readiness).

Technology Stack

Category Technology
Core Platform Salesforce NPSP
Code Analysis PMD Static Analysis
Target Integration Layer MuleSoft Anypoint Platform
Event Architecture Platform Events and Change Data Capture
DevOps Gearset CI/CD
Result
  • 120+ Integration Endpoints Mapped: Complete integration inventory across 50+ connected apps and 70+ remote site settings, organised across 12 categories and produced as a reusable as-is System Landscape Diagram, the first complete view of the integration estate in the organisation's history.
  • 115 Security Vulnerabilities Documented with 0 to 30 Day Remediation Plan: Every ApexCRUDViolation finding logged with recommended fix and owner, giving the engineering team an actionable security remediation backlog and the board an evidence-based case for immediate investment.
  • 2,452 Apex Findings Categorised Across Security, Performance, and Best Practices: Full PMD static analysis baseline established, with each finding category mapped to a remediation phase and timeline across the four-phase roadmap.
  • Expired Conga Licence Flagged with Migration Pathway Defined: Document generation risk surfaced before a production failure, and a structured migration pathway to the Conga Platform was designed as part of the Phase 4 scope.
  • Zapier Retirement Plan Scoped and Sequenced: Every business-critical Zapier automation is mapped with Salesforce-native Flow and MuleSoft event-driven patterns specified as replacements, with full Zapier retirement scheduled as a Phase 2 deliverable.
  • Board-Ready MuleSoft Modernisation Roadmap Delivered: Executive-ready risk register and roadmap delivered, unlocking the Phase 2 investment decision with Intacct and Drupal scoped as the first MuleSoft API-led connectivity builds.
Data Flow Diagram
stream-dfd
Client Testimonial

“For the first time, we have a complete picture of everything running in our Salesforce org and a clear, evidence-based plan for what to fix first. The risk register gave us exactly the technical and business language we needed to have the integration modernisation conversation with our board.”

– CTO, Global Nonprofit Organisation

Conclusion

Ksolves delivers Salesforce consulting services and MuleSoft integration modernisation for nonprofit and enterprise organisations that need an independent, technically rigorous view of their platform risk before committing to a modernisation programme. Explore Ksolves Salesforce Advisory Services or speak to our team.

 

Before this engagement, the organisation had no integration map, no risk register, and no modernisation plan. After the three-week Salesforce Org Assessment, it had all three, plus a board-ready four-phase roadmap to a governed, scalable platform. The assessment itself was the value delivered, and it gave the organisation everything it needed to move forward with confidence.

 

Does your Salesforce org have integrations no one has fully mapped or Apex code that has never been audited? A structured Salesforce Org Assessment turns five years of accumulated risk into a governed modernisation roadmap in three weeks.

If Your Salesforce Org Has Grown Faster Than Your Governance, It Is Time For An Independent Audit.

Copyright 2026© Ksolves.com | All Rights Reserved
Ksolves USP