Integrations¶

GRC-ITSM is built on HaloITSM and inherits its native integration catalog, spanning identity, asset management, security, communication, automation, and more, each connector enabled and configured independently. The vendor owns that catalog and its setup guides: Halo advertises over 200 native integrations across its product family.

This page covers the part that is ours: the integrations Stratus refines for compliance work, and the connectors that carry weight when the platform sits inside an authorization boundary.

Navigation

Configuration > Integrations on the GRC-ITSM website navigation.

Canonical reference

HaloITSM is the canonical source for the integration catalog and for per-integration setup instructions. The complete, filterable list is at haloitsm.com/integrations, and the configuration guides are in the Halo guides library. Anything not documented here is documented there.

FedRAMP and Compliance Environments

If the GRC-ITSM platform is deployed within a FedRAMP authorization boundary (or any controlled environment handling CUI), every integration that connects to an external service creates a data flow across the boundary that must be documented and assessed.

Before enabling any integration:

Verify the external service is FedRAMP-authorized or has an acceptable risk profile approved by the Authorizing Official
Document the integration in the System Security Plan (SSP), including data flow diagrams and interconnection details
Ensure compliance with CA-3 (Information Exchange), SA-9 (External System Services), SC-7 (Boundary Protection), and CM-7 (Least Functionality)
Disable all integrations that are not necessary for operations

Integrations with FedRAMP-authorized services (such as Microsoft Entra ID or Microsoft Teams on a FedRAMP tenant) carry lower risk because the external service already has an assessed security posture, but they still require formal documentation and boundary monitoring.

What Stratus adds¶

Some integrations need more than the vendor's stock setup to work well in GRC-ITSM: the right ticket type, a category that drives framework linkage, and populated fields so a responder can act without leaving the ticket. Where we have refinements, they get their own page covering what to change on top of the vendor's guide.

Integration	What the page covers
AWS GuardDuty & CloudWatch	A deployable Lambda-to-webhook stack that forwards GuardDuty findings and CloudWatch alarm state changes into the Alert ticket type
Datadog	Routing monitor and security alerts into the Alert ticket type with category-driven control mapping and populated technical fields
Steampipe/Powerpipe Stack	Running the Stratus-provided compliance-scanning deployment in your environment and feeding machine-based KSI validation records into the platform
Platform Connectors	Creating the read-only Okta, GitLab, and GitHub identities the compliance scan authenticates with, the permissions each needs, and where the values go in the scanner stack
Compliance Exemptions	Tagging a cloud resource so the compliance scan reports it as skipped instead of failing, with the justification carried into the evidence
Halo Integrator	The scheduled import and synchronization service that keeps the platform in sync with Entra ID, RMM tools, and other asset sources
Trust Center Uploads	Uploading FedRAMP certification JSON artifacts into Certification Documents through the three-call Halo Attachment presigned-URL flow
Webhooks	Incoming and outgoing HTTP webhooks: filing alerts and validation evidence into the platform, and triggering external workflows from platform events

More integration pages follow as we refine them.

Connectors that carry compliance weight¶

The groups below are the parts of the vendor catalog that most often end up in an SSP, an evidence pipeline, or a control narrative. Each is configured through the vendor's own guide; what matters here is why an assessor cares about it. Anything not listed is still available in the full HaloITSM catalog.

Identity and access¶

Source of user provisioning, authentication, and Single Sign-On. These feed access control and user access review evidence (AC-2, AC-3).

Integration	Purpose
Microsoft Entra ID	Identity synchronization, user and group management, and SSO
Active Directory	On-premise AD synchronization
AD FS	Active Directory Federation Services for SSO
Okta	Identity and access management platform
SailPoint	Identity governance and administration
Centrify	Privileged access management
Google Workspace	Google identity and user management
Single Sign-On	Generic SSO configuration (SAML, OAuth)

Security monitoring and vulnerability management¶

Sources of vulnerability findings and security telemetry. These feed the scanning and monitoring record (RA-5, SI-4) and, through the Steampipe/Powerpipe stack, machine-based KSI validation.

Integration	Purpose
Qualys	Vulnerability management
Rapid7	Vulnerability and threat detection
Tenable	Vulnerability scanning
SentinelOne	Endpoint detection and response
Splunk	SIEM and log analytics
Azure Sentinel	Microsoft SIEM and SOAR
Azure Monitor	Cloud monitoring and alerting
Datadog	Infrastructure monitoring, with Stratus alert-routing refinements
AWS GuardDuty & CloudWatch	GuardDuty findings and CloudWatch alarm state changes, with Stratus alert-routing refinements

Incident response and on-call¶

Alert routing and escalation paths. These carry incident handling and reporting evidence (IR-4, IR-6) and connect to the Incident Response playbook.

Integration	Purpose
PagerDuty	Incident response and on-call scheduling
Opsgenie	Alerting and incident management
Splunk On Call	Incident alerting and on-call management
XSOAR	Security orchestration, automation, and response
ServiceNow	Enterprise ITSM
Jira Service Management	ITSM and incident tracking

Asset inventory and discovery¶

Sources that populate and maintain the inventory of the components inside the boundary (CM-8). Most reach the platform through the Halo Integrator.

Integration	Purpose
Halo Asset Discovery	Built-in asset discovery
Intune	Microsoft endpoint management
AWS / Azure Key Vault	Cloud resource and secrets inventory
Jamf / Kandji / Addigy	Apple device management
Lansweeper / Device42 / Snipe-IT	IT asset discovery and management
NinjaOne / Datto RMM / Connectwise / N-Able / Kaseya	RMM and endpoint management
Tanium	Endpoint management and security
SCCM / SCOM	Microsoft System Center management
Liongard	Configuration capture and change detection

Remote access¶

Remote support sessions into managed systems. Each is a remote access path that must be documented and authorized (AC-17), and monitored (AC-17(1)).

Integration	Purpose
Beyond Trust	Privileged remote access
Connectwise Control	Remote access and support
TeamViewer	Remote desktop and support
Splashtop / Anydesk / ISL Online	Remote desktop
GoTo Resolve / GoToAssist	Remote support
LogMeIn Rescue	Remote support
N-Able Take Control	Remote access

Communication and notification¶

How the platform reaches people: approvals, alerts, and change windows.

Integration	Purpose
Microsoft Teams	Team chat, notifications, and ticket interactions
Slack	Team messaging and notifications
Twilio for SMS	SMS notifications and two-way messaging
Exchange Calendars / Google Calendars	Calendar sync for scheduling and change windows

Automation and extensibility¶

The surfaces you build on when no stock integration fits.

Integration	Purpose
HaloPSA API	Halo's REST API (branded HaloPSA across the Halo product line), for custom integrations and external connectivity
Webhooks	Send or receive HTTP webhooks for event-driven automation. Powers the n8n automation pipeline
Halo Integrator	Scheduled import and synchronization service
Microsoft Power Automate	Low-code workflow automation
Azure Automation	Cloud-based runbook execution
PowerShell	Script execution for automation tasks
Zapier	No-code automation connector
Lookups	External data lookups for enriching ticket and asset data
SQL Imports / Scheduled Imports	Direct and recurring data imports
Custom Integrations	Build your own using the platform's extensibility framework

AI services¶

The platform's built-in AI service connections. For connecting AI assistants such as Claude to operate GRC-ITSM, see AI.

Integration	Purpose
Azure OpenAI	AI capabilities via Azure-hosted OpenAI models
OpenAI	Direct OpenAI API access
Azure AI Search	AI-powered search indexing
Azure AI Translator	Multilingual translation
OpenSearch	Search and analytics engine