Skip to content
Kindo Kindo Docs

Use Cases

Kindo is an enterprise platform that professionals in DevOps, SecOps, and ITOps use to create autonomous infrastructure — infrastructure that helps manage and secure itself using natural language instructions. Kindo agents are typically deployed across three categories of use cases.

Incident Response

Incident Response refers to use cases where Kindo agents serve as first responders to changes in the security, reliability, or uptime of infrastructure.

Security Incident Response

For Enterprise Security teams, these use cases typically fall under Managed Detection and Response (MDR) or Incident Detection and Response (IDR). Examples include:

  • Analyzing threat intelligence feeds against failed login alerts in a SIEM to identify potential attacker C2 infrastructure.
  • Querying logging infrastructure to determine exposure from compromised credentials across databases and secrets management systems.
  • Reviewing indicators of compromise against threat intelligence and correlating with root cause analysis to determine evidence of malicious activity.

DevOps / Platform Engineering Incident Response

For DevOps and Platform Engineering teams, Incident Response typically involves Root Cause Analysis (RCA) of outages, service interruptions, or quality of service changes. Examples include:

  • Analyzing logging infrastructure and observability suites for activity preceding an outage, then performing RCA using system configuration context.
  • Analyzing firewall configs, load balancer settings, and routing logs to determine causes of network performance degradation.
  • Cross-referencing internal analysis with outage maps from telcos and cloud providers to identify macro system failures.

Vulnerability and Compliance Enforcement

Kindo agents proactively review systems for faults, vulnerabilities, and change management issues to prevent incidents before they occur.

Security Vulnerability and Compliance

For Enterprise Security teams, this involves continually reviewing system changes and IAM infrastructure for exploitable vulnerabilities or compliance violations. Examples include:

  • Reviewing IAM policies against GDPR guidelines to verify least privilege is maintained per GRC requirements.
  • Scanning public-facing infrastructure for exposed services, cross-referencing versions with known CVEs, and generating proof-of-concept exploits for critical findings.

DevOps / Platform Engineering Compliance

For DevOps and Platform Engineering teams, this involves reviewing change management procedures and infrastructure changes for potential faults. Examples include:

  • Reviewing system or IAM profile changes to determine if they may cause instability, and reporting results via email.
  • Cross-referencing Infrastructure as Code changes with PCI-DSS compliance requirements.

ITOps Automation

ITOps Automation use cases focus on removing time-consuming service offering tasks from ITOps professionals. Examples include:

  • Providing a helpdesk chatbot for answering questions about IT policies and filing tickets.
  • Automatically provisioning development environments for new users when tickets are created.