Mohnish Shende
[01]Work[02]Research[03]Investigations[04]Writing[05]About[06]CV[07]Connect

Work

Public engineering output: a sanitized infrastructure case study, a substantive assurance repository, a working security-tooling prototype, and a bounded methodology note.

Sanitized case study

NodeZero

A public-safe account of documenting and assessing a self-hosted Linux environment across service boundaries, security posture, and recovery readiness.

Infrastructure engineering

Substantive v1 repository

ECI EVM Engineering Assurance

A structured review of public evidence concerning the Election Commission of India EVM ecosystem, organized around traceable claims, exclusions, and validation boundaries.

Assurance and evidence

Working prototype

nmap-llm

An offline workflow for Nmap planning, execution, XML parsing, and local-LLM-assisted triage reporting.

Security toolingPython working prototype

Methodology note

Bounded OSINT reconnaissance

A deliberately limited account of passive and semi-passive reconnaissance, evidence classification, severity writing, and positive-control reporting.

Source material withheldPublic-safe methodology

Every entry states what the material can and cannot support. Raw audits, live-target reconnaissance, and sensitive source material stay out of the public record by design.

Read about the practice →

Mohnish Shende

Cybersecurity and infrastructure engineer. Nagpur, India.

  • Work
  • Research
  • Investigations
  • Writing
  • About
  • CV
  • Connect

Professional email: mohnish@mohnish.ink

Evidence-led analytical practice. Claims are reported at the level the material supports; boundaries and exclusions are part of the record.

mohnish.ink — evidence · traceability · bounded conclusions