Twigs requires user details to connect to your ThreatWorx instance during the discovery process. You can use one of the three options below to initialize twigs. Option 1 twigs provides “login” and “logout” capability. This allows users to authenticate via twigs to their ThreatWorx service instance

Twigs cloud native images are currently available for AWS, docker hub and Digital Ocean marketplaces. These images are free to download and use and are built and maintained by ThreatWorx to contain all the requirements and dependencies of twigs including any native CLI or other open source dependenc

Twigs command-line usage Please refer to twigs documentation for command-line usage Twigs source code Twigs is open source. If you are interested in going through the source code of twigs, you can find it here. Twigs is a python-based package and can be installed using ‘pip’ as below: sudo pip ins

Twigs provides a bunch of common options i.e. irrespective of what type of assets are being discovered. These common options are optional as seen below: twigs [-h] [-v] [--handle HANDLE] [--token TOKEN] [--instance INSTANCE] [--run_id RUN_ID][--location LOCATION] [--tag_critical] [--tag TAG] [--n

Twigs can discover various classes of assets as below: • Cloud assets from AWS, Azure and GCP • Docker containers • Import assets from a file (PDF or JSON) • Servers, desktops, laptops etc. • Source code repository • Ingest existing assets details from CMDB like ServiceNow, etc. Twigs suppor