Works with your existing tools

Integrations

Security scanning that fits into your existing workflow. Connect your CI/CD pipelines, source control, issue trackers, and infrastructure tools.

CI/CD Pipeline Integrations

Scan on every commit. Block vulnerable builds. Ship secure code.

GitHub Actions

Available

Trigger scans on push, PR, or release. Results posted as PR comments and status checks.

GitLab CI/CD

Available

Native integration via .gitlab-ci.yml. Results appear in the GitLab security dashboard.

Bitbucket Pipelines

Available

Add security scanning to your Bitbucket pipeline with our pipe integration.

Azure DevOps

Available

Azure Pipelines task for SAST and DAST scanning in your build process.

Jenkins

Available

Jenkins plugin for triggering scans and collecting results as build artifacts.

CircleCI

Available

CircleCI orb for adding security scanning to your CI/CD workflow.

Source Control

Connect your repositories and scan code automatically.

GitHub

Connect repositories directly. Auto-scan on push or pull request.

GitLab

Self-hosted and GitLab.com repository integration.

Bitbucket

Bitbucket Cloud and Server repository connection.

Azure Repos

Azure DevOps repository integration with branch policies.

Issue Tracking & Notifications

Get notified instantly and track remediation in the tools you already use.

Jira

Auto-create tickets for new vulnerabilities with severity mapping.

Slack

Get real-time scan notifications and alerts in your Slack channels.

Microsoft Teams

Push scan results and vulnerability alerts to Teams channels.

Webhooks

Send scan events to any system via customizable webhook payloads.

Infrastructure & Containers

Secure your infrastructure-as-code and container configurations.

Docker

Scan Docker images and Dockerfiles for security misconfigurations.

Kubernetes

Analyze Kubernetes manifests, Helm charts, and cluster configurations.

Terraform

Scan Terraform files for insecure cloud configurations and policy violations.

AWS CloudFormation

Validate CloudFormation templates against security best practices.

Set up in minutes

A few lines of YAML is all you need to add security scanning to your pipeline.

.github/workflows/security.yml

name: Security Scan
on: [push, pull_request]

jobs:
  sast:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Run Offensive360 SAST
        uses: offensive360/sast-action@v1
        with:
          api-key: ${{ secrets.O360_API_KEY }}
          project-id: ${{ secrets.O360_PROJECT_ID }}
      - name: Upload Results
        uses: actions/upload-artifact@v4
        with:
          name: sast-report
          path: o360-report.json

Integrate security into your pipeline

Set up CI/CD scanning in minutes. Our setup wizard generates the configuration for your platform.

Get Started Book a Demo