Use Case Recommendations

Different scenarios favor different tools:
# use-case-recommendations.yaml
recommendations:
  use_trivy_when:
    - scenario: "Air-gapped or restricted environments"
      reason: "Full offline capability after initial setup"
      
    - scenario: "High-volume CI/CD pipelines"
      reason: "Fast scanning with minimal overhead"
      
    - scenario: "Budget-conscious organizations"
      reason: "Zero licensing costs"
      
    - scenario: "Simple vulnerability detection needs"
      reason: "Excellent detection without complexity"
      
    - scenario: "Kubernetes-native environments"
      reason: "Strong Kubernetes integration via Trivy-Operator"
      
  use_snyk_when:
    - scenario: "Developer-centric organizations"
      reason: "Superior developer experience and IDE integration"
      
    - scenario: "Need automated remediation"
      reason: "Automated fix PRs and upgrade guidance"
      
    - scenario: "Enterprise compliance requirements"
      reason: "Comprehensive reporting and audit trails"
      
    - scenario: "Multi-language applications"
      reason: "Broader language and framework support"
      
    - scenario: "Continuous monitoring needs"
      reason: "Built-in monitoring and alerting"
      
  use_both_when:
    - scenario: "Defense in depth strategy"
      reason: "Different detection capabilities complement each other"
      
    - scenario: "Migration scenarios"
      reason: "Gradual transition between tools"
      
    - scenario: "Critical infrastructure"
      reason: "Cross-validation of security findings"