Saket Mohan

If a low-cost connected product can be misused, the weakness usually lies earlier—in procurement, architecture, development, validation, supply-chain onboarding or post-production monitoring. The durable fix is secure-by-design development, supply-chain visibility across battery-management systems, apps, firmware and connected components, basic authentication, cryptography and access control, continuous monitoring, and incident-response playbooks.

The post reports that a Bluetooth-enabled battery-management-system app was misused to remotely disable e-rickshaws in India.

• The government asked Google and Apple to remove the BAT-BMS app.
• Mohan says Secure Elements India reviewed the app behaviour and carried out its own assessment, but withholds technical details for responsible disclosure.
• The post says the reported impact appeared limited to disabling the battery system and asks what would happen if the same weakness affected charging, thermal controls or another safety-critical function.

The same lifecycle framing appears in posts on software-defined vehicles and the UK–India CETA. Mohan lists TARA, secure architecture, SBOM, embedded intrusion detection, secure OTA and fleet-level monitoring as parts of one security program.

Read original · Original 2 · Original 3

Vehicles need continuous intelligence and risk-aware decisions across the lifecycle, so detection, analysis, decision and secure deployment should operate as one loop. That means combining intrusion detection, security operations and compliance rules with update delivery.

At CAEVExpo 2026 Bangalore, eSyncSynapse was unveiled through a collaboration with Excelfore.

• Mohan describes it as combining CRISKLE IDS, CRISKLE MSOC, UNECE R155 and R156, and eSync OTA to connect detection, analysis, decision and secure deployment at fleet scale.
• They thank Shrikant Acharya, Shrinath Acharya and Rituraj Shrivastava for their guidance and confidence in the team.

Read original

Interpreting a regulation is not the same as running it: risk assessment, SBOM, vulnerability management, PSIRT, compliance documentation and post-market monitoring have to work together across the product lifecycle.

CRISKLE Workspace supports EU Cyber Resilience Act compliance.

• Mohan points to CRA reporting obligations beginning 11 September 2026 and says the workspace helps organisations move from interpreting regulation to operationalising compliance.
• They invite readers to register interest.

In other posts, Mohan names ISO/SAE 21434, AIS 189/190 and UNECE R155/R156 in the same practical, engineering-focused way.

Read original · Original 2 · Original 3

UK automotive SMEs need local investment, trusted partnerships, regulatory alignment, IP protection and long-term commitment to capture opportunities in India's electric, connected and software-defined mobility market.

The UK–India Comprehensive Economic and Trade Agreement enters into force on 15 July 2026.

• Mohan writes that Secure Elements UK is growing its presence in Bengaluru with Secure Elements India, headed by Rituraj Shrivastava.
• They list cybersecurity work across TARA, secure architecture, SBOM management, embedded CAN, Ethernet and RF intrusion detection, secure OTA, V2X and fleet-level security monitoring.

Read original

It is the clearest example of Saket Mohan connecting a specific attack to a lifecycle security argument.

Saket Mohan describes reports that a Bluetooth-enabled battery-management-system app was misused to remotely disable e-rickshaws by interfering with battery discharge controls, prompting the Indian government to ask Google and Apple to remove the BAT-BMS app.

• They argue app removal is an emergency brake, not a long-term cybersecurity strategy; the real fix starts earlier with secure-by-design development, supply-chain visibility across BMS, apps, firmware and connected components, basic authentication, cryptography and access control, standards such as ISO/SAE 21434 and AIS 189/190, continuous telemetry and IDS monitoring, dynamic risk assessment and incident-response playbooks.
• Secure Elements India reviewed the app behaviour and carried out its own assessment, but withholds technical details for responsible disclosure.
• The reported impact was disabling the battery system; the post asks what might happen if the same weakness affected charging, thermal controls or another safety-critical function.

For brands planning a campaign

For an automotive cybersecurity vendor targeting EV and SDV manufacturers, this is a ready-made thought-leadership anchor: use the BAT-BMS incident to argue that battery-system security must be designed into procurement, architecture, validation and post-production monitoring—not handled through app-store takedowns. It supports a campaign on securing connected vehicle battery systems against Bluetooth-based attacks, with specific hooks around TARA, embedded IDS, supply-chain visibility and incident response.

It introduces the product vocabulary—IDS, MSOC, OTA and UNECE rules—that recurs across their work.

Saket Mohan announces that eSyncSynapse will be unveiled at Future Mobility Media CAEVExpo 2026 Bangalore through a collaboration with Excelfore Corporation.

• They argue that software-defined vehicles need more than OTA delivery: they need continuous intelligence, risk-aware decision-making and a closed-loop cybersecurity architecture across the vehicle lifecycle. eSyncSynapse combines CRISKLE IDS, CRISKLE MSOC, UNECE R155/R156 and eSync OTA to connect detection, analysis, decision and secure deployment at fleet scale.
• They frame this as a shift from reactive updates to intelligent, risk-governed orchestration of vehicle software, and thank Shrikant Acharya, Shrinath Acharya and Rituraj Shrivastava for guidance.

For brands planning a campaign

This gives vendors a concrete, product-led angle for SDV thought leadership: explain why OTA alone is insufficient and show how intrusion detection, security operations and regulatory compliance feed a closed loop from detection to deployment. It can support campaigns for OEMs and Tier 1 suppliers evaluating fleet-scale software security.

It connects cybersecurity engineering with compliance evidence and post-market monitoring.

Saket Mohan presents CRISKLE Workspace for EU Cyber Resilience Act compliance, noting that CRA reporting obligations begin on 11 September 2026.

• They say manufacturers need a practical way to connect product security engineering with risk assessment, SBOM, vulnerability management, PSIRT, compliance evidence and post-market monitoring.
• They position the workspace as a way for organisations to move from interpreting regulation to operationalising compliance across the product lifecycle, and invite readers to register interest.

For brands planning a campaign

For a cybersecurity vendor, this supports compliance-focused content for manufacturers selling into Europe: connect automotive product security work to CRA obligations, SBOM, PSIRT and post-market monitoring. It is a useful secondary angle for audiences that include regulated connected-product makers, not just vehicle OEMs.

It gives context on the UK-India partnership behind Secure Elements' Bengaluru presence.

Saket Mohan marks the UK-India Comprehensive Economic and Trade Agreement entering into force on 15 July 2026.

• They say CETA creates a platform for UK automotive SMEs to supply software, engineering and R&D services, deploy specialists between both markets and develop technology partnerships in India.
• They describe India as entering a defining phase in electric, connected and software-defined mobility, with cybersecurity engineered across the lifecycle: TARA, secure architecture, SBOM management, embedded CAN, Ethernet and RF intrusion detection, secure OTA, V2X, and fleet-level security monitoring and operations.
• Secure Elements UK is growing its presence in Bengaluru with Secure Elements India, headed by Rituraj Shrivastava.
• They argue CETA opens the door, but results require local investment, trusted partnerships, regulatory alignment, IP protection and long-term commitment.

For brands planning a campaign

This offers a market-entry and partnership angle: use the UK-India CETA moment to discuss how automotive cybersecurity SMEs can combine UK innovation with Indian engineering talent, manufacturing scale and mobility growth. It can support content for UK or Indian OEMs, Tier 1 suppliers and research partners considering cross-border security programmes.

They say the government asked Google and Apple to remove the BAT-BMS app, then argue that app removal is an emergency brake, not a cybersecurity strategy.

• The post recommends secure-by-design development; supply-chain visibility across BMS, apps, firmware and connected components; basic authentication, cryptography and access control; standards such as ISO/SAE 21434 and AIS 189/190; continuous monitoring of telemetry, IDS events, BOMs and vulnerabilities; dynamic risk assessments; and incident-response playbooks.
• They argue that the real fix starts earlier—with procurement, architecture, development, validation, supply-chain onboarding and post-production monitoring.

Incident-led analysis: starts with a reported attack, says Secure Elements India reviewed the app behaviour and conducted its own assessment, and withholds technical details for responsible disclosure.

The reported impact was limited to disabling the battery system; the post does not claim a broader safety compromise.

For brands planning a campaign

For vendors targeting EV and SDV manufacturers, this offers a timely example for thought leadership on battery-system security. The angle can move from Bluetooth BMS app misuse to procurement, secure-by-design requirements, supply-chain visibility and post-market monitoring—practical buying concerns for battery and vehicle manufacturers.

Examples: Source 1

The post says manufacturers need a practical way to connect product security engineering with risk assessment, SBOM, vulnerability management, PSIRT, compliance evidence and post-market monitoring. It presents the product as a way to move from interpreting regulation to operationalising compliance across the product lifecycle.

Regulation-to-practice framing: names the compliance deadline, connects the engineering and documentation functions involved, and offers a product registration link.

For brands planning a campaign

A cybersecurity vendor can use this as a template for content that turns a regulation deadline into an operational checklist. The strongest angle is how automotive and connected-product teams bring SBOM, vulnerability management, PSIRT and post-market documentation together in one lifecycle process—not simply what the CRA says.

Examples: Source 1

The post argues that software-defined vehicles need more than OTA delivery: they require continuous intelligence, risk-aware decision-making and a closed-loop cybersecurity architecture across the vehicle lifecycle. It describes eSyncSynapse as combining CRISKLE IDS, CRISKLE MSOC, UNECE R155 and R156, and eSyncOTA in a real-time loop linking detection, analysis, decision and secure deployment at fleet scale.

Product-launch explanation: names the component parts and traces the loop from detection to secure deployment, presenting it as a shift from reactive updates to risk-governed orchestration.

This is an announcement post, with no deployment results, customer outcomes or independent validation.

For brands planning a campaign

A brand can position itself around lifecycle security orchestration rather than point OTA updates. The campaign could contrast reactive patching with detection, analysis, decision and secure deployment at fleet scale, using the named standards and product components to demonstrate domain focus.

Examples: Source 1

For Secure Elements UK, it creates a platform for UK automotive SMEs to supply software, engineering and R&D services, deploy specialists between the two markets and develop technology partnerships in India. The post describes India entering a new phase in electric, connected and software-defined mobility, and argues that cybersecurity must be engineered across the lifecycle: TARA, secure architecture, SBOM management, embedded CAN, Ethernet and RF intrusion detection, secure OTA, V2X, and fleet-level security monitoring and operations.

Trade-policy context and a market-entry argument: uses the CETA milestone to outline what UK automotive SMEs need to do in India, including local investment, trusted partnerships, regulatory alignment, IP protection and long-term commitment.

Mohan says the agreement alone will not create business; the post focuses on preparation and execution, not an immediate commercial result.

For brands planning a campaign

For vendors targeting EV and SDV manufacturers, this supports content on cross-border engineering and market entry. A campaign can focus on what UK and Indian automotive teams need to align: lifecycle security, local partnerships, regulatory alignment and IP protection.

Examples: Source 1

They link this to secure-by-design product development, supply-chain visibility, authentication and cryptography, continuous monitoring, dynamic risk assessment and incident-response playbooks. The posts also name standards and regulations, including ISO/SAE 21434, AIS 189/190, UNECE R155 and R156, and the EU Cyber Resilience Act.

Consistent standards-to-practice translation: each post takes a regulation, incident or product launch and maps it to lifecycle stages such as architecture, procurement, validation, deployment and post-market monitoring.

The posts name standards and regulations but offer no clause-level implementation guidance or step-by-step compliance walkthrough.

For brands planning a campaign

A brand can build a content series translating standards into automotive cybersecurity practice. The practical hook is lifecycle coverage: what procurement, engineering, validation, supply-chain and operations teams each need to do, rather than a general case for security.

Examples: Source 1 · Source 2 · Source 3 · Source 4

They target industry readers and often cover concrete technical categories such as BMS apps, SBOM, PSIRT, IDS, MSOC and secure OTA.

Short-form thought leadership pairs a news hook with a practical list and a commercial close.

The LinkedIn posts are short-form. Ask for case studies, technical walkthroughs or video transcripts if those formats matter.

For brands planning a campaign

A brand should expect a collaborative format built around a timely hook, a practical framework and named ecosystem partners. For battery security, a natural fit is a short, incident-led post that moves from the Bluetooth BMS attack to procurement and lifecycle controls, then presents the vendor's own assessment or tooling as the next step.

Examples: Source 1 · Source 2 · Source 3 · Source 4

The posts describe the company’s work on vehicle intrusion detection, secure OTA, and EU Cyber Resilience Act compliance. Their title and ownership stake aren’t stated; ask them to clarify their role.

View example

Ask for the commercial terms and duration.

View example

The two posts here explain why automotive cybersecurity has become as critical as functional safety, how ISO/SAE 21434 builds security into product development, and how static analysis, dynamic analysis, fuzz testing and penetration testing fit across the embedded lifecycle. Readers who follow Mohan for lifecycle security commentary will find Camacho covering the adjacent verification side of the same problem.

Camacho's posts centre on software verification and testing: how teams find, prioritise and fix defects in embedded code, including through static analysis, secure coding and structural coverage.

• Mohan's posts focus on vehicle-level security operations, translating regulation into compliance and monitoring workflows, and on cross-border partnerships.
• Follow Camacho for testing methodology; follow Mohan for lifecycle governance, detection and security operations.

Read original · Original 2

Like Mohan, Bhatt uses a timely hook, a short, structured list of points and a plain conclusion aimed at industrial decision-makers in India.

Bhatt focuses on market growth, visibility and demand systems for manufacturing SMEs, not security engineering. Follow Bhatt for insight into how Indian manufacturers sell and scale; follow Mohan to learn how the connected and electric products they build are secured.

Read original · Original 2

The overlap in cybersecurity, India and connected technology makes Robbins a plausible next follow for the same reader.

Robbins writes as the leader of a global technology company, describing customer visits, government meetings and market commitments in the first person.

• The posts offer market and partnership context rather than explanations of standards, engineering practice or controls.
• Follow Robbins for company-level context on cybersecurity and India technology; follow Mohan for how connected-vehicle security is engineered and operationalised.

Read original · Original 2

The testing framework gives technical audiences concrete practices to discuss, while Saket Mohan’s e-rickshaw post is the closer fit for a campaign about battery-system risk and product-lifecycle controls.

For a campaign focused on vehicle software security verification, Ricardo Camacho offers a broader engineering perspective than Saket Mohan’s e-rickshaw incident post.

• Camacho connects connected-vehicle risks with ISO/SAE 21434, secure coding and software verification, then breaks embedded security testing into static analysis, dynamic analysis, fuzzing and penetration testing.
• This is a better fit for explaining testing practices, but less directly tied to battery-management systems or a specific Bluetooth attack.

Examples: Source 1 · Source 2