refactor(deps): Merge defsec into trivy

[simar7]

Description

Merges any remaining defsec packages into Trivy.

Related issues

• Close refactor(misconf): Merging trivy-iac into Trivy #5626 (comment)

Related PRs

• refactor(deps): Merge trivy-iac into Trivy #6005
• refactor(deps): Use trivy pkgs instead of defsec trivy-checks#77
• refactor(deps): Use trivy pkgs instead of defsec trivy-aws#99

Checklist

• I've read the guidelines for contributing to this repository.
• I've followed the conventions in the PR title.
• I've added tests that prove my fix is effective or that my feature works.
• I've updated the documentation with the relevant information (if needed).
• I've added usage information (if the PR introduces new options)
• I've included a "before" and "after" example to the description (if the PR is a user interface change).

[knqyf263]

According to #5626, I presumed most logic existed in trivy-iac, so we've almost done the migration in #6005. However, this PR is also huge. What is the difference between trivy-iac and defsec?

[knqyf263]

What is this file for? I'd like to keep Trivy only under the cmd/ dir. Does Mage help?
https://github.com/aquasecurity/trivy/tree/main/magefiles

[simar7]

In order to support wildcards here we need to constantly know which actions are allowed. This is automatically generated by this code and put here.

I've converted them both (schema and allowed actions) into magefile targets. Thanks for the suggestion!

[simar7]

According to #5626, I presumed most logic existed in trivy-iac, so we've almost done the migration in #6005. However, this PR is also huge. What is the difference between trivy-iac and defsec?

Sorry I apologize for another big PR but it is the last remaining pieces of defsec that are part of this PR.

As for the differences, we merged all the parsers (code that parses language files) and adapters (code that adapts parsed language files into defsec state) in the last PR. This PR is about merging the providers (code that describes the state of a service like AWS).

[knqyf263]

Sorry I apologize for another big PR but it is the last remaining pieces of defsec that are part of this PR.

No apologies! I was just wondering why this PR was so large.

As for the differences, we merged all the parsers (code that parses language files) and adapters (code that adapts parsed language files into defsec state) in the last PR. This PR is about merging the providers (code that describes the state of a service like AWS).

I drew a diagram. Is this correct?

[simar7]

I drew a diagram. Is this correct?

Yes I would say so 👍🏼

[knqyf263]

Yes I would say so 👍🏼

Thanks for confirming!