Jump to Content
Jit - Product-Security-as-a-Service - Documentation★Start Free★
GuidesAPI Reference
★Start Free★Jit - Product-Security-as-a-Service - Documentation
Guides
GuidesAPI Reference

Welcome!

  • About Jit
  • Key Features and Experiences
  • Security Mapping

Security Champion Experience

  • Onboarding Steps: Getting started with Jit
    • Connect Jit with your GitHub Account
    • Connect Jit with your GitLab account
      • GitLab integration method - Fastest
      • GitLab integration method - Fast
      • Configuring Self-Hosted Runners for Jit
      • Troubleshooting
    • Explore Jit Features
  • Platform User Interface
    • Overview
    • Security Plans
    • Specific Plan Page
    • Pipelines
    • Actions
    • Teams
    • Security Impact
    • Performance
    • Pull Requests
    • Risk and Context Engine
      • Backlog
      • Resource
    • Integrations
    • Manage Resources
    • Users and Permissions
    • Secrets
  • Integrating with Third-Party Products and Services
    • Slack Integrating
    • AWS Integration
    • Azure Integration
    • GCP Integration
    • Ticketing Management Systems (TMS) Integrations
    • Jira Integration
    • Linear Integration
    • Shortcut Integration
    • Monday.com Integration
    • Semgrep Pro Tier Integration
    • Legitify Integration
    • NPM registry Integration
    • Drata Integration
    • Wiz Integration
    • Splunk Cloud integration
  • Security as Code Configuration
    • Monorepo Support
    • Files and Folder Exclusions
    • Concealed Public Repos
  • Jit Scripts for extended usability
    • Jit Teams sync
    • Jit on GitHub self-hosted runners
  • Audit logs

Developer Experience

  • Developers Getting Started
  • Change-Based Security Tests in Pull-Requests
  • Automated Remediation
  • Jit IDE Extension for Visual Studio Code

Security Plan Reference

  • Security Plans Introduction
  • Security Plan Structure
    • Plan Resources Exclusion
    • Plan Workflow Modifications
    • Run ZAP-Based Security Controls on a GitHub-Hosted Runner
  • Product Security Plans
    • Jit MVS for AppSec Plan
    • AWS Foundational Technical Review (FTR)
    • GitHub Security Plan
    • SOC2 by Drata
  • Security Controls
    • Scan Your Code for Vulnerabilities (SAST)
    • Scan Your Code Dependencies for Vulnerabilities (SCA)
    • Scan Code for Hard-Coded Secrets
    • Scan Your Dockerfiles for Vulnerabilities
    • Scan Kubernetes Configuration Files
    • Scan Your infrastructure-as-code (IaC) for Misconfigurations
    • Scan Infrastructure for Runtime Misconfigurations
    • Verify that The Users of Your AWS Accounts Have Enabled MFA
    • Import AWS Security Hub Findings
    • Scan Your API for Vulnerabilities (DAST)
    • Scan your Web Application for Vulnerabilities (DAST)
    • Configuring Vulnerability Scans for Web Applications
    • ZAP Rules for Detecting Vulnerabilities
    • Configuring Vulnerability Scans for APIs
    • Verify that MFA for Your GitHub Organization is Enabled
    • Verify that Github Branch Protection is Properly Configured
    • Detect GitHub Misconfigurations
    • Software Bill of Materials (SBOM)
    • Scan your Code for License Violations
  • Security Tools
  • Deployment-Based Scanning
  • Code Samples and Test Targets

GUIDES AND Troubleshooting

  • Troubleshooting
    • GitHub Outage
    • Retrieving Authentication Information With Browser Developer Tools
    • Troubleshooting AWS Integration
    • Upgrading from Prowler v2 to Prowler v3
    • Configuring Branch Protection for Jit Compatibility
    • Supporting Non-Default Branch Scanning
Powered by 

Troubleshooting

Suggest Edits
  • GitHub Outage
  • Retrieving Authentication Information With Browser Developer Tools
  • Troubleshooting AWS Integration
  • Upgrading from Prowler v2 to Prowler v3
  • Configuring Branch Protection for Jit Compatibility

Alt text

Updated 6 months ago