top of page

Nasuni Achieved 100% Compliance with SLA Response

pexels-diva-plavalaguna-6146816.jpg
Challenges

Intertek depended on Nasuni for global access to invoices and critical files, where disruptions directly impacted operations. The root cause was operational architecture gaps including certificate lifecycle risks, tight integrations, and limited observability.

Outcome

Nasuni Achieved 100% Compliance with SLA response

Solution

Managed Services

Challenges
Solution
Technology Stack 
Outcomes

Intertek’s global operations depend on uninterrupted access to business-critical files, where Nasuni serves as the backbone for invoice workflows and cross-system integrations across regions.


In such an environment, even minor disruption adversely affects major financial processes and compliance controls. The expectation was to have continuous availability paired with strict SLA response and resolution adherence.


Intertek faced operational risks in managing Salesforce and MuleSoft integrations. What followed was a structured operational hardening initiative that redefined Nasuni as a managed service layer, where engineered controls and ISLA Compliance Automation ensured Nasuni Achieved 100% Compliance.

Client Problem


When global operations depend on file access, “mostly stable” is considered not stable enough.


Intertek relies on Nasuni as a cloud-native file services layer powering invoice access and critical documentation across multiple geographies. If access breaks, business slows immediately, finance teams keep waiting, downstream integrations fail and audit trails become vulnerable.


From a business point of view, downtime wasn’t acceptable. And from a governance standpoint, SLA response and resolution compliance wasn’t optional.


  • Technically, the environment carried several hidden fault lines:


  • Always-on access requirements across regions and time zones


  • Strict incident and change management operations with audit sensitivity


  • SSL certificate lifecycle management Nasuni risks, where a missed renewal could instantly break secure access


  • Tight integration dependencies like Salesforce and MuleSoft where file structures effectively functioned as interface contracts


  • High fragility to config failures, something as small as a folder naming change could cascade into invoice download failures


The environment wasn’t failing terribly, but it was exposed. Without engineered operational hardening, small issues had the potential to become audit events or SLA breaches.


Root Cause Analysis


Instead of directly starting with the implementation, Cloudaeon conducted deep research on identifying the root cause through a detailed analysis.


We came to the conclusion that this was not a platform instability issue. It was an operations architecture gap.


Three systemic risk patterns emerged:


  1. Certificate Lifecycle as an Unmanaged Risk Surface


SSL certificates were treated as periodic admin tasks instead of lifecycle-governed assets. Expiry equals outage. In a globally distributed file system, that becomes a Severity-1 scenario.


  1. Cross-System Coupling Increased Blast Radius


Nasuni NMC, Edge Appliances and Access Anywhere were not operating in isolation. They were tightly coupled with Salesforce workflows and MuleSoft orchestration, where folder structures and naming conventions acted as implicit API contracts.


That meant minor changes could break invoice retrieval at scale.


  1. Partial Observability Inflated MTTR


Continues monitoring answered the questions like “Is it up?”, but failed to answer the


  • Is NMC healthy?


  • Are Edge Appliances syncing?


  • Is Global File Acceleration functioning?


  • Are volumes stable?


  • Is sync lag increasing?


Without deep signal telemetry across Nasuni NMC Edge Appliances Access Anywhere monitoring, root cause isolation takes longer and SLA clocks do not pause during diagnosis.

Solution Architecture


One thing was clear with root cause analysis, that the solution we had to implement had to be conceptualised before being technical.


Nasuni was redefined from “storage platform” to “managed service layer.”


Cloudaeon implemented a five-layer operational architecture:


Observability Layer


End-to-end monitoring across:


  • Nasuni Management Console (NMC)


  • Edge Appliances


  • Access Anywhere


  • Global File Acceleration signals (volume health, sync activity, storage utilisation, file health)


Eventing and Alerting Layer


Real-time anomaly detection and log-driven alerting to reduce time-to-detect and eliminate alert noise.


Operational Control Layer


Incident and change management operations were aligned to governance controls, ensuring SLA response and resolution compliance with complete audit traceability.


Risk Lifecycle Layer


Proactive SSL certificate lifecycle management Nasuni processes:


  • Expiry tracking


  • Planned renewals


  • Secure installation


  • Validation


Integration Assurance Layer


Active monitoring of Nasuni ↔ Salesforce ↔ MuleSoft contracts was done to prevent structural mismatches and sync failures.


This is where ISLA Compliance Automation became foundational, embedding SLA enforcement logic directly into operational workflows instead of managing it through manual oversight.


How We Delivered


Cloudaeon execution followed a disciplined engineering model, which was completed step by step engineering:


  • Established comprehensive monitoring across all Nasuni surfaces and sync signals


  • Implemented real-time alerting with log hygiene to reduce false positives


  • Operationalised SSL certificate lifecycle management, Nasuni end-to-end


  • Executed production-grade patching within controlled windows, including post-change stability validation


  • Aligned workflows to governance requirements for audit-ready change documentation


  • Introduced first-cut diagnostics to reduce MTTR before vendor escalation


  • Stabilised integration pathways to prevent sync drift and folder mismatch failures


  • Resolved a Severity-1 incident caused by folder naming inconsistency impacting invoice downloads, root cause isolated and restored with minimal business disruption


  • Delivered operational reporting dashboards for decision transparency


  • Upgraded Nasuni NMC and Edge Appliances to supported versions


We made sure that the SLA response and resolution compliance was no longer reactive but engineered.

Technology Stack


  • Nasuni Management Console (NMC)


  • Nasuni Edge Appliances


  • Nasuni Access Anywhere


  • Global File Acceleration (GFA)


  • Salesforce


  • MuleSoft


  • SSL certificate lifecycle tooling

Outcomes


  • Nasuni Achieved 100% Compliance with SLA response and resolution timelines


  • Zero missed SLA windows post operational hardening


  • Severity-1 incident resolved with rapid root-cause isolation


  • Seamless invoice access maintained globally


  • On-time upgrades and patching were executed without escalations


  • Reduced MTTR through internal first-cut diagnostics


ISLA Compliance Automation ensured response metrics were systematically met than manually tracked.


POD & Managed Ops Transition


Intertek’s engagement with Cloudaeon followed a Special Forces Engineering model: Solutions → POD → Ops.


Solution


Hardening through monitoring, lifecycle risk controls and disciplined governance-aligned execution.


POD


A dedicated operational unit took accountability for:


  • First-line diagnostics


  • Integration contract enforcement


  • Runbook optimisation


  • Continuous operational hardening


Managed Ops


Delivered as Nasuni managed services 24/7 operations:


  • Continuous monitoring


  • Proactive risk mitigation


  • SLA response and resolution compliance enforcement


  • Incident and change management operations with full audit alignment


Nasuni transitioned from a fragile dependency to a predictable service layer.


That is how Nasuni Achieved 100% Compliance, through engineered operational design, not reactive support.


Conclusion


Nasuni Achieved 100% Compliance because the operations were redesigned with engineering discipline and the required technical expertise. Additionally, naturally embedded governance and ISLA Compliance Automation were at the core.


What was once a risk-prone global dependency became a resilient, audit-aligned managed service with predictable SLAs, reduced MTTR and zero tolerance for operational failures.


For organisations where downtime translates directly into business and compliance exposure, this is the difference between reactive support and engineered stability.


If your Nasuni or enterprise file platform requires similar hardening, speak to a Cloudaeon expert to assess how your operational architecture can be strengthened for measurable, SLA-backed performance.

We ready for Help you !

Take the first step with a structured, engineering led approach. 

bottom of page