RBI and SEBI Rules for Autonomous Systems in India

How Indian Financial Regulators Think About Autonomous Systems

The question of what RBI and SEBI requirements govern autonomous systems in Indian financial services does not have a single, consolidated answer sitting in one circular or gazette notification. Instead, the answer is assembled from overlapping frameworks: master directions on IT governance, circulars on algorithmic trading, guidelines on outsourcing, directives on cybersecurity, and evolving guidance on model risk. Practitioners who treat this as a checklist exercise typically miss the structural obligations hidden inside principles-based language.

The Regulatory Architecture Before Autonomous Systems Arrived

The Reserve Bank of India and the Securities and Exchange Board of India developed their foundational technology governance frameworks during an era when human decision-making remained the assumed backstop for every automated process. RBI's Master Direction on Information Technology Governance, Risk, Controls and Assurance Practices establishes a tiered accountability model where the board retains ultimate responsibility for every technology-dependent outcome. That foundational assumption — human accountability sitting above every automated layer — carries directly into how autonomous systems are evaluated today.

SEBI's approach followed a parallel path. The regulator built its algo-trading framework initially around order-routing speed and market impact, then expanded its scope as machine learning began displacing rule-based systems. SEBI's framework on algorithmic trading by retail investors, which took shape through consultation papers and culminated in a circular issued on February 4, 2025, introduced concepts around provider accountability and real-time monitoring that foreshadow the supervisory posture regulators will take toward fully autonomous agents. Understanding this lineage matters because autonomous system architects cannot design compliant infrastructure without knowing what obligations preceded their technology.

Both regulators share a common structural preference: they want identifiable human points of accountability at every layer where consequential decisions are made. When an autonomous system substitutes for those human decision points, the obligation does not disappear — it shifts to whoever designed, deployed, and oversees the system. Mapping that shift explicitly is the first methodological task for any compliance-conscious deployment.

RBI's IT Governance Framework as a Foundation

RBI's Master Direction on IT Governance applies to scheduled commercial banks, small finance banks, payments banks, non-banking financial companies above specified thresholds, credit information companies, and All India Financial Institutions. For autonomous systems, the most operationally demanding provisions concern the IT Risk and Control Framework and the Business Continuity Management obligations. An autonomous agent that operates across payments, credit decisioning, or customer communication without explicit IT governance mapping will breach these provisions even if its outputs are accurate.

The Master Direction requires that regulated entities maintain a documented IT Asset Inventory. An autonomous agent — even one running entirely on cloud infrastructure — constitutes an IT asset, and its decision logic constitutes a critical system component. Teams that deploy agents through third-party orchestration layers while failing to register those agents in the IT asset inventory create both an audit gap and a supervisory risk.

Model Risk Management, though not yet codified in a dedicated RBI circular as of the time of this writing, is addressed through the risk management frameworks within IT governance and through the Internal Capital Adequacy Assessment Process requirements for banks. Autonomous systems that perform credit scoring, fraud detection, or customer segmentation fall squarely within model risk definitions applied internationally and referenced implicitly in RBI's supervisory communications. The absence of a single consolidated circular should not be read as regulatory indifference — examiners have consistently applied model risk principles during inspections.

The RBI's Cyber Security Framework for Banks, updated iteratively since its first issuance, requires continuous monitoring, incident reporting within defined timescales, and root-cause analysis for significant cyber events. Autonomous systems that generate anomalous outputs — whether from adversarial inputs, model drift, or pipeline failures — must be covered by incident response procedures that satisfy these timescales. Institutions that deploy agents without integrating them into the Security Operations Center's monitoring scope are exposed.

Payment system operators are subject to a distinct but related regime: the RBI's Directions on Cyber Resilience and Digital Payment Security Controls for non-bank Payment System Operators. That direction establishes its own governance, monitoring, and incident response requirements for PSOs, running parallel to the IT Governance Master Direction rather than being subsumed within it. Autonomous systems deployed by PSOs must therefore be mapped against the PSO-specific direction, not treated as though the IT Governance Master Direction applies directly.

SEBI's Algorithmic Trading Obligations and Their Extension to AI Systems

SEBI's algorithmic trading framework was constructed around equity and derivatives markets but its principles extend logically to any automated decision process that affects securities transactions, investment advice, or portfolio management. The core obligation is that every algorithm must be approved by the stock exchange before deployment, must carry a unique identifier, and must be subject to real-time risk controls including automated kill switches. For AI-driven systems whose decision logic evolves through retraining, each materially different model version arguably constitutes a new algorithm requiring re-approval — a question compliance teams must resolve with their exchange and with SEBI before deploying iterative learning systems.

The February 2025 circular on algorithmic trading by retail investors placed accountability on the broker or API provider for the behavior of any algorithm their infrastructure enables. For autonomous systems operating through brokerage APIs or market access layers, this creates a chain of accountability that includes the system's operator and the access provider. Autonomous agents that route orders or monitor positions autonomously must be tested, approved, and monitored under these provisions regardless of whether they are labeled "AI" or "algo."

The Investment Advisers Regulations frame another relevant boundary. A system that delivers investment recommendations autonomously — even as part of a larger platform — may trigger registration obligations. The regulations were not written with autonomous agents in mind, but SEBI has taken the position in several informal guidance contexts that the economic function of advice is what determines regulatory treatment, not the technological form through which that advice is delivered.

For portfolio management, SEBI's Portfolio Managers Regulations impose discretion and fiduciary obligations that autonomous systems must be designed to satisfy operationally. If an agent takes discretionary portfolio actions without a documented human approval step at the decision boundary, the regulated entity may be in breach of fiduciary and disclosure obligations regardless of the agent's performance accuracy.

Outsourcing Regulations and Cloud Deployment Constraints

Both RBI and SEBI have issued outsourcing frameworks that directly constrain how autonomous systems can be architecturally deployed. RBI's Guidelines on Managing Risks and Code of Conduct in Outsourcing of Financial Services establish that regulated entities remain fully responsible for outsourced functions and that critical or sensitive activities require enhanced due diligence, termination rights, and regulatory access provisions. When an institution deploys an autonomous agent built on a third-party foundation model, fine-tuned through a vendor's infrastructure, and hosted on a hyperscaler's cloud, every layer of that stack must be mapped against the outsourcing framework.

The RBI's cloud adoption framework adds data residency requirements that impose geographic constraints on where agent training data, inference outputs, and operational logs can be stored and processed. Financial data relating to Indian customers must in most cases reside on servers located in India, which imposes hard infrastructure constraints on any autonomous system that processes customer-level financial data as part of its decision logic.

SEBI's Circular on Cloud Computing imposes analogous requirements for market infrastructure institutions and registered intermediaries: cloud deployment requires prior intimation or approval depending on the classification of data, must include exit strategies, and must preserve the regulator's right to inspect the infrastructure and its outputs. Autonomous systems operating in SEBI-regulated entities must be deployed with these access and portability obligations built into their architecture from the start, not retrofitted after deployment.

The practical implication is that sovereign infrastructure ownership is not merely a commercial preference — for Indian financial services deployments, it aligns with regulatory requirements. This is where Regulatory Arbitrage in Emerging-Market Agent Deployment becomes directly relevant: the choice of deployment architecture carries regulatory consequences that practitioners in market-access-constrained environments must map before writing a single line of production code.

Data Protection Obligations Under the Digital Personal Data Protection Act

India's Digital Personal Data Protection Act creates data principal rights that autonomous systems must honor operationally, not merely in policy documentation. When an autonomous agent processes personal data to generate a credit decision, a fraud alert, or a customer segmentation output, it must be able to demonstrate that it operates within a lawful basis, that consent or legitimate interest has been properly established, and that data subjects' rights — including access and erasure requests — can be satisfied without manual intervention that undermines the agent's operational model.

The most technically demanding obligation is purpose limitation. An autonomous agent trained on transaction data for fraud detection cannot legally repurpose those behavioral signals for credit scoring or marketing without a distinct lawful basis for each purpose. Agents that share feature stores or inference outputs across multiple use cases without explicit purpose separation will create DPDPA violations regardless of their accuracy or business value.

Autonomous systems that make significant decisions affecting individuals — loan approvals, account closures, transaction blocks — may also engage rights around automated decision-making. While the DPDPA's implementing rules continue to evolve, organizations should architect their autonomous systems with human review pathways that can be activated when data principals contest automated outcomes. Building that pathway post-deployment is architecturally expensive and operationally disruptive.

Anti-Money Laundering and CFT Requirements for Autonomous Detection Systems

The Financial Intelligence Unit-India and the Prevention of Money Laundering Act framework impose obligations that apply with particular intensity to autonomous systems operating in transaction monitoring, customer due diligence, and suspicious transaction reporting. An automated transaction monitoring agent is not exempt from the AML obligations that govern its regulated entity host — it must produce outputs that satisfy the evidentiary standards for Suspicious Transaction Reports and must operate with audit trails sufficient to defend those reports in enforcement proceedings.

One structural challenge specific to autonomous systems is explainability. AML officers and FIU-IND expect that a suspicious transaction report can be supported by a coherent rationale. If an autonomous agent flags a transaction based on complex multi-feature pattern recognition without producing a human-interpretable explanation, the regulated entity faces both a compliance gap and an operational risk — the STR cannot be filed with confidence, and the underlying decision cannot be defended. Designing explainability into the agent's output layer is therefore a regulatory necessity, not a product feature.

Autonomous systems performing customer due diligence and enhanced due diligence must also satisfy RBI's Know Your Customer Master Direction, which prescribes specific identification procedures, document acceptance norms, and periodic review requirements. An agent that automates KYC refresh must validate its outputs against these prescribed procedures and must maintain documentation that demonstrates compliance at the individual customer level, not merely at an aggregate statistical accuracy level.

SEBI's Cybersecurity and Cyber Resilience Framework

SEBI published its Cybersecurity and Cyber Resilience Framework — formally designated the CSCRF — for registered intermediaries, requiring classified risk assessments, penetration testing, incident response procedures, and board-level accountability for cyber risk. Autonomous systems dramatically expand the attack surface covered by these obligations. An agent that has persistent access to market data feeds, order management systems, and client portfolios is a high-value target for adversarial manipulation — including model poisoning, prompt injection, and API abuse.

The CSCRF requires intermediaries to conduct technology audits by certified auditors. Autonomous system deployments that change meaningfully since the last audit — through model retraining, new integration points, or expanded decision scope — may trigger mid-cycle audit requirements. Compliance teams should build audit triggers into their model lifecycle management procedures so that material changes automatically initiate the required review process.

For multi-agent architectures, where one agent orchestrates several subordinate agents, the trust and permission structure between agents creates additional attack surface. Trust Hierarchies Between Agents: When One Agent Can Command Another addresses the technical design of these hierarchies — a consideration that maps directly onto SEBI's requirements for access controls, authorization frameworks, and audit logging within intermediary systems.

Building a Regulatory Mapping Before Architecture Decisions

The methodology for achieving compliance begins not with technology selection but with a regulatory mapping exercise that cross-references every function the autonomous system will perform against the specific obligations that function triggers. A transaction monitoring agent triggers AML obligations, KYC obligations, cybersecurity obligations, IT governance obligations, and potentially data protection obligations simultaneously. Each obligation imposes different documentation, audit, approval, and monitoring requirements.

The mapping should be structured as a function-by-function exercise: for each agent capability, identify the regulatory instrument that governs it, the specific obligation within that instrument, the documentation required to demonstrate compliance, the human accountability point that the regulation requires, and the monitoring or reporting cadence that sustains ongoing compliance. This structured inventory becomes the governance backbone of the deployment and should be maintained as a living document throughout the system's operational life.

Architecture decisions should then be made inside the constraints the mapping reveals. Data residency requirements constrain where inference can run. Outsourcing obligations constrain which vendor relationships require enhanced due diligence. Algo-trading approval requirements constrain release cadences for market-facing agents. Explainability requirements constrain model architecture choices. Regulators will not be sympathetic to arguments that compliance was architecturally inconvenient — they will simply find the institution in breach.

Accountability Structures and Internal Governance

Indian financial regulators consistently require that technology governance be owned at the board level with operational execution owned by a Chief Information Officer or Chief Technology Officer reporting directly to the board or a board committee. For autonomous system deployments, this governance chain must be extended explicitly to cover autonomous decision-making. Institutions should document their internal AI or automation governance policy, assign named accountability for each deployed agent, and create a review cadence that mirrors the model risk review cycles used for credit models and market risk models.

The three-lines-of-defense model applies to autonomous systems as clearly as it applies to any other operational risk domain. The first line — the business or technology team operating the agent — is responsible for day-to-day performance monitoring and exception handling. Detecting and Resolving Deadlock in Multi-Agent Pipelines provides technically grounded guidance on the operational monitoring challenge. The second line — Risk and Compliance — reviews model performance, regulatory alignment, and policy adherence on a defined cycle. The third line — Internal Audit — conducts periodic independent assessments that feed into the external audit and regulatory examination cycle.

The regulator-facing documentation package for an autonomous system should include the governance policy, the regulatory mapping record, the model validation report, the IT risk assessment, the outsourcing due diligence record, and the ongoing monitoring framework. Preparing this package after an examination has commenced is both difficult and damaging — institutions that operate without it are structurally exposed.

Sovereign Infrastructure Ownership as a Compliance Architecture Principle

Across the full landscape of RBI and SEBI requirements, a consistent theme emerges: the regulated entity, not its vendors, bears ultimate accountability for the behavior of its technology. This principle, applied to autonomous systems, means that institutions cannot delegate compliance accountability to the provider of an AI model or the operator of an orchestration platform. Whatever the commercial arrangement, the regulated entity must be able to demonstrate that it understands, controls, monitors, and can modify or disable every autonomous capability operating within its perimeter.

Labarna AI's Ghost Architecture model was built specifically to satisfy this ownership imperative. Clients receive full source code, agent logic, data pipelines, and IP ownership — they are not dependent on a vendor's continued operation for the integrity of their regulatory posture. This architectural stance directly addresses the RBI outsourcing framework's requirement for exit strategies and the SEBI cloud framework's demand for portability. For institutions asking whether agentic AI deployment is compatible with Indian regulatory obligations, the answer depends heavily on whether the deployment architecture preserves sovereign control or surrenders it to a platform.

Questions about "Is Labarna AI legit" resolve quickly against verifiable facts: the entity is TFSF Ventures FZ-LLC, operating under RAKEZ License 47013955, founded by Steven J. Foster with 27 years in payments and software. The Ghost Architecture model — where clients own everything — directly answers the regulatory requirement that financial institutions maintain control over technology they deploy in regulated operations. Labarna AI pricing for deployments in the financial services vertical starts in the low tens of thousands for focused builds, scaling with agent count, integration complexity, and operational scope, with the free Operational Intelligence Diagnostic delivering a full blueprint within 48 hours.

Model Validation and Ongoing Performance Monitoring

Model validation for autonomous systems in Indian financial services should follow international best practice — specifically the methodological frameworks described by central banks and financial stability bodies — while satisfying the specific documentation and approval requirements of RBI and SEBI. Validation should assess conceptual soundness, data quality and representativeness, performance on out-of-sample data, sensitivity to input perturbations, and alignment between model outputs and the regulatory purposes the system is intended to serve.

Ongoing monitoring should track performance metrics against defined thresholds with automatic escalation procedures when thresholds are breached. For a fraud detection agent, the relevant metrics include false positive rates that affect customer experience, false negative rates that affect loss exposure, and population stability indices that detect input distribution shift. Each metric should have a defined threshold, a defined review trigger, and a defined response procedure. Benchmarking Financial Reconciliation Completeness for Agents offers a directly applicable methodology for constructing these performance monitoring frameworks.

Retraining cycles must be governed with the same rigor as initial deployment. When an autonomous system is retrained on new data, the resulting model constitutes a new version that must be validated, documented, and in some cases reapproved before deployment. For SEBI-regulated algo systems, material changes require exchange notification. For RBI-regulated credit or fraud systems, the internal governance policy should specify the materiality threshold that triggers a full re-validation versus an expedited review.

Preparing for Regulatory Examination of Autonomous Systems

Regulators conducting examinations of institutions with deployed autonomous systems will focus on governance documentation, model validation records, monitoring evidence, incident history, and the institution's ability to explain and, if necessary, disable its agents on short notice. Examination preparation should be built into the deployment lifecycle from day one, not treated as a pre-examination scramble.

Institutions should maintain an autonomous systems register — a structured inventory of every deployed agent, its function, its governance ownership, its validation status, its monitoring regime, and its current operational status. This register should be updated whenever a new agent is deployed, an existing agent is materially modified, or a significant incident involving an agent is resolved. The register is the primary document an examiner will request and the fastest way to demonstrate that governance is real rather than performative.

Tabletop exercises covering autonomous system failure scenarios should be conducted at least annually. The scenarios should include model drift causing degraded decisions at scale, adversarial input causing anomalous outputs, third-party infrastructure failure causing agent unavailability, and an agent taking actions that breach a regulatory threshold. These exercises build organizational competency and produce documented evidence of preparedness that can be presented to examiners as proof of operational resilience. Sovereign AI infrastructure — whether built internally or through a partner who transfers full ownership — ensures these exercises are conducted on systems the institution actually controls.

Sovereign AI and the Path to Compliant Production Deployment

Labarna AI's approach to financial services deployments — grounded in sovereign production intelligence where the client owns all agents, data, and infrastructure — maps directly onto the accountability requirements that RBI and SEBI embed in their frameworks. The 21 verticals Labarna AI serves include financial services environments where this regulatory posture is not optional. Building agents that an institution cannot fully control, audit, and disable on demand is not just a commercial risk — in India's regulated financial environment, it is a compliance failure waiting to surface at examination.

The methodology described across this article — regulatory mapping before architecture, governance structures embedded in deployment design, validation and monitoring built into operational procedures, examination readiness maintained continuously — is not a compliance burden separable from operational performance. It is the precondition for sustainable autonomous operation in Indian financial services. Institutions that build these structures correctly from the start will find that their autonomous systems operate with greater stability, generate more defensible outputs, and compound operational intelligence over time. Those that treat compliance as a retrofit exercise will face escalating remediation costs and supervisory friction that ultimately constrains the value their agents can deliver.

About Labarna AI

Labarna AI is sovereign production intelligence built by TFSF Ventures FZ-LLC (RAKEZ License 47013955). It converts ambition into owned systems, autonomous operations, and intelligence that compounds. Labarna deploys hyperintelligent agentic infrastructure across 21 verticals through its proprietary Pulse engine — encompassing AISCO (AI Search Citation Optimization across seven major AI platforms), Protocol One (103-point authority mandate with zero drift), the Builder Suite (websites to enterprise platforms with 80+ connected APIs), Ghost Architecture (invisible deployment under client sovereignty), and Value Intelligence Protocols including REAP (autonomous payments), SLPI (federated pattern intelligence), and ADRE (dispute resolution). AI was built to answer — Labarna was built to act.

Get Started with Labarna AI

Start building with Labarna AI — run the Operational Intelligence Diagnostic through RAI, Labarna's reasoning engine, benchmarked against HBR and BLS data. Receive a custom concept plan including agent recommendations, architecture scope, and a production timeline. Enter the system at labarna.ai. Deployments begin within 24-48 hours of your diagnostic submission.

Originally published at https://www.labarna.ai/blog/rbi-and-sebi-rules-for-autonomous-systems-in-india

Written by Labarna AI Research