Overview Guard Dog Proxy for Jira
These guides will walk you through setting up Guard Dog Proxy for Jira. Designed specifically for administrators, they provide a comprehensive overview of all the features available in Guard Dog Proxy for Jira.
Challenges
Companies that move from on-premises or data center solutions to SaaS cloud-based solutions gain significant operational benefits. However, many of the methods used to monitor the health of their integrations are no longer available to them. As a result, organizations face challenges in maintaining an oversight of their API governance for API Proxy within the Atlassian ecosystem, leaving them vulnerable to evolving security threats.
Key features
Comprehensive data tracking and logging
Proxy configuration: Generate proxy URLs to track API requests passing through the app.
Logging of activity: Log all request events through API proxy.
API integration and log management
Integration with Splunk and Logstash: Push logs to Splunk for advanced monitoring and alerts or to Logstash for flexible log analysis using the ELK stack.
Insights and analytics
Insight cards: Display critical information that defines API health
Analysis chart: Provide visualizations to offer deeper insights into the shared data.
Dashboards and visualization
Overview dashboard: Offers a more holistic view of API data usage.
Policies and automation
Policies & automation: Increase customization for business units to enhance API security and streamline governance.
Some further concepts are explained at the Key concepts Guard Dog Proxy for Jira page.
Key benefits
Perform monitoring within the Atlassian environment.
Easily connect with external monitoring and alerts.
Probe incidents or activities from logs.
Early detection of API traffic anomalies.
Customize policies to fit cloud security governance.
Implement the same data center processes in the cloud.
Empowers and delivers greater transparency.
Use cases
Resolving security governance as an organization migrates to the cloud.
Centralizing cloud governance, policies and protocols.
Identifying the root cause of an integration incident.
Monitoring integration traffic under the hood in the Atlassian environment.