This title slide features the main title "Jira for Security Engineers using AWS." Its subtitle emphasizes "Empowering AWS security workflows."

Jira for Security Engineers using AWS

Empowering AWS security workflows

Jira is an agile tool for issue tracking and workflows that streamlines Security Operations (SecOps) in AWS. It enhances collaboration, visibility in cloud security, and supports agile methodologies for security engineers.

Introduction to Jira in AWS Security

• Jira: Agile tool for issue tracking and workflows
• Streamlines Security Operations (SecOps) in AWS
• Enhances collaboration and visibility in cloud security
• Supports agile methodologies for security engineers

This slide outlines setting up Jira for SecOps teams by creating a Security Board project and configuring issue types for Vulnerabilities and Incidents. It also covers setting permissions with custom fields for AWS data, plus integrating users and basic workflows.

Setting Up Jira for SecOps Teams

• Create a Security Board project
• Configure issue types: Vulnerabilities and Incidents
• Set permissions and custom fields for AWS data
• Integrate users and basic workflows

The slide "Integrating Jira with AWS Tools" outlines key integrations in a table format. It details CloudWatch sending alerts to Jira tickets, Security Hub auto-creating issues from findings, and Lambda automating ticket updates.

Integrating Jira with AWS Tools

{ "headers": [ "Tool", "Integration" ], "rows": [ [ "CloudWatch", "Alerts to Jira tickets" ], [ "Security Hub", "Findings auto-create issues" ], [ "Lambda", "Automate ticket updates" ] ] }

The slide outlines two common use cases in a two-column format. The left column describes Incident Tracking by logging AWS alerts from CloudWatch or Security Hub into Jira issues for assignment, prioritization, and resolution; the right covers Vulnerability Management by prioritizing CVEs based on severity and exposure to create remediation tickets and monitor progress.

Common Use Cases

This slide on Best Practices for Automation & Reporting recommends automating tickets via webhooks and AWS Lambda while building dashboards for security metrics and SLA reports. It also advises using JQL queries for AWS-specific searches and conducting regular audits for compliance and optimization.

Best Practices: Automation & Reporting

• Automate tickets using webhooks and AWS Lambda
• Build dashboards for security metrics and SLA reports
• Use JQL queries for AWS-specific searches
• Conduct regular audits for compliance and optimization

This slide depicts the Security Issue Tracking Workflow, with phases including Detect (Security Hub, real-time), Create & Assign Ticket (Automation/Lambda, <1 min), Investigate (Security Engineer/CloudWatch, 24-48 hrs), Remediate (Security Engineer/Various, 3-5 days), and Close & Report (Manager/Jira Reports, 1 day). It structures the process by phase, owner, duration, and AWS tools for efficient security management.

Example: Security Issue Tracking Workflow

{ "headers": [ "Phase", "Owner", "Duration", "AWS Tools" ], "rows": [ [ "Detect", "Security Hub", "Real-time", "Security Hub" ], [ "Create & Assign Ticket", "Automation", "<1 min", "Lambda" ], [ "Investigate", "Security Engineer", "24-48 hrs", "CloudWatch" ], [ "Remediate", "Security Engineer", "3-5 days", "Various" ], [ "Close & Report", "Manager", "1 day", "Jira Reports" ] ] }

The slide summarizes key takeaways: Jira boosts AWS SecOps efficiency through early integration, automation, reporting, and a strategy of starting simple before scaling up. It closes with thanks and an invitation for Q&A.

Summary & Key Takeaways

• Jira boosts AWS SecOps efficiency

• Key: Integrate early, automate, report
• Start simple, scale up

Thanks! Q&A

Thank you for your attention!