KAVACH vs pytm

KAVACH is an automotive cybersecurity engineering workspace connecting vehicle architecture to traceable cybersecurity evidence across ISO/SAE 21434 workflows. Its TARA process links assets, damage and threat scenarios, attack paths, risk assessment and treatment, security goals, controls, and evidence. The workspace includes architecture context, attack-tree editing, a traceability hub, vulnerability monitoring, a cybersecurity case, an R155 compliance matrix, and report generation. SBOM and vulnerability signals can connect affected components with assets, threats, and treatment decisions. The current release focuses on ISO/SAE 21434 Clauses 5–15, UNECE R155/R156 evidence, AIS 189/AIS 190 readiness, and post-production monitoring. Deployment choices are a customer-controlled desktop workspace, on-premise deployment, or a customer-dedicated EU cloud VPC. Manual engineering, deterministic automation, and optional private AI are available. Generated work products are structured drafts requiring engineer review and customer approval. Pricing is scoped per programme.

pytm is a free, open-source Python framework for creating threat models from architectural descriptions. A model is defined in Python with elements such as servers, data stores, actors, processes, data flows, and trust boundaries. From it, pytm can generate data flow diagrams, sequence diagrams, and relevant threats. Templates can produce reports with diagrams and findings, and a RevealMD template can create slides for browser presentation. Data flow diagrams use Graphviz DOT, while sequence diagrams use PlantUML. Models can be imported from JSON with pytm's Python load function. Users can supply a custom threats file and change finding attributes such as CVSS score, response text, and severity. Requirements include Python 3.11 or later, Graphviz, Java OpenJDK 10 or 11, and plantuml.jar; Linux and macOS are listed, while Windows use is documented through Devbox in WSL. The project also documents container and Devbox dependency workflows. The README warns that strings in threats.json are evaluated with eval(), so the file's permissions need protection against unauthorized changes.