Back to Integrations

Opsgenie Integration

Streamline incident response with intelligent access automation. Integrate TigerAccess with Opsgenie for on-call based access, incident-triggered permissions, and real-time security alerts.

Features

Intelligent Incident Response

Automate access management based on on-call schedules and incident workflows.

On-Call Integration

Automatically grant access to on-call engineers based on their rotation schedule with time-bound permissions.

Incident-Triggered Access

Provision just-in-time access when incidents are created, with automatic revocation when incidents close.

Alert Notifications

Send real-time alerts to Opsgenie for high-risk access events, anomalies, and security violations.

Escalation Policies

Integrate access approval workflows with Opsgenie escalation chains for faster incident response.

Capabilities

Enterprise-Grade Opsgenie Integration

On-call schedule sync
Incident-based access
Alert routing to teams
Escalation policy integration
Break-glass notifications
Access request alerts
Session anomaly alerts
Heartbeat monitoring
Custom alert actions
Runbook automation
Team-based routing
Priority-based access
Setup

Get Started in Minutes

Follow these simple steps to integrate TigerAccess with Opsgenie.

1

Create Opsgenie API Integration

Generate an API key in Opsgenie with permissions for alerts, schedules, and incidents.

# In Opsgenie:
# 1. Go to Settings > Integration List
# 2. Add "API" integration
# 3. Copy the API Key
# 4. Set permissions:
#    - Create and Update Alert
#    - Read Schedule
#    - Read Incident
2

Configure TigerAccess Integration

Add the Opsgenie integration to TigerAccess with your API key and team configuration.

tacctl integrations add opsgenie \
  --api-key=xxxxx-xxxx-xxxx-xxxx-xxxxxxxxx \
  --region=us \
  --teams=platform,security,sre \
  --enable-schedules \
  --enable-incidents
3

Configure Access Rules

Set up rules to automatically grant access based on on-call schedules and incident status.

# Create on-call access rule
tacctl access-rules create oncall-production \
  --schedule="Primary On-Call" \
  --resources="env:production" \
  --duration=8h \
  --auto-approve

# Create incident access rule
tacctl access-rules create incident-access \
  --incident-priority=P1,P2 \
  --resources="tag:incident-response" \
  --duration=24h \
  --require-reason
4

Set Up Alert Routing

Configure which TigerAccess events should trigger Opsgenie alerts and their routing.

# Configure alert rules
tacctl alerts add opsgenie-security \
  --events="failed_login,anomaly_detected,policy_violation" \
  --priority=P2 \
  --teams=security \
  --responders="team:security-oncall"

# Configure break-glass alerts
tacctl alerts add break-glass \
  --events="emergency_access_granted" \
  --priority=P1 \
  --teams=security,management \
  --note="Break-glass access granted"
Use Cases

Real-World Opsgenie Scenarios

On-Call Access Automation

Automatically grant on-call engineers access to production systems during their rotation. Access is provisioned when the shift starts and revoked when it ends, with full audit trails.

Incident Response Acceleration

When a P1 incident is created in Opsgenie, automatically grant the incident commander and responders access to affected systems with elevated permissions for faster resolution.

Security Event Escalation

Route high-severity privileged access events through Opsgenie escalation policies. Failed login attempts, unusual access patterns, and policy violations trigger alerts to security teams.

Break-Glass Access Control

Enable emergency break-glass access for critical incidents while simultaneously alerting security teams through Opsgenie with incident context and approval workflows.

FAQ

Frequently Asked Questions

How does on-call schedule synchronization work?

TigerAccess periodically syncs with Opsgenie schedules (every 5 minutes by default). When an engineer goes on-call, TigerAccess automatically provisions access based on configured rules. When they go off-call, access is automatically revoked. All changes are logged with the schedule context.

Can access be granted automatically when an incident is created?

Yes. TigerAccess can monitor Opsgenie incidents and automatically grant access to incident responders when incidents of specified priorities are created. Access can be scoped to specific resources relevant to the incident and is automatically revoked when the incident is resolved.

What types of events trigger Opsgenie alerts?

You can configure TigerAccess to send alerts for any security event including: failed authentication attempts, anomalous access patterns, policy violations, break-glass access usage, high-privilege operations, and access request approvals. Each alert includes full context and links to session recordings.

How do escalation policies integrate with access approvals?

TigerAccess access request workflows can be configured to follow Opsgenie escalation policies. When a user requests access, the approval request is routed through the configured escalation chain. If the first approver doesn't respond within the timeout, it automatically escalates to the next level.

Can I use Opsgenie schedules for approval workflows?

Yes. Access approval workflows can be configured to route to whoever is on-call in a specific Opsgenie schedule. For example, "Production Database Access" requests can automatically route to whoever is on the "DBA On-Call" schedule, ensuring requests always reach available personnel.

What happens if the Opsgenie integration fails?

TigerAccess includes heartbeat monitoring and will alert if the Opsgenie integration becomes unavailable. Access grants and revocations continue to work based on cached schedule data. You can configure fallback approval workflows that don't depend on Opsgenie for critical access paths.

Ready to Secure Your Infrastructure?

Join thousands of security-conscious teams using TigerAccess to protect their critical infrastructure and AI agents.

No credit card required • 14-day free trial • Enterprise support available