AssurIQ
Fix Center

A successful technical action is not the end.

AssurIQ connects remediation to authorization, execution context, fresh validation and evidence. Windows endpoint execution is entering pilot validation; the workflow never presents a staged action as already operational.

Explore Endpoint OperationsRequest an RMM Pilot
Remediation Center · Northline MSP portfolioSorted by AssurIQ Risk, not CVSS
  • critical
    Patch KEV vulnerability on edge firewall
    Summit Ridge Ford · affects 3 controls
  • high
    Enforce MFA on 2 privileged M365 accounts
    Brightpath Dental · affects 2 controls
  • medium
    Move camera cam-lot-03 back to IoT VLAN
    Summit Ridge Ford · affects 1 control
  • medium
    Replace 3 unsupported Windows endpoints
    Brightpath Dental · affects 1 control
The target workflow re-checks the control after a fix and preserves the fresh result. Endpoint automation remains in pilot.
How it works

Detect → Precheck → Approve → Execute → Validate → Document

01
Detect

Create work from an endpoint, infrastructure or security signal.

02
Precheck

Confirm scope, dependencies, exposure and validation criteria.

03
Approve

Apply the required role, policy and maintenance boundary.

04
Execute

Run through a supported integration or the Windows pilot agent.

05
Validate

Collect a fresh observation and compare the intended state.

06
Document

Preserve the action, result and control evidence in history.

Prioritization

A queue that already knows the blast radius.

Because every item points at the same asset, finding and control records as the rest of the platform, the queue can say “this one firmware update clears three controls across two frameworks” without anyone doing the mapping by hand.

  • Connected impact: controls, frameworks and downstream assets
  • Portfolio view for MSPs, single-customer view for internal teams
  • Quick wins surfaced when one fix clears several controls
How AssurIQ Risk is calculated
Finding · CVE on fw-edge-01 · Summit Ridge FordcriticalAssurIQ Risk 94
Why this ranks first
  • CVSS base9.8
  • EPSS0.94
  • Known exploited (KEV)Yes
  • ExposureInternet-facing
  • Asset criticalityEdge firewall
  • Compensating controlNone
  • Age11 days
Connected impact
  • 3 controls affected — AIQ-NET-011, AIQ-VUL-001, AIQ-NET-014 move to FAIL
  • Frameworks — FTC Safeguards, NIST CSF 2.0, Cyber Insurance Baseline
  • Blast radius — every VLAN behind the edge, incl. F&I workstations
  • Remediation — firmware update queued · validation rescan on completion
Validation

Closed should mean verified, not ticked.

A ticket marked done is a claim. A control re-evaluated from fresh evidence is proof. AssurIQ records the second and shows it in the control's history.

  • Fresh observations provide the validation signal
  • Validated outcomes write new evidence to history
  • Automated endpoint rechecks and regression handling remain in pilot
Evidence Vault and history
Evidence Vault · AIQ-END-004 · historyAppend-only · nothing overwritten
  1. Aug 04Evidence GapNo evidence on file
    Control created from HIPAA pack mapping
  2. Aug 06PartialCollector · endpoint census
    3 of 41 workstations still on unsupported OS
  3. Aug 19PartialManual upload · lifecycle plan
    Replacement schedule attached, exception requested
  4. Aug 27PassCollector · endpoint census
    All endpoints on supported OS · confidence 94
Provenance
Collector · connector · manual
Integrity
Hashed, timestamped
Maps to
HIPAA · NIST CSF · Insurance
Capabilities

Built for the people who do the work.

Work queues

Portfolio, customer and technician views with filters by severity, control, framework and age. Bulk actions for common fixes.

Ticketing & operational integration

Route context into configured PSA or operational providers. Remote-support and general endpoint job connectors are in development.

Validation & re-verification

Fresh evidence after completion is the target workflow. Automated endpoint validation remains part of the Windows pilot.

Playbooks

Step-by-step remediation guidance per finding type, from firewall firmware to privileged MFA to VLAN correction, with validation criteria included.

Incident workflows

When a finding becomes an incident, a structured record with timeline, containment steps and post-incident review — leaving legal notification decisions to your counsel.

Approved automation · pilot

PowerShell scripts, scheduling, results and offline retry are designed for authorization and auditability; general execution is not broadly released.

Evidence after action

A validated result can update control state and preserve who approved the change, what ran and what the follow-up observation proved.
Outcomes

What changes when remediation is connected.

  • Technicians stop guessing which of 400 findings matters this week
  • Compliance analysts see evidence gaps close as fixes validate
  • Executives see remediation trend against Security Risk and Assurance separately
  • Assessors see the regression, the fix and the proof — in order
Keep exploring

Vulnerability & Risk

Where priority comes from
Learn more

Continuous Assurance

Controls that stay verified
Learn more

For MSPs

Portfolio-wide queues and roles
Learn more

Demo environment

Try the remediation storyline
Learn more
Next step

Bring validation into every remediation workflow.

Explore the connected Fix Center, or discuss a controlled Windows endpoint pilot with the AssurIQ team.

See the PlatformRequest an RMM Pilot