> ## Documentation Index
> Fetch the complete documentation index at: https://docs.corgea.app/llms.txt
> Use this file to discover all available pages before exploring further.

# SLA Management

> Configure and manage Service Level Agreements (SLAs) for security issues

<Info>
  The SLA Management feature allows users to define Service Level Agreements (SLAs) for security issues based on their urgency levels. It helps ensure that issues are addressed within specified timeframes and provides notifications when SLAs are not met.
</Info>

## Who it's For

This feature is primarily designed for project managers, security teams, and developers who need to manage and prioritize security issues effectively.

## Key Features and Benefits

<Check>
  * Define SLAs with customizable remediation and escalation timeframes for different urgency levels (e.g., Critical, High, Medium, Low)
  * Receive notifications (email or Slack) when issues are approaching or exceeding their SLA deadlines
  * Track issue aging and SLA compliance through a dedicated reporting page
  * Improve accountability and response times for addressing security vulnerabilities
  * Enhance collaboration and communication between teams by aligning on SLA expectations
</Check>

## How to Access

<Note>
  The SLA Management feature is accessible through the "Policies" section of the application. Users with the appropriate permissions can navigate to the "SLA Management" page to configure and manage SLAs.
</Note>

## Setup Instructions

<Steps>
  <Step title="Navigate to Policies">
    Log in to the application and navigate to the "Policies" section
  </Step>

  <Step title="Access SLA Management">
    Click on the "SLA Management" tab or link

    <Frame>
      <img src="https://mintcdn.com/corgea/mpJUc1GyXtnVYEyT/images/sla_management_nav.png?fit=max&auto=format&n=mpJUc1GyXtnVYEyT&q=85&s=97d0df34a7913973b46cea1e2e2b06e1" style={{ borderRadius: '0.5rem' }} width="1686" height="860" data-path="images/sla_management_nav.png" />
    </Frame>
  </Step>

  <Step title="Create New SLA">
    Click the "Create Issue SLA" button to set up a new SLA

    <Frame>
      <img src="https://mintcdn.com/corgea/mpJUc1GyXtnVYEyT/images/sla_create.png?fit=max&auto=format&n=mpJUc1GyXtnVYEyT&q=85&s=220ac06458baf6fce1b1c277437cd5b4" style={{ borderRadius: '0.5rem' }} width="1554" height="1852" data-path="images/sla_create.png" />
    </Frame>
  </Step>

  <Step title="Configure Urgency Levels">
    In the SLA creation modal, select the desired urgency levels (e.g., Critical, High, Medium, Low) by checking the corresponding checkboxes
  </Step>

  <Step title="Set Timeframes">
    Set the remediation and escalation timeframes (in days) for the selected urgency levels
  </Step>

  <Step title="Configure Notifications">
    Choose the notification method(s) by checking the "Email" and/or "Slack Integration" options. If selecting Slack, choose the desired integration from the dropdown.

    <Tip>
      Make sure you have configured your Slack integrations in the Integrations section before enabling Slack notifications. See the [Slack Integration Guide](slack) for setup instructions.
    </Tip>
  </Step>

  <Step title="Save Configuration">
    Click "Save SLA" to finalize the SLA configuration
  </Step>
</Steps>

## Usage Guide

### Viewing and Managing SLAs

<Info>
  * On the "SLA Management" page, you can view a list of all defined SLAs for your company
  * Use the provided actions (edit, delete) to manage existing SLAs
</Info>

### Issue Tracking and Notifications

<Info>
  * When a new security issue is created, it will be automatically associated with the appropriate SLA based on its urgency level
  * As the issue approaches its remediation and escalation deadlines, notifications will be sent to the configured recipients (assigned user or project owners)
  * The issue's status will be updated to reflect its SLA compliance (overdue or escalated)
  * SLA notifications are sent once a day, checking for any issues that have passed their remediation or escalation deadlines
</Info>

### Reporting and Analytics

<Info>
  * Access the dedicated "Issue Aging" reporting page for a comprehensive overview
  * Filter and sort issues based on various criteria
  * Identify trends and patterns to improve processes
</Info>

<Frame>
  <img src="https://mintcdn.com/corgea/uxLuQR4653lM43Tj/images/aging_report.png?fit=max&auto=format&n=uxLuQR4653lM43Tj&q=85&s=81b1012a84bf21c2501192bbce30c945" style={{ borderRadius: '0.5rem' }} width="3020" height="2004" data-path="images/aging_report.png" />
</Frame>

## Examples

### Setting up an SLA for Critical Issues

<Steps>
  <Step title="Create SLA">
    Create a new SLA and check the "Critical" urgency level
  </Step>

  <Step title="Set Timeframes">
    Set the remediation timeframe to 2 days and the escalation timeframe to 3 days
  </Step>

  <Step title="Configure Notifications">
    Check the "Email" option and select a Slack integration (if available)
  </Step>
</Steps>

### Tracking SLA Compliance

<Steps>
  <Step title="Access Reports">
    On the "Issue Aging" reporting page, filter the issues by the desired project
  </Step>

  <Step title="Review Issues">
    Review the list of issues, their urgency levels, and their SLA status (overdue or escalated)
  </Step>

  <Step title="Prioritize">
    Identify any overdue or escalated issues and prioritize their resolution based on the defined SLAs
  </Step>
</Steps>

## Best Practices

<Tip>
  * Regularly review and update SLAs to align with changing business priorities
  * Involve relevant stakeholders in defining SLA timeframes
  * Leverage reporting capabilities to identify areas for improvement
  * Integrate with existing issue tracking and project management tools
</Tip>

## Troubleshooting

<Warning>
  * If you encounter issues while creating or editing SLAs, ensure that you have the necessary permissions and try refreshing the page
  * If notifications are not being received, verify the configured notification methods and check for delivery failures
  * If the issue aging or SLA compliance data appears inaccurate, try refreshing the reporting page or contact support
</Warning>