Niladri Sekhar Hore
Sr Staff Engineer | StoneX
Bengaluru, India
Actions
With over a decade of experience spanning data engineering and cybersecurity, Niladri is a versatile and accomplished professional currently working at StoneX, where he focuses on advancing cyber defence, observability, and secure data systems at scale. His career has included pivotal roles at leading global firms such as Cognizant, Eli Lilly, Accenture, and KPMG, where he has driven initiatives in eDiscovery, digital forensics, GRC, security engineering, and cloud observability.
Combining hands-on technical expertise with strategic vision, he brings a unique lens to solving complex problems at the intersection of data, threat operations, and governance. His recent work explores synthetic media abuse, deepfake detection, and the evolution of adversarial AI in enterprise environments.
Area of Expertise
Topics
Self-Healing Architectures: The Next Phase of Cloud Resilience
1. Abstract
Cloud computing solved scalability. Automation solved speed. But resilience still depends on humans noticing something is wrong and fixing it.
As infrastructures become more ephemeral, this dependency has become our weakest link.
The next revolution is self-healing architecture—cloud platforms that can detect, diagnose, and remediate faults automatically. By combining telemetry, control theory, and AI-driven feedback, systems can transition from reactive to autonomous recovery.
This session explores the anatomy of a self-healing loop—detect → analyze → act → learn—and the design principles that make it safe and reliable. We’ll discuss real-world patterns emerging from large-scale cloud deployments: adaptive scaling, intelligent rollback, service-mesh introspection, and learning-based remediation.
Attendees will leave with practical blueprints for embedding autonomous recovery in modern architectures—balancing human judgment with machine speed, and creating infrastructures that don’t just survive failure, but grow stronger because of it.
Key takeaways
Understand the architecture of self-healing feedback loops
Learn how telemetry and machine learning combine to drive autonomous recovery
Design guardrails for safe, auditable automation
Build resilient systems that evolve through failure, not despite it
2. Problem / Overview
Despite extensive automation, most cloud operations remain reactive.
When an outage occurs, engineers intervene manually—investigating logs, rerouting traffic, restarting pods, or rolling back deployments.
This manual recovery introduces:
Latency — Every minute of human triage extends downtime.
Inconsistency — Resolution quality depends on who’s on call.
Cognitive fatigue — Alert overload erodes focus and morale.
Traditional redundancy and auto-scaling mitigate some failures but cannot reason about complex, cascading ones.
What we need are systems that observe themselves and apply the same DevOps feedback loop—Build → Measure → Learn—internally, at runtime.
3. Research and Industry Signals
Autonomic Computing Redux
IBM’s early-2000s vision of autonomic systems predicted four pillars: self-configuration, self-optimization, self-healing, and self-protection. Two decades later, cloud-native telemetry and AI make this achievable at scale.
Reinforcement Learning for Operations
Studies from Google’s DeepMind and Microsoft Research show that reinforcement models can optimize data-center cooling and resource allocation with minimal human input—proving closed-loop control is viable for production workloads.
Predictive Failure Detection
Correlating time-series metrics with event data enables early failure prediction; one telecom provider reduced mean time to recovery (MTTR) by 47 % using anomaly-driven auto-rollback logic.
Human Factors in Autonomous Ops
Safety-critical industries demonstrate that trust, transparency, and graceful degradation are essential when automation makes decisions. The same principles now apply to cloud reliability.
4. Anatomy of a Self-Healing System
A self-healing architecture consists of five interacting layers:
A. Sense Layer – Continuous Telemetry
Capture metrics, logs, traces, and health probes in near real time.
Use adaptive sampling to focus on high-entropy signals during anomalies.
B. Analyze Layer – Intelligent Diagnosis
Correlate anomalies across services. Employ pattern recognition and causal inference to determine likely root causes.
C. Act Layer – Automated Remediation
Trigger context-aware runbooks: restart pods, roll back versions, or shift traffic through service-mesh policies. All actions must be idempotent and reversible.
D. Learn Layer – Feedback and Evolution
Every intervention becomes new training data. The system refines its thresholds and remediation strategies through reinforcement.
E. Govern Layer – Safety and Accountability
Implement approval gates, audit logs, and explainability. Humans remain in control of policy; machines execute within defined boundaries.
5. Human in the Loop
Full autonomy without oversight is risky. Effective self-healing keeps humans in the feedback loop:
Observable Automation – Operators can see why the system acted.
Graceful Escalation – When confidence drops, control returns to humans.
Blameless Learning – Post-incident reviews feed improvements back into automation logic.
This balance creates trustworthy autonomy—a partnership, not a replacement.
6. Patterns and Implementation Blueprints
Event-Driven Remediation
Use message queues or event buses to trigger healing workflows. Example: A failed health probe publishes to a topic consumed by a function that replaces the failing node.
Declarative Guardrails
Store recovery logic as code—policies expressed in YAML or Terraform, versioned and reviewed like any deployment artifact.
Feedback Pipelines
Connect incident management systems back into CI/CD to automatically adjust tests, thresholds, or deployment canaries.
Anomaly-Aware Scaling
Instead of CPU thresholds, scale based on anomaly probability or latency deviation models.
Policy-Driven Rollback
Implement canary analysis that rolls back automatically when error budgets breach.
7. Ethics and Safety in Autonomous Recovery
Automation that acts without supervision must follow ethical guidelines:
Explainability: Every decision should have an interpretable rationale.
Fail-Safe Defaults: When uncertain, prefer containment over aggression.
Auditability: All actions logged for post-mortem review.
Bias Awareness: Ensure models are trained on diverse failure data to prevent blind spots.
Privacy: Telemetry used for learning must avoid leaking sensitive customer information.
8. Case Studies and Emerging Practices
A. Kubernetes Self-Healing Controllers
Health-check controllers automatically recreate failed pods, but newer operators integrate ML models that predict degradation before failure.
B. Serverless Resilience Loops
Functions observe their own latency and concurrency, invoking fallback logic when upstream APIs slow down.
C. Observability as Feedback Fuel
Modern observability stacks feed incident insights directly into remediation runbooks, enabling progressive automation.
D. Digital Twin Simulations
Some organizations simulate entire infrastructures to test how self-healing behaves under chaos—closing the loop between experimentation and production.
9. Organizational and Cultural Impact
Introducing self-healing changes team dynamics:
Role Shift: SREs evolve from firefighters to automation architects.
Trust Building: Start with “shadow mode” where automation suggests actions before executing them.
Skill Evolution: Engineers learn feedback design, policy writing, and AI governance.
Measurement: Track “mean time to confidence” instead of merely MTTR.
This cultural evolution mirrors the DevOps transformation a decade ago—only now, humans collaborate with intelligent systems rather than just each other.
10. Research and Future Directions
Reinforcement Learning for Policy Optimization – Adaptive runbooks that evolve through reward signals (recovery speed, stability).
Federated Resilience Models – Sharing anonymized failure patterns across organizations to improve collective robustness.
Cognitive Service Meshes – Network layers that understand context and reroute intelligently.
Ethical Autonomy Standards – Developing open frameworks for safe self-healing behavior akin to AI safety initiatives.
11. Conclusion
Self-healing is not a luxury feature; it’s an evolutionary step in system design. We can no longer afford architectures that depend on human reflexes to survive complexity.
By embedding continuous learning and ethical automation, our infrastructures can transform from brittle to anti-fragile—gaining strength through stress.
The next era of cloud resilience belongs to systems that do more than recover:
they listen, reason, and adapt.
12. Key Takeaways (Recap)
The feedback-loop blueprint for self-healing architectures
How to pair AI/ML with event-driven remediation safely
Cultural and ethical practices for human-in-the-loop autonomy
Practical steps to evolve existing DevOps automation into learning systems
Niladri Sekhar Hore - The Deepfake Supply Chain
In an era where synthetic media and deepfakes are becoming tools of choice for adversaries, this session delivers a deep dive into the entire lifecycle of a synthetic media attack—from initial OSINT gathering to monetization through fraud and extortion. Drawing from real-world incidents, cutting-edge research, and red-team simulations, we’ll dissect how deepfake-based attacks are operationalized, bypass controls, and reshape the threat landscape across sectors.
Finally, the session presents a comprehensive defense framework—covering AI-driven detection techniques, content authenticity infrastructure (C2PA), security engineering controls, and organizational playbooks for executive impersonation response. By the end of this session, security professionals, risk leaders, and technical architects will be equipped with actionable strategies to detect, disrupt, and defend against synthetic media threats in the real world.
CODE BLUE 2025 Sessionize Event
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top