Skip to main content

Incident Response Security

Harness Incident Response (IR) includes security measures to protect incident data, ensuring confidentiality, integrity, and availability. It integrates with the Harness Platform’s security features, including authentication, role-based access control (RBAC), audit trails, and secret management.

Security measures include:

  • Data encryption in transit (TLS 1.3) and at rest (AES 256)
  • Role-based access controls to restrict incident data
  • Secure API authentication for third-party integrations
  • Audit logging for compliance tracking

Security Measures​

Harness IR ensures incident security by restricting access, encrypting data, and logging all activities.

  • Access Management: Supports authentication via SAML, OAuth, and API tokens.
  • Data Protection: Encrypts incident metadata, logs, and communication history.
  • Automation & Runbook Security: Ensures that only authorized users execute automated actions.
  • Audit & Compliance: Logs every action for tracking and compliance reviews.

Security Components​

Incident Data Storage​

Incident data, logs, and automation history are securely stored.

  • Data is encrypted and retained per organization policies.
  • Access is controlled through RBAC.
Data Retention

Harness IR retains incident logs and history based on your organization’s settings.

Operational Security​

Harness IR ensures security at every stage:

  1. Incident Creation & Logging

    • Incidents are created through authenticated sources (UI, API, webhooks).
    • Data is encrypted before storage.

  2. Access & Role Management

    • RBAC controls who can access incidents.
    • Authentication via OAuth/SAML is required.

  3. Automation Execution

    • Actions are logged for compliance.
    • Only approved integrations execute via Harness Delegates.

  4. Audit & Compliance Logging

    • Every action is recorded for compliance audits.
    • Logs can be exported for security reviews.

  5. Third-Party Integration Security

    • OAuth tokens, API keys, and access scopes protect integrations.
    • Secure connections use TLS 1.3 encryption.

Best Practices​

To enhance security in Harness IR:

  • Use RBAC policies to limit access.
  • Enable OAuth/SAML authentication.
  • Review audit logs regularly.
  • Use API tokens with least privilege.
  • Encrypt webhook notifications.