Microsoft Entra ID
Directory, sign-in, MFA, Conditional Access, and identity-risk evidence
Integrations
VitalSec connects identity, endpoint, network, backup, analytics, exposure, healthcare, insurance, and governance tools so the evidence, approved actions, follow-up checks, and proof stay connected.
What each integration does
Observe → Decide → Act → Validate → Prove → Measure
Each integration does one or more practical jobs: read evidence from the source, carry an approved action, check what changed, or send verified evidence to another workflow.
How integrations work
Read from the source
Pull evidence from the system that owns it and keep its source, scope, time, and identity attached.
Carry out approved action
Send approved changes into endpoint, identity, network, remediation, and orchestration systems.
Check the result
Read the relevant system again and use CAAT where appropriate to test whether the expected condition now holds.
Reuse the evidence
Send verified evidence into underwriting, claims, governance, reporting, and portfolio workflows.
Example source families
Bring directory, MFA, privilege, application, consent, authentication, and managed-device evidence into VitalSec while keeping each fact tied to the system that actually owns it.
Use identity and device evidence to see what changed, make supported customer-approved changes, check the result, and keep the evidence tied to its source.
Directory, sign-in, MFA, Conditional Access, and identity-risk evidence
Managed-device inventory, compliance, configuration, and remediation state
Workspace directory, authentication, MFA, admin, and application-access evidence
SSO, MFA, lifecycle, application-assignment, and sign-in evidence
MFA enrollment, authentication, device-trust, and access-policy evidence
Directory, device, authentication, policy, and access-control context
Cloud identity, authentication, MFA, and access-policy evidence
Federated authentication, SSO, token, and policy-decision context
Workforce SSO, MFA, directory, and application-access evidence
Customer identity, authentication, MFA, application, and login-event evidence
Healthcare workforce identity, clinical access, authentication, and session context
Privileged account, vault, session, credential, and access-control evidence
Privileged access, endpoint privilege, session, and credential-management evidence
Identity governance, entitlement, certification, and lifecycle evidence
Identity governance, entitlement risk, access review, and lifecycle context
Connect endpoint evidence, detections, containment, remediation, and follow-up readback so VitalSec can move from a signal to a verified result.
Endpoint integrations let VitalSec read device state and, where the customer has approved it, make supported changes and check the device again afterward.
Endpoint detections, host telemetry, containment, and response evidence
Endpoint/XDR detections, automated containment, remediation, and host context
Endpoint alerts, incidents, device posture, investigation, and response evidence
Endpoint behavioral detections, storyline context, isolation, and remediation evidence
Endpoint detections, XDR investigations, isolation, and response state
Endpoint sensor telemetry, process behavior, detections, and response actions
Endpoint prevention, behavioral detection, threat, and response evidence
Endpoint protection detections, policy, device, and response context
Endpoint prevention, detection, forensics, and remediation evidence
Endpoint telemetry, threat detections, device trajectory, and response context
Endpoint behavioral detections, incident context, and response evidence
Endpoint detection, automated response, device, and forensic evidence
Endpoint and XDR analytics, incidents, causality, and response state
Endpoint protection events, detections, policy, and response context
Endpoint/XDR telemetry, workbench alerts, threat context, and response evidence
Endpoint prevention, EDR incidents, risk analytics, and response state
Endpoint telemetry, behavior alerts, investigation, and response evidence
Managed endpoint detections, persistent-footprint findings, and remediation context
Endpoint detections, isolation, remediation, and threat evidence
Endpoint detections, risk events, device posture, and response context
Bring firewall, edge, SASE, and network events into VitalSec while keeping their source and scope clear.
Network integrations let VitalSec read firewall, edge, and SASE state, keep the source clear, and use supported customer-approved changes where the integration allows them.
Network and application-delivery telemetry, security events, and policy context
Cloud firewall policy, flow, alert, and rule-evaluation evidence
Cloud firewall policy, threat-intelligence, flow, and rule evidence
Firewall traffic, security events, VPN, and policy state
SASE traffic, threat, access, and network-policy evidence
Firewall, IPS, threat prevention, policy, and network-event evidence
Firewall, intrusion, connection, policy, and remote-access evidence
Edge network policy, traffic, threat, and filtering evidence
Firewall, SD-WAN, IPS, policy, and connection context
Firewall, IPS, VPN, traffic, and security-policy evidence
Cloud firewall rule, hierarchical-policy, flow, and network evidence
Firewall, security-policy, threat, VPN, and session evidence
Branch firewall, security-appliance, VPN, client, and network-health evidence
Router/firewall rule, interface, connection, and network-event context
Open firewall, IDS/IPS, VPN, rule, and network-event evidence
NGFW traffic, threat, URL, policy, and session evidence
NGAF firewall, threat-detection, policy, and traffic context
Firewall, threat prevention, VPN, policy, and connection evidence
Firewall, IPS, application, web, VPN, and policy evidence
Firebox traffic, threat, VPN, policy, and security-service evidence
Private-access, gateway, device, and network-activity evidence
Firewall rule, interface, VPN, package, and network-event evidence
Internet-access policy, web transaction, threat, and user-activity evidence
Connect detections, security observations, investigations, and supporting evidence while keeping control facts tied to the system that actually owns them.
SIEM data adds detection and investigation context; control facts stay tied to the systems that can verify them.
Cloud SIEM alerts, incidents, analytics-rule, investigation, and evidence context
Searchable security events, correlation output, investigation, and timeline evidence
Security events, detection rules, cases, timelines, and analytics context
Offenses, events, flows, correlation, and investigation evidence
Security events, incidents, CMDB context, and correlation evidence
Normalized security telemetry, detections, entity context, and investigations
Security events, alarms, case, and correlation evidence
Security events, correlation events, cases, and investigation context
Behavior analytics, threat detections, incidents, and entity-risk context
Behavior analytics, timelines, cases, and threat-detection evidence
Cloud security logs, signals, insights, and investigation context
Security events, alarms, asset context, and threat-intelligence evidence
Connect backup scope, job health, freshness, recovery context, and supporting evidence so teams can see whether protection is actually current and recoverable.
Backup health is evaluated across scope, freshness, and recoverability rather than inferred from one status signal.
Endpoint backup coverage, last-backup freshness, and restore readiness
Backup job, protection-plan, endpoint, recovery, and cyber-protection evidence
Microsoft 365 and Google Workspace backup scope, snapshot, job, and restore context
Cloud-workload backup, retention, restore, and protection-state evidence
AWS backup plan, vault, recovery-point, job, and compliance evidence
Azure protected-item, vault, job, recovery-point, and restore evidence
Managed backup job, device, retention, and recovery evidence
Data-protection policy, backup job, snapshot, recovery, and resiliency evidence
Backup workload, job, policy, recovery, and cyber-resilience evidence
Appliance backup, snapshot, replication, recovery, and continuity evidence
Enterprise backup asset, policy, job, retention, and recovery context
Cloud backup workload, snapshot, restore, ransomware, and resiliency evidence
Google Cloud backup plan, appliance, job, recovery-point, and restore context
Microsoft 365 protection scope, backup status, recovery point, and restore context
Managed-device backup, job status, retention, and recovery evidence
VM and workload backup, replication, job, recovery, and immutability context
SaaS backup scope, job status, retention, and restore evidence
Data-protection SLA, snapshot, backup, recovery, and ransomware-resilience evidence
Backup appliance, job, recovery, replication, and continuity evidence
Backup job, repository, restore point, immutability, and recovery evidence
Enterprise backup policy, job, media, retention, and recovery evidence
Send approved actions into orchestration, run them within customer policy, and bring back evidence of what actually happened.
SOAR can execute approved steps, but VitalSec still checks the relevant system afterward before treating the work as complete.
Playbook execution, action result, case, and orchestration evidence
Playbook, incident, integration command, and response-outcome evidence
Case workflow, playbook, task, and response-action evidence
Playbook execution, incident workflow, connector action, and result evidence
Logic Apps playbook invocation, action result, incident, and automation evidence
Story execution, action, event, and governed-automation result
Low-code automation workflow, case, task, and action-result evidence
Security workflow execution, step output, case, and response evidence
Bring threat details, disposition, campaign context, and supporting evidence into the current security view without copying the whole mailbox into VitalSec.
Email integrations add threat and disposition context while keeping the connection limited to the evidence VitalSec actually needs.
Message threat verdicts, campaign, URL/attachment, user, and disposition evidence
Email threat detections, message tracking, policy, and remediation context
Email incidents, Safe Links/Attachments detections, message, and remediation evidence
Behavioral email attacks, account-takeover signals, cases, and remediation evidence
Message threat verdicts, sender/reputation, campaign, and disposition evidence
Email phishing/malware detections, message, policy, and response evidence
Email threat detections, impersonation, link, sender, and disposition context
VUMA and CAAT use vulnerability, asset, software, cloud, external-exposure, scanner, and managed-operations evidence to prioritize work, remediate, retest, and close findings.
Exposure integrations give VUMA and CAAT enough context to distinguish a raw finding from a confirmed exposure that needs action.
External exposure, passive reconnaissance, and internet-facing CAAT context
Cloud-managed vulnerability findings, assets, severity, and remediation-state evidence
Scanner findings, plugin output, asset context, and file-based vulnerability evidence
Asset inventory, vulnerability detections, prioritization, and remediation evidence
Asset vulnerability findings, risk scores, remediation projects, and validation context
Cloud posture, recommendations, attack-path, asset, and exposure evidence
AWS workload vulnerability findings, package exposure, severity, and resource context
Google Cloud findings, misconfiguration, vulnerability, and asset-posture context
Endpoint vulnerability inventory, affected hosts, CVE context, and remediation state
Endpoint vulnerability findings, software inventory, exposure score, and remediation context
Managed-device remediation assignment, execution, compliance, and result context
Managed-device inventory, patch state, remote-management, and remediation evidence
Asset discovery, software inventory, exposure, and attack-surface context
Host, port, service, and network-discovery evidence
Template-driven vulnerability findings, target, severity, and scanner evidence
Web-server findings, exposed files/configurations, and scan evidence
Network vulnerability findings, host/service context, severity, and scan evidence
Container, filesystem, IaC, SBOM, and SARIF vulnerability evidence
Use global, sector, exploitation, and technique intelligence to understand attacker pressure while keeping outside intelligence separate from what is actually observed in the customer environment.
Threat intelligence informs the risk model without being mistaken for a confirmed finding in the customer environment.
Cataloged known-exploited CVEs for exploitation-priority enrichment
Internet scanner/noise classification, IP context, and observed exploitation activity
CVE metadata, CVSS, CWE, references, and vulnerability enrichment
ATT&CK techniques, tactics, software, groups, and STIX relationship context
HHS healthcare cyber threat briefs, alerts, sector tactics, and adversary context
Healthcare community threat intelligence, indicators, alerts, and sector context
Open-source package vulnerability records, affected versions, and ecosystem enrichment
Bring passive medical-device identity, clinical context, vulnerability, and threat observations into VitalSec for asset visibility, VUMA prioritization, evidence, and risk analysis.
These integrations contribute passive device and exposure evidence. They do not give VitalSec permission to change medical devices.
Passive medical-device discovery, identity, clinical context, vulnerability, and exposure evidence
Passive connected-device inventory, behavior, communication, vulnerability, and risk context
Connect agency-management data to broker account, portfolio, onboarding, renewal, and evidence workflows while keeping the broker's book context intact.
Agency-management integrations let the broker workspace start from the book brokers already use every day.
Broker account, policy, client, renewal, activity, and book-of-business context
Agency client, policy, renewal, activity, and account-management context
Enterprise agency account, policy, renewal, and book-of-business context
Bring exported scanner and evidence files into VitalSec when a product provides files instead of a continuous API, while keeping the source clear and connecting the evidence to remediation and proof.
Portable formats let evidence enter VitalSec without forcing every tool into the same connection method.
Portable analysis findings with rule, location, severity, and tool provenance
Software component, dependency, license, vulnerability, and supply-chain evidence
Software package, component, license, relationship, and provenance evidence
Portable Nessus scan findings, plugin output, host, port, and severity evidence
Send verified evidence into carrier, policy-administration, GRC, assurance, ratings, and governance workflows so the people making those decisions can use the same current record.
Outbound integrations make verified evidence available where underwriting, governance, assurance, and portfolio decisions are made.
Validated cyber evidence for carrier policy, underwriting, claims, and account workflows
Validated cyber evidence for carrier policy-administration, underwriting, and claims workflows
Control, risk, issue, evidence, and compliance records for GRC workflows
Risk, control, finding, assessment, and evidence records for IRM workflows
Risk, control, assessment, compliance, and evidence data for governance workflows
Enterprise risk, control, issue, audit, and compliance evidence
Risk Cloud controls, assessments, issues, and evidence for governance workflows
Control, requirement, evidence, task, and assurance records for compliance workflows
Audit, risk, control, issue, and evidence data for connected-assurance workflows
Governance, risk, compliance, issue, and control evidence for OpenPages workflows
Governance, reporting, audit, risk, and evidence packages for connected-reporting workflows
Audit, risk, control, issue, and assurance evidence for HighBond workflows
Control monitoring, test, evidence, compliance, and assurance data for trust workflows
Control monitoring, evidence, test, compliance, and assurance data for GRC workflows
Structured cyber-risk evidence package for insurer financial-strength and rating workflows
Governed cyber-risk evidence package for S&P analytics and ratings workflows
Governed cyber-risk evidence package for Moody's analytics, credit, and ratings workflows
Governed cyber-risk evidence package for Fitch credit, insurer, and ratings workflows
Why the breadth matters
Observe → Decide → Act → Validate → Prove → Measure
Read from the source
Identity, endpoint, network, backup, SIEM, email, exposure, threat, and medical-device evidence keeps its source and scope attached.
Act only when approved
EDR, identity, remediation, and SOAR integrations can act only through the permissions and policies set for that customer.
Prove the result
After an action, VitalSec checks the relevant system again before treating the work as complete.
Carry evidence outward
Insurance, GRC, ratings, and portable-evidence integrations make verified information useful beyond the security team.
Your stack
Tell us which tool you use and what you want VitalSec to read, change, verify, or pass into another workflow.