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

Updates to Fuzzing Documentation #86

Open
olearycrew opened this issue Oct 2, 2024 · 0 comments
Open

Updates to Fuzzing Documentation #86

olearycrew opened this issue Oct 2, 2024 · 0 comments

Comments

@olearycrew
Copy link
Contributor

Objective: Update the fuzzing documentation to incorporate insights from Brendan's BSides presentation, helping users better understand how to use fuzzing templates. Additionally, include "DAST" as the flag and update the wording accordingly.

Tasks:

  1. Review Brendan's Presentation:

    • Obtain and review the presentation materials from Brendan's BSides talk.
    • Extract key insights and examples that can enhance the fuzzing documentation.
  2. Update Fuzzing Templates Section:

    • Revise the section on fuzzing templates to include detailed explanations and examples from the presentation.
    • Ensure that the documentation clearly guides users on how to effectively use fuzzing templates.
  3. Incorporate "DAST" Flag:

    • Update the documentation to include "DAST" as a flag.
    • Provide a clear explanation of the "DAST" flag and how it is used in fuzzing.
    • Update any examples and command-line instructions to reflect the use of the "DAST" flag.
  4. Revise Wording:

    • Ensure that the overall wording of the documentation is updated to include "DAST" where relevant.
    • Make the language more user-friendly and accessible, incorporating feedback from Brendan's presentation.
  5. Review and Approve:

    • Share the updated documentation with relevant stakeholders, including Brendan, for review and approval.
    • Incorporate any feedback and make necessary revisions.
  6. Publish Updates:

    • Update the fuzzing documentation on the documentation site.
    • Ensure the changes are live and verify that the updated information is displayed correctly.

Acceptance Criteria:

  •  The fuzzing documentation is updated with insights and examples from Brendan's BSides presentation.
    
  •  The "DAST" flag is included in the documentation with clear explanations and examples.
    
  •  The wording throughout the documentation is revised to be user-friendly and include "DAST" where relevant.
    
  •  The updated documentation is reviewed, approved, and published on the site.
    
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant