Skip to content

Setup::Kits#new - offer more options to choose from#1503

Merged
caitmich merged 27 commits intorelease-5.0.0from
welcome/kits
Mar 20, 2026
Merged

Setup::Kits#new - offer more options to choose from#1503
caitmich merged 27 commits intorelease-5.0.0from
welcome/kits

Conversation

@etdsoft
Copy link
Copy Markdown
Member

@etdsoft etdsoft commented Jan 29, 2026

Summary

From a single Welcome kit to a variety of options to try things go. The goal is to let people see how Dradis can be configured for different assessment types.

Check List

  • Added a CHANGELOG entry
  • Commit message has a detailed description of what changed and why.

etdsoft and others added 20 commits January 29, 2026 10:13
Project and 3 HTML report variants
Makes the divider styles reusable across layouts by moving them from the
inline block in hera/modules.scss into hera/modules/_divider.scss, and
imports the module in setup/setup.scss so the divider is available in
the setup flow.
Assumes new users are inexperienced, so predefined kits are now the
primary options with a consistent horizontal layout. The no-kit "I got
this!" option moves to the bottom behind an "or" divider. Consolidates
btn-experience and btn-kit into a single class since they were always
used together.
add /create-addon skill for scaffolding new Dradis addon gems
The templates filtered for Type 'Conclusions' which doesn't exist in
the OWASP kit data. Replace with iteration over actual content block
types (Document Control, Engagement Overview, Key Findings, Risk
Posture, Recommendations, Appendix). Also normalize mixed CRLF/LF
line endings in owasp.zip to LF only.
Define the field schema for new issues (with Liquid-computed Risk and
Risk Score fields) and evidence entries in the OWASP kit.
New kit for adversary simulation assessments, showcasing a different
approach from Welcome (infrastructure/CVSS) and OWASP (webapp/Impact
x Likelihood). Uses direct severity assignment, ATT&CK tactic/technique
mapping, and detection status tracking.

Includes:
- 10 sample findings across 7 ATT&CK tactics
- Evidence with timestamps and host attribution
- MITRE ATT&CK methodology board (12 phases, progress distributed)
- Content blocks for Pro (Rules of Engagement through Appendix)
- Kill Chain Ops HTML report template (after-action briefing style)
- Issue and evidence note templates
kit_folder = Rails.root.join('lib', 'tasks', 'templates', 'welcome').to_s
logger = Log.new.info('Loading Welcome kit...')
when :owasp, :welcome
kit_folder = Rails.root.join('lib', 'tasks', 'templates', @kit.to_s)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We're converting the params from string to symbols (L46) then to string again here. What about skipping the symbols step entirely and just handle strings?

Copy link
Copy Markdown
Member Author

@etdsoft etdsoft Mar 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the only minimal advantage is the use of @kit in a case/when, having symbols as keys is slightly better than matching strings. If anyone in the review chain feels strongly, I don't mind either way.

@etdsoft etdsoft changed the base branch from develop to release-5.0.0 March 20, 2026 08:30
@caitmich caitmich merged commit 977c45b into release-5.0.0 Mar 20, 2026
2 checks passed
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

Successfully merging this pull request may close these issues.

4 participants