Skip to main content

Detection & Response


Cases

The user can access the cases menu, which is under Detection & Response.

image.png

Case List

The Case List screen in the SmartWAN Portal, accessible under the "Detection & Response" section, provides a detailed list of cases generated by analyzing event logs. This screen allows users to view and manage security and network-related incidents efficiently.

image.png

Key Features
  • Filters and Search:
    • Customer and Asset Selection: Dropdown menus at the top (e.g., "Select a customer," "Select an asset") to filter cases by specific customers or assets.
    • Date Range: A date picker to filter cases within a specific time period (e.g., 2024/09/30 - 2024/10/30).
    • Advanced Search: A button on the right to access advanced search options for more granular filtering.
  • Case Summary:
    • Displays the total number of cases (e.g., 279 cases) and the total results (e.g., 2,193 cases) for the selected filters.
  • Case Table:
    • A table listing cases with columns such as:
      • Event Type: Type of event (e.g., Raw Packet).
      • Source Asset: Source of the event.
      • Destination Asset: Destination of the event.
      • Rule: Applied rule.
      • Source IP: Source IP address.
      • Destination Port: Destination port.
      • Time: Timestamp of the event.
      • Raw Packet: A column with a clickable icon to view raw packet details (e.g., BSX525D9252F...).
  • Notification Settings:
    • A "Notification Settings" button at the top-right corner to configure alert preferences.

The items provided in the Case List may be modified in the future based on evolving requirements.

Case Filtering

image.png

After selecting a customer, the case table updates to reflect cases specific to that customer, ensuring users can focus on relevant incidents.
Customer Selection:
  • Dropdown Menu: Displays a list of available customers (e.g., SK Telecom, Samsung Electronics, KT&G, Ericsson, Coca Cola, General Electric, BMW).
  • Action: Click the "Select a customer" dropdown to choose a customer, filtering the case list to show only cases related to the selected customer.
Multi-Tenant Support:
  • Each customer is represented, indicating secure separation of data in the multi-tenant environment.
  • The associated assets for the selected customer are displayed.

image.png

The Select an Asset dropdown on the Case List screen allows users to filter cases by specific assets. It lists assets such as "Seoul IDC LW3007," "T-Store Pangyo LW2308-4G," and "Daejeon IDC LW7009." Users can select an asset and click "Selection Confirmed" to update the case list.

image.png

The Advanced Search feature on the Case List screen allows users to refine their case search with additional filters. Accessible via the "Advanced Search" button, it includes options to select a customer, asset, severity level (e.g., Critical, High), and enter a search keyword. Users can apply these filters by clicking the "Search" button to update the case list.

Case Details

The Case Details popup in the SmartWAN Portal is displayed when a user selects a case from the Case List screen. This popup provides detailed information about the selected case, including event specifics and related events, to assist users in analyzing and managing.
  • Case Information: The default tab, showing detailed case data.
  • Case Management: A secondary tab for managing the case.
Case Information

image.png

Detailed Case Information:
  • Event Type: The type of event
  • Asset Type: The type of asset involved
  • Asset No.: The asset identifier
  • Timestamp: The date and time of the event
  • System IP: The system IP address
  • Origin Country: The country of origin
  • Origin IP: The originating IP address
  • Origin Port: The originating port
  • Destination Country: The destination country
  • Destination IP: The destination IP address (
  • Destination Port: The destination port 
  • Remote IP: The remote IP address

Case Management

The Case Management tab in the Case Details popup outlines the steps for handling a case in the SmartWAN Portal.
The procedures guide users through the process of managing a case from opening to closure. Below is a summary of the steps involved.

Case Management Procedure Table

Step Procedure Description
1 Case Open Initiates the case and assigns it to a user.
2 Initial Investigation Conducts preliminary analysis of the incident.
3 Prioritization Assigns a priority level to the case.
4 Analysis and Response Performs detailed analysis and responds to the incident.
5 Containment and Mitigation Implements measures to contain and mitigate the issue.
6 Recovery and Remediation Restores systems and applies fixes to prevent recurrence.
7 Case Closure Closes the case after resolution.
8 Post-Incident Review Reviews the incident for lessons learned.
Step 1. Case Open

image.png

Purpose: The "Case Open" step marks the beginning of the case management process. When a case is identified (e.g., a traffic-related event on a Juniper asset), it is opened in the system, and relevant details are recorded.
Details Displayed:
  • Assignee: The user assigned to handle the case (e.g., Bryan Ga).
  • Event Type: The type of event (e.g., Traffic).
  • Asset Type: The type of asset involved (e.g., Juniper).
  • Asset No.: The asset identifier (e.g., 38697).
  • Timestamp: The date and time the event occurred (e.g., 2024-09-30 10:57:59+09:00).
  • System IP: The system IP address (e.g., 1.1.1.1).
  • Severity Level: The severity of the case (e.g., Critical).
  • Threat Classification: The threat level or classification (e.g., 9)
Step 2. Initial Investigation

image.png

Purpose: The "Initial Investigation" step involves evaluating the case details and associated events to confirm whether the incident is a legitimate threat that requires further action.
Instructions Provided:
  • Evaluate the Case: Users are prompted to "Evaluate the case details and associated events to verify if it’s a legitimate threat incident and handle it accordingly."
  • Event Information Access: Users can find detailed event information for the open case and related events in the "Case Information" tab of the Case Details popup.
  • Check for Positive: Users must determine the legitimacy of the threat by selecting one of two options:
    • Confirmed as True Positive: Indicates the incident is a confirmed threat.
    • Confirmed as False Positive: Indicates the incident is not a threat (e.g., a false alarm).
Action:
  • After completing the evaluation and selecting the appropriate "Check for Positive" option, users click the "Save Step" button to record their findings and proceed to the next step in the Case Management process.
Step 3. Prioritization

image.png

Purpose: The "Prioritization" step involves evaluating the case based on its severity and impact to determine the urgency of response. This helps in allocating resources effectively and addressing high-priority incidents first.
Instructions Provided:
  • Priority Evaluation: Users are informed that "Priority is evaluated based on the severity and impact of the event."
  • Severity Level Selection: Users can select the severity level of the case from the following options:
    • Critical: For incidents with severe impact requiring immediate action.
    • High: For incidents with significant impact needing prompt attention.
    • Moderate: For incidents with moderate impact that can be addressed in a standard timeframe.
    • Low: For incidents with minimal impact that can be handled with lower urgency.
Action:
  • After selecting the appropriate severity level (e.g., Critical, High, Moderate, or Low), users click the "Save Step" button to record the prioritization and proceed to the next step in the Case Management process.
Step 4. Analysis and Response

image.png

Purpose: The "Analysis and Response" step aims to analyze the root cause of the threat, identify the affected assets and scope, and develop a response strategy to mitigate the incident.
Instructions Provided:
  • Analyze the Threat: Users are prompted to "Analyze the root cause of the threat and identify the affected assets and scope."
  • Further Analysis: If needed, users are advised to "conduct further analysis on related logs and events" to gain deeper insights into the incident.
  • Document Findings: Users are required to "describe the analysis details thoroughly in the text-area below for reporting purposes." A text editor is provided to input detailed notes, with formatting options such as bold, italic, underline, alignment, lists, links, images, and emojis.
Action:
  • Users enter their analysis details in the text area.
  • After completing the analysis and documenting the findings, users click the "Save Step" button to record their work and proceed to the next step in the Case Management process.
Step 5. Containment and Mitigation

image.png

Purpose: The "Containment and Mitigation" step aims to limit the spread and impact of the incident by isolating affected systems and applying necessary security measures.
Instructions Provided:
  • Containment Measures: Users are advised to "perform containment measures or isolate network segments to minimize impact" if the attack is ongoing.
  • Isolation and Blocking: Users are instructed to "temporarily isolate affected systems or apply security policies to block the attack, if needed."
  • Document Actions: Users are required to "describe the analysis details thoroughly in the text-area below for reporting purposes." A text editor is provided to input detailed notes, with formatting options such as bold, italic, underline, alignment, lists, links, images, and emojis.
Action:
  • Users document the containment and mitigation actions taken in the text area.
  • After completing the actions and documenting the details, users click the "Save Step" button to record their work and proceed to the next step in the Case Management process.
Step 6. Recovery and Remediation

image.png

Purpose: The "Recovery and Remediation" step aims to fully resolve the incident by addressing its root cause, restoring systems or networks to their normal operational state, and applying preventive measures to avoid recurrence.
Instructions Provided:
  • Resolve and Restore: Users are instructed to "resolve the root cause and restore systems or networks to their normal operational state."
  • Apply Security Measures: Users are advised to "apply security patches and remove malware from infected assets" to secure the environment.
  • Document Actions: Users are required to "describe the analysis details thoroughly in the text-area below for reporting purposes." A text editor is provided to input detailed notes, with formatting options such as bold, italic, underline, alignment, lists, links, images, and emojis.
Action:
  • Users document the recovery and remediation actions taken in the text area.
  • After completing the actions and documenting the details, users click the "Save Step" button to record their work and proceed to the next step in the Case Management process.
Step 7. Case Closure

image.png

Purpose: The "Case Closure" step marks the completion of the case handling process, confirming that the incident has been resolved and all necessary actions have been taken.
Instructions Provided:
  • Update Case Status: Users are instructed to "refer to the case status and use the button below to update it to ‘Closed’" once processing is complete.
  • Prepare for Next Stage: Users are informed that "during the next stage, you will be able to document the response process and outcomes, and generate the final report."
  • Document Details: Users are required to "describe the analysis details thoroughly in the text-area below for reporting purposes." A text editor is provided to input detailed notes, with formatting options such as bold, italic, underline, alignment, lists, links, images, and emojis.
Action:
  • Users document the final details of the case resolution in the text area.
  • After documenting the details, users click the "Closed" button to officially close the case and proceed to the final step in the Case Management process.
Step 8. Post-Incident Review

image.png

Purpose: The "Post-Incident Review" step aims to summarize the lessons learned from the incident response process and strengthen future security measures to better handle similar threats.
Instructions Provided:
  • Summarize Lessons Learned: Users are instructed to "summarize lessons learned from the response process and strengthen future security measures to better handle similar threats."
  • Generate Final Report: Users are advised to "document the response and outcomes, click the ‘Generate Report’ button below and complete the final report."
  • Document Details: Users are required to "describe the analysis details thoroughly in the text-area below for reporting purposes." A text editor is provided to input detailed notes, with formatting options such as bold, italic, underline, alignment, lists, links, images, and emojis.
Action:
  • Users document the lessons learned and post-incident analysis in the text area.
  • After documenting the details, users click the "Generate Report" button to compile the final report, concluding the Case Management process.
Report Generation

image.png

After completing all eight steps in the Case Management process, including the Post-Incident Review, a confirmation message is displayed in the SmartWAN Portal. 

Notification Setting 

image.png

The Alert Subscription Settings screen in the SmartWAN Portal allows users to customize how they receive notifications for cases. This screen is accessed by clicking the "Notification Settings" button on the Case List screen.
Users can configure various aspects of alert subscriptions, including the type of notifications, severity levels, assignees, recipients, and additional metadata, ensuring they are informed about relevant cases in a timely manner.
Subscription Information

image.png

Subscription Information:
  • Title: A text field to enter a custom title for the alert subscription.
    • Type: Checkboxes to select the type of notifications:
    • Notify on case opening: Sends an alert when a new case is created.
    • Notify on case progress: Sends an alert when a case’s status is updated.
  • Severity Level: Radio buttons to select the severity level of cases to be notified about.
Assignee and Recipient Management:
  • Assignee: Displays a list of users assigned to receive alerts, including:
    • Name: The assignee’s name (e.g., Bryan Ga, Timo Choi, Jay Cho, Leonardo DiCaprio).
    • Assigned Role: The role of the assignee (e.g., Administrator, Customer, Engineer).
    • Email Address: The assignee’s email (e.g., [email protected]).
    • Actions: Options to "Change Assignee" (reassign to another user) or "Remove Entry" (delete the assignee from the list).
  • Recipient: Displays a list of additional recipients for alerts, with similar details and actions as the Assignee section.
  • Add to Entry: A button to add new assignees or recipients to the subscription list.
Additional Fields
  • Additional fields can be defined by users. 
Subscription Note

image.png

The Subscription Note screen, accessible via a tab in the Alert Subscription Settings popup, allows users to add and save notes related to an alert subscription. Users can enter text in a provided text box and save the note for future reference.

Real-Time New Case Alert

The SmartWAN Portal provides real-time notifications to alert users of new cases while they are actively using the platform. This feature ensures that users are promptly informed of critical incidents, allowing for immediate action to address potential threats.

image.png