K-Shield Quick Tasks

Use this page for fast execution. For the complete scanning, monitoring, VM, and compliance workflow, use K-Shield (Security).

Task 1: Run First Node Security Scan (5-10 Minutes)

When to Use:

Use this when a node has not yet been baselined.

Purpose:

Establish the first node-level security baseline and populate findings.

Steps:

  1. Open K-Shield -> Dashboard.

  2. Select Node level.

  3. Open a reachable managed node.

  4. Click Start Security Scan and choose the approved security profile.

  5. Wait for completion and refresh if needed.

Expected Outcome:

  • Scan status is COMPLETED.

  • Compliance score and CAT findings are visible on the managed-node page.

If this fails:

  1. Verify the node is reachable in the left panel.

  2. Confirm your role has scan permission.

  3. Retry once after refreshing the page.

  4. If still failing, collect node name/time and escalate via support@karios.com.

Task 2: Triage Findings in Correct Order (5-10 Minutes)

When to Use:

Use this immediately after a completed scan.

Purpose:

Prioritize remediation in the correct severity order.

Steps:

  1. Review CAT I findings first.

  2. Review CAT II findings next.

  3. Review compliance trend and total open findings.

  4. Open one critical/high finding and capture remediation details.

Expected Outcome:

  • Priority queue is documented.

  • One remediation action owner and timeline is assigned.

If this fails:

  1. Confirm scan data is refreshed and current.

  2. Re-open the managed-node Overview or Compliance tab and verify severity counts.

  3. If findings are missing, run one more scan and re-check.

Task 3: Verify Remediation (3-8 Minutes)

When to Use:

Use this after applying a remediation change.

Purpose:

Validate that the applied fix reduced risk.

Steps:

  1. Apply approved remediation change.

  2. Re-run the scan on the same managed node or VM.

  3. Compare findings and score with prior run.

Expected Outcome:

  • Target finding count decreases or severity is reduced.

  • Evidence (timestamps, IDs, results) is recorded.

If this fails:

  1. Confirm remediation was applied to the same target that was scanned.

  2. Review recommendation prerequisites and re-apply if needed.

  3. Re-scan and compare by scan ID/time.

  4. Escalate unresolved critical findings through your internal chain.

Task 4: Security Escalation Path (2-3 Minutes)

When to Use:

Use this for critical findings, repeated failures, or blocked remediation.

Purpose:

Route incidents to the correct internal and platform escalation paths.

Steps:

  1. Use your customer internal chain for governance approvals.

  2. Use support@karios.com for Karios platform/vendor escalation.

  3. Include target ID, scan timestamp, severity summary, and impact scope.

Expected Outcome:

  • Escalation owner is clear.

  • Required incident details are shared in the first message.

If this fails:

  1. Re-send with complete details: target, scan ID, timestamp, severity, impact.

  2. Confirm the internal on-call/escalation owner is notified.

  3. Track follow-up in your incident record.

Escalate immediately when:

  • CAT I findings affect production-critical assets

  • Compliance drops below your approved policy threshold

  • Scan repeatedly fails after one controlled retry