Skip to content

cravex2-reachability: Create a design/evaluation doc for rules engines and policy engines #1962

Description

@pombredanne

We need a design and and evaluation document for the necessary features with the results of testing rules engines and policy engines. It should describe the features we need for these. It also means we want to evaluate rules tools triaging vulnerabilities

Activity

  1. self-assigned this
    on Apr 9, 2026
  2. TG1999 commented on Apr 9, 2026

    @TG1999
    Contributor

    I am working on suggesting the kind of rules we can have on the basis of our existing data in VCIO.

  3. moved this from Needs prep to In progress in 00-AboutCodePlanneron Jun 4, 2026
  4. pombredanne commented on Jul 16, 2026

    @pombredanne
    MemberAuthor

    @TG1999 do you have a doc with some results of your eval?

  5. TG1999 commented on Aug 18, 2026

    @TG1999
    Contributor

    aboutcode-org/www.aboutcode.org#176 Design decision is ready for review here

  6. TG1999 commented on Aug 21, 2026

    @TG1999
    Contributor
  7. TG1999 commented on Aug 24, 2026

    @TG1999
    Contributor

    This is done now

    Reference:

    We have an architecture decision where we have weighed and evaluated many options, Also we have a POC banch where we experiemented these options

  8. moved this from Done to Reviewed in 00-AboutCodePlanneron Aug 24, 2026
  9. changed the title [-]cravex2-reachability: Evaluate rules tools triaging vulnerabilities[/-] [+]cravex2-reachability: Create a design and evaluation document for the necessary features with the results of testing rules engines and policy engines - Evaluate rules tools triaging vulnerabilities[/+] on Sep 22, 2026
  10. changed the title [-]cravex2-reachability: Create a design and evaluation document for the necessary features with the results of testing rules engines and policy engines - Evaluate rules tools triaging vulnerabilities[/-] [+]cravex2-reachability: Create a design/evaluation doc for rules engines and policy engines[/+] on Sep 22, 2026
  11. moved this from Reviewed to Validated in 00-AboutCodePlanneron Sep 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions