Skip to content

Instantly share code, notes, and snippets.

@kingthorin
Last active August 22, 2019 14:16
Show Gist options
  • Save kingthorin/469cb6cc0f9a915fbf382b6c8a1abeb2 to your computer and use it in GitHub Desktop.
Save kingthorin/469cb6cc0f9a915fbf382b6c8a1abeb2 to your computer and use it in GitHub Desktop.

Requirement > We need icons to represent:

  • Primary Requirement:
    • websocket passive scripts
    • websocket active scripts
  • Secondary requirement:
    • websocket passive scanning
    • websocket active scanning

Summary > Icons should fit into Zap's overall feel and only need to be low res/size versions. The script icons should combine the background script (scroll) icon with something that combines the concept of the main component (websocket [plug icon]) and facilitated component (passive scan/active scan). The icons "could" be based simply on the latter two elements if that is necessary for visual clarity (similar to the HUD radar icon). Here's a screenshot of Zap's UI and the other existing script icons to help illustrate things. [As for ideas/inspiration I guess it's worth noting the difference is the passive scan eye (used straight on) vs the script eye element (side view).]

Zap GUI
(Original size png here: https://www.owasp.org/images/b/bc/ZAP-ScreenShotSearchTab.png)

Script icons

is the icon we use for passive scanning.

is the icon we use for the WebSockets tab.

is the icon we use for the active scanner.

The greater selection of ZAP icons is here:

In the past we've drawn heavily upon:

Script icons:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment