Back to workspace
AXORIK Help Center
Learn by outcome

What do you want to accomplish?

Find a workflow, understand live evidence or learn the safest next step. Search by the job you need to complete, not only by a feature name.

Understand 7 minute read Lesson 11 of 19

Use Security

Review configuration posture, verified controls, exposure and supported remediation.

Network ownerIT teamMSP
Complete this lesson, then continue through the system0 of 19 completed

Outcome

Prioritize real security gaps instead of treating every observation as equal risk.

Where to find it

Main navigation > Security

Start here

Complete guide to Use Security

When you do this

Use Security during a posture review, after AXORIK reports a security finding or before proving that required network controls are present.

What this means

Security combines verified configuration controls, important events and actionable gaps. It separates a missing or degraded control from informational activity so the response matches the actual risk.

Before you start

  • Select the correct site and confirm monitoring and security analysis are current.
  • Know which networks contain staff, guests, IoT, cameras and management devices.
  • Have approval before changing firewall, isolation or access policies.

Do this step by step

  1. 1Read Security posture to see verified, degraded and missing controls.
  2. 2Open Needs attention before informational observations.
  3. 3Read each Security finding for the affected device, network, policy and practical risk.
  4. 4Use Security events for time and activity context without treating volume alone as severity.
  5. 5Open Supported remediation only when the scope and impact are understood.

How to know it worked

The finding shows a verified resolution or a documented accepted risk, and the affected control is rechecked with current evidence.

If it does not work

  • If a control is Unknown, refresh the evidence or verify that the connected controller exposes the required data.
  • If events appear without a finding, they may be contextual observations rather than a configuration failure.
  • If remediation is unavailable, follow the manual guidance or escalate to an authorized operator.

Important

A green device state does not prove security posture, and a stale security check is not a pass.

What you will see on this page

These are the exact AXORIK sections to look for. Read them in the order shown unless the complete guide directs you to a specific finding.

1

Security posture

Summarizes verified, degraded and missing network controls.

2

Security findings

Explains the affected device, network or policy and the practical risk.

3

Security events

Shows analyzed activity and important event context when evidence is available.

4

Supported remediation

Opens a reviewed change with scope, safeguards and verification.

Recommended workflow

Follow these steps in order. If a step is blocked, resolve it before moving to the next one.

1

Check evidence freshness

Confirm that monitoring and security analysis are current.

2

Start with needs attention

Open verified gaps before informational observations.

3

Confirm scope

Read the affected segment, device, policy and latest evidence.

4

Choose the smallest response

Use a supported fix that reduces risk without unrelated change.

Safety and interpretation

  • A stale security check is not a pass.
  • Event volume alone does not measure risk.
  • Review impact before remediation.

AXORIK Essentials lesson 11 of 19

Can you now explain when and why to use this feature?

Mark it complete only when you know where to find it, what its main sections mean and what the safe next step is.