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

Welcome!

  • About Jit

Security Champion Experience

  • Getting Started
  • Integrating with GitHub
  • Platform User Interface
    • My Plan
    • Pipelines
    • Actions
    • Performance
    • Pull Requests
    • Backlog
    • Integrations
    • Manage Resources
    • Users and Permissions
  • Integrating with Third-Party Products and Services
    • Integrating with Slack
    • Integrating with AWS
  • Security as Code Configuration
    • Monorepo Support
    • Folder Exclusion

Developer Experience

  • Getting Started
  • Change-Based Security Tests in Pull-Requests
  • Automated Remediation

Security Plan Reference

  • Introduction
  • Security Plan Structure
  • Product Security Plans
    • Jit MVS for AppSec Plan
  • Security Requirements
    • Scan Code for Vulnerabilities
    • Scan Code for Hard-Coded Secrets
    • Scan Code Dependencies for Vulnerabilities
    • Scan IaC for Misconfigurations
    • Scan for Infrastructure Runtime Misconfigurations
    • Scan Container Images
    • Require MFA for Cloud Providers
    • Require MFA for SCM
    • Run a Web Application Scanner (DAST)
    • Ensure Your APIs are Secure (DAST)
    • Require Branch Protection for SCM
  • Security Tools
  • Code Samples and Test Targets

Troubleshooting

  • Retrieving Authentication Information With Browser Developer Tools
  • Troubleshooting AWS Integration

Legal

  • Terms of Use
  • Privacy Policy
Powered by 

Introduction

Suggest Edits

This chapter describes Jit's security plans and their constituent components in detail.

  • For a complete list of security plans supported by Jit, see Security Plans.
  • For a complete list of available security requirements, see Security Requirements
  • For a complete list of security tools, see Security Tools.

Updated 8 months ago


What’s Next

For an in-depth explanation of how security plans are structured, see the following—

  • Security Plan Structure and Components