Tosh Defence
CYBER DECEPTIONIn active development

MAYA माया

Military Autonomous Yield-intelligence Architecture

“The attacker sees what we want them to see.”

On-prem
Customer-operated deployment
MITRE
ATT&CK-mapped context
Air-gap
Designed for disconnected networks
Human
Authority over consequential response

THE PROBLEM

Firewalls, antivirus and intrusion detection are essential, but an intruder who gets past them can move quietly for a long time before anyone notices. Defenders need signals that are hard for an intruder to avoid and easy for an operator to trust. MAYA places approved decoy assets where an intruder is likely to look, so that touching one becomes an early, high-signal indication that something is wrong.

THE SOLUTION

What MAYA Does

MAYA is a defensive cyber-deception and incident-intelligence platform in active development. It is designed to deploy approved honeypots, honeytokens and canary artefacts across a network the customer controls. No legitimate user has a reason to touch a decoy, so an interaction with one is a high-signal event worth an operator's attention. It is not proof of malice on its own: scanners, misconfigured tools and authorised testing can also reach a decoy, and MAYA is designed to surface that context.

MAYA maps observed behaviour to MITRE ATT&CK and produces incident context that an operator can read and act on. Automated containment is treated as a consequential action: it runs only within approved rules, network policy and rollback behaviour, under defined human authority. MAYA runs inside the customer's own boundary, on-premises or air-gapped, with no mandatory external runtime dependence.

MAYA

माया (MAYA) - Illusion. That which appears to be but is not. In Vedantic philosophy, Maya is the illusion that conceals the truth beneath. An intruder who reaches a MAYA decoy sees a convincing asset, while the defender sees the intruder.

CAPABILITIES

Key Features

Approved Honeypots

SSH, web, database and network-service decoys placed in network segments the customer approves, configured to resemble real assets in that environment.

Honeytokens

Decoy credentials and keys placed in approved locations. Their use is a high-signal indicator, raised to operators with the context needed to verify it.

Canary Artefacts

Decoy documents and records designed to signal when they are opened or moved, within the limits of the environment they are deployed in.

Behaviour Context

Observed actions, tools and sequences are grouped into a behaviour picture of the interaction. MAYA describes what happened; it does not attribute an actor.

MITRE ATT&CK Mapping

Observed behaviour mapped to MITRE ATT&CK tactics and techniques, giving security teams a shared, standard vocabulary for each incident.

Policy-Bounded Response

Containment actions such as blocking or isolation run only under approved rules, network policy and rollback behaviour. Consequential actions follow a defined human authority model.

Incident Narratives

Plain-language incident summaries drafted for operators and commanders, with the underlying events kept alongside for verification.

Adaptive Decoy Placement

Design direction: propose additional decoys along likely lateral-movement paths, deployed only within pre-approved placement policy.

DEPLOYMENT OPTIONS

Product Tiers

MAYA Core

Internal network deception: approved decoys deployed inside the customer's perimeter. In active development; scope confirmed through a controlled demonstration.

MAYA Edge

Phase 2

Internet-facing deception: decoy services on approved external addresses, to observe hostile activity before it reaches the perimeter.

MAYA Sentinel

Phase 3

Authorised exercise support: simulated activity against MAYA decoys to help security teams measure and improve their own readiness.

CUSTOMER CONTROL COMPARED

Why MAYA?

Externally Hosted Platforms
MAYA
Data control
Event data often processed in the vendor's environment
Designed to run on-premises, on customer infrastructure
Assurance
Assured under the vendor's own jurisdiction and processes
Alignment pathway to the customer's national standards, confirmed per deployment
Organisation-specific tuning
Generic enterprise templates
Decoys configured to the customer's environment and threat profile
Inspectability
Limited visibility into internals
Documented interfaces, inspectable deployment and export paths
Deployment
Often depends on vendor cloud connectivity
Designed for air-gapped and disconnected networks

“A deception layer reveals how your defences are arranged, so it should stay under your control. MAYA is designed to be owned, inspected and operated inside your own boundary, with human authority over every consequential response.”

Claims boundary

What MAYA is designed to do, and what we do not claim

MAYA is in active development. We publish its design intent and its limits side by side, so security teams can judge it on evidence rather than adjectives.

Designed to

  • Deploy approved honeypots, honeytokens and canary artefacts inside a boundary the customer defines.
  • Identify interactions with those decoy assets and raise them as high-signal events.
  • Map observed behaviour to MITRE ATT&CK tactics and techniques.
  • Produce operator-readable incident context for the security team.
  • Run containment actions only within approved rules, network policy, rollback behaviour and human authority.

What we do not claim

  • No claim of zero false positives. Decoy interactions are high-signal, but scans, misconfigured tools and authorised testing can also touch a decoy.
  • No published response-time, detection-time or dwell-time figures until dated test evidence with explicit scope exists.
  • No attacker attribution or actor classification. MAYA provides behaviour context, not identity.
  • MAYA complements, and does not replace, existing perimeter, endpoint and monitoring controls.
  • No formal certification is claimed. Alignment to national standards is a pathway, confirmed per deployment.

MAYA is aligned to iDEX DISC 14, Challenge 74 (Indigenous Cyber Deception Framework). This describes problem fit only, not selection, award or contract.

INTEGRATION

Works With

Customer-approved internal network segments
SOC and SIEM systems, through documented interfaces
MITRE ATT&CK framework
Customer-approved threat intelligence sources
Incident reporting to national CERT processes, where required
Target integrated workflow: DRISHYA infrastructure correlation and Tosh AI incident summaries, proposing bounded next actions for approval

DESIGNED FOR

Who It Serves

Defence Networks
National-Security Agencies
Critical Infrastructure
Government IT
Financial Institutions
Telecom Operators

Built in India. Designed for Sovereign Nations.

Engineered in India for lawful deployment by sovereign nations and approved organisations. Customer-controlled infrastructure, documented interfaces and export paths, and no mandatory runtime dependence on infrastructure outside your boundary.

Ready to See MAYA in Action?

Start with a controlled demonstration scoped to your operational problem, security boundary and existing systems. Available to sovereign and approved organisations, subject to applicable export law.