Security Operations
Orchestration
❓

🎯 Orchestration & Automation

Enterprise-grade remediation orchestration, verification and automation capabilities.

🎯 Remediation Command Centre

The Remediation Command Centre (Command Centre > Remediation Centre) provides a unified real-time view of all remediation activity across your environment.

  • Active Remediations β€” actions currently executing or pending
  • Awaiting Approval β€” actions requiring administrator approval
  • Completed (24h) β€” successful remediations in the last 24 hours
  • Failed (24h) β€” failed remediations requiring attention
  • Automation Rate β€” percentage of remediations handled by automation
  • Avg Remediation Time β€” mean time to remediate
  • Verification Engine β€” post-remediation verification pass/fail rates
  • Rollback Engine β€” rollback success rates and history

Every metric is computed from real data in the database β€” nothing is static or hardcoded.

⚑ Fix Everything

Fix Everything (Command Centre > Fix Everything) analyses all open issues and categorises them:

  • Auto-Remediable β€” safe issues ProPera can fix automatically (low-risk config drift, medium/low vulnerabilities, low-severity incidents)
  • Requires Approval β€” issues needing administrator authorisation before remediation
  • Needs Investigation β€” complex issues requiring human analysis
  • Blocked by Policy β€” issues blocked by automation policies

Dry Run previews what would happen without making changes. Fix All Safe Issues creates RemediationRecords for every auto-fixable issue with full audit trail.

ProPera never automatically fixes Critical-severity issues or high-risk assets without explicit approval.

βœ… Verification Engine

The Verification Engine ensures remediations actually solved the original problem. After a remediation completes, ProPera runs verification checks:

  • Version Check β€” for patches: verifies installed version matches target
  • Service Health β€” verifies endpoint sensor is active and healthy
  • Vulnerability Rescan β€” re-checks vulnerability status after remediation
  • Configuration Check β€” verifies configuration state changed as expected

Each check records expected vs actual state with full evidence. ProPera never marks an issue as resolved simply because a command executed successfully.

Verification results link to RemediationRecords and are available in the Evidence Vault.

πŸ“¦ Evidence Vault

The Evidence Vault (Command Centre > Evidence Vault) generates audit evidence packages for compliance frameworks:

  • Supports CIS, ISO 27001, NIST, SOC 2, PCI DSS, NZISM, and internal frameworks
  • Packages bundle: evidence items, remediation records, verification results, audit log entries
  • Each package has a SHA-256 checksum for tamper-evidence
  • Filter by framework, date range, or asset

Every automated action in ProPera records before/after state, and the Evidence Vault packages this into audit-ready evidence.

πŸ“‹ Playbooks (Automation Studio)

Playbooks (Command Centre > Playbooks) are version-controlled automation workflows:

  • Create playbooks with triggers, conditions, and steps
  • Version control: every change creates a new version with change notes
  • Draft β†’ Published lifecycle
  • Trust Score: computed from historical success rate, failure rate, rollback rate, and recency of failures
  • Minimum trust thresholds: auto-execute only if trust score meets minimum
  • Dry-run mode for safe testing
  • Approval gates for high-risk operations

Every execution is tracked with full audit trail including trigger type, steps executed, duration, and outcome.

πŸ–₯️ Asset Digital Twin

The Asset Digital Twin (Command Centre > Asset Twin) provides a complete contextual view of each endpoint:

  • Hardware, OS, IP, sensor health, endpoint value, risk score
  • Installed applications with versions and out-of-date status
  • Open network ports and services
  • Open vulnerabilities with severity and CVSS scores
  • Dependency mapping: which assets depend on this endpoint
  • Impact analysis: what business services would be affected if this endpoint fails
  • Risk summary with identified risk factors
  • Recent remediation activity history

All data is populated dynamically from endpoint inventory, vulnerability data, and integration feeds.

πŸ“ˆ Executive Risk Score & ROI

The Executive Risk Score (Command Centre > Executive Risk) provides:

  • Enterprise Risk Score (0-100) computed from: critical/high vulnerabilities, active incidents, high-risk endpoints, unhealthy endpoints, open alerts, and failed remediations
  • Classification: LOW (0-25), MEDIUM (26-50), HIGH (51-75), CRITICAL (76-100)
  • Risk Breakdown: per-factor contribution to the score with visual bars
  • ROI Dashboard: manual hours saved, automated hours, cost savings, annual savings estimate, automation rate
  • Cost Configuration: customise hourly rate, currency, estimated task durations

All metrics are dynamically calculated from real remediation data. The ROI section shows exactly how much ProPera automation saves compared to manual remediation.

↩️ Rollback Engine

The Rollback Engine supports enterprise-grade rollback for remediation actions:

  • Supported: actions where rollback is technically possible (isolation release, incident state revert)
  • Unsupported: actions requiring manual review (account disable, quarantine, process termination)
  • Every rollback records: original state, rolled-back state, reason, actor, and timestamp
  • Rollback success rates are shown on the Command Centre dashboard

ProPera never assumes rollback is possible for every technology. The UI clearly shows rollback status: SUPPORTED, UNSUPPORTED, AVAILABLE, or FAILED.

πŸ”” Notifications & Collaboration

ProPera sends notifications to configured channels:

  • Microsoft Teams β€” rich cards with severity color coding
  • Slack β€” formatted messages with event details
  • Email β€” HTML-formatted notifications via configured SMTP
  • Webhooks β€” generic HTTP POST to any endpoint

Each channel can filter by event type (incident, remediation, compliance, etc.) and severity level. All notification attempts are tracked for delivery confirmation.

πŸ”— Dependency Mapping

ProPera maps dependencies between assets for impact analysis:

  • Hard, soft, optional, and failover dependency types
  • Business impact classification: Low, Medium, High, Critical
  • Impact analysis: when an asset fails, ProPera identifies all affected downstream assets
  • Dependencies can be manually created or discovered through scans and API integrations