DAST: Explore ways to clarify "Active" and "Passive" scan mode badges

Insight

Users misinterpret the “Active” scan mode value, thinking it represents that the scan is enabled.

Supporting evidence

The meaning of “Active” and “Passive” scan mode is not clear to some users. It's assumed that “Active” implies that the profile is being used.

🕊 Dovetail Insight (DAST config)

Passive? Scan mode, passive. It doesn't say "in use", I guess it hasn't taken effect immediately but in a while it's going to be applied... I will be waiting for it (the profile) to be "active".

🕊 Dovetail Insight (DAST Viable CMS)

It's a little weird, the scan is "active" but I can still run it. I guess it schedules it again?

Action

Explore ways to minimize the point of confusion

Resources

• 🕊 Dovetail project
• 🔍 Research issue 1
• 🔍 Research issue 1

Tasks

• Assign this issue to the appropriate Product Manager, Product Designer, or UX Researcher.
• Add the appropriate Group (such as ~"group::source code") label to the issue. This helps identify and track actionable insights at the group level.
• Link this issue back to the original research issue in the GitLab UX Research project and the Dovetail project.
• Adjust confidentiality of this issue if applicable