Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Summary Renderer #179

Open
nhopkins19 opened this issue Nov 2, 2023 · 1 comment
Open

Summary Renderer #179

nhopkins19 opened this issue Nov 2, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@nhopkins19
Copy link
Member

I want to add the feature of having bomber output a summary report, with non-technical friendly terminology of how the vulnerability findings can be exploited by bad actors. This can be accomplished by adding a renderer for summary as well as integrating with the OpenAI API.

@nhopkins19
Copy link
Member Author

So the steps here would be:

  1. Integrate OpenAI's API and key into Bomber.
  2. Generate text based summary of CVE findings by using render and OpenAI to provide a summary on said findings:
    func generateSummary(client *openai.Client, cveDescription string) (string, error) {
    prompt := "Summarize the following CVE:\n" + cveDescription
    response, err := client.Completions.Create(
    openai.CompletionParams{
    Prompt: prompt,
    MaxTokens: 100, // Adjust as needed
    Temperature: 0.7, // Adjust to control randomness
    },
    )
    if err != nil {
    return "", err
    }
    return response.Choices[0].Text, nil
    }
  3. Use OpenAI to generate example scenarios of how the CVE's can be exploited.
  4. Set some type of API rate limit threshold?

Loose overview of how to potentially implement this

@djschleen djschleen added this to the 0.5.0 milestone Mar 8, 2024
@djschleen djschleen added the enhancement New feature or request label Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

2 participants