base on A Workflow Engine for Offensive Security # Osmedeus Core Engine <p align="center"> <a href="https://www.osmedeus.org"><img alt="Osmedeus" src="https://raw.githubusercontent.com/osmedeus/assets/main/logo-transparent.png" height="140" /></a> <br /> <strong>Osmedeus - A Workflow Engine for Offensive Security</strong> <p align="center"> <a href="https://docs.osmedeus.org/"><img src="https://img.shields.io/badge/Documentation-0078D4?style=for-the-badge&logo=GitBook&logoColor=39ff14&labelColor=black&color=black"></a> <a href="https://docs.osmedeus.org/donation/"><img src="https://img.shields.io/badge/Sponsors-0078D4?style=for-the-badge&logo=GitHub-Sponsors&logoColor=39ff14&labelColor=black&color=black"></a> <a href="https://twitter.com/OsmedeusEngine"><img src="https://img.shields.io/badge/%40OsmedeusEngine-0078D4?style=for-the-badge&logo=Twitter&logoColor=39ff14&labelColor=black&color=black"></a> <a href="https://discord.gg/gy4SWhpaPU"><img src="https://img.shields.io/badge/Discord%20Server-0078D4?style=for-the-badge&logo=Discord&logoColor=39ff14&labelColor=black&color=black"></a> <a href="https://github.com/j3ssie/osmedeus/releases"><img src="https://img.shields.io/github/release/j3ssie/osmedeus?style=for-the-badge&labelColor=black&color=2fc414&logo=Github"></a> </p> </p> *** ## 🔥 What is Osmedeus? Osmedeus is a Workflow Engine for Offensive Security. It was designed to build a foundation with the capability and flexibility that allows you to build your own reconnaissance system and run it on a large number of targets. ## 📖 Documentation & FAQ You can check out the documentation at [**docs.osmedeus.org**](https://docs.osmedeus.org) and the Frequently Asked Questions at [**here**](https://docs.osmedeus.org/faq) for more information. ## 📦 Installation > NOTE that you need some essential tools like `curl, wget, git, zip` and login as **root** to start ```bash bash <(curl -fsSL https://raw.githubusercontent.com/osmedeus/osmedeus-base/master/install.sh) ``` ### Build the engine from the source Make sure you installed `golang >= v1.17` ```bash go install -v github.com/j3ssie/osmedeus@latest ``` Check out [**this page**](https://docs.osmedeus.org/installation/) for more the install on other platforms and [**docker image**](https://docs.osmedeus.org/installation/using-docker/). ## 🚀 Key Features of Osmedeus - [x] Significantly speed up your recon process - [x] Organize your scan results - [x] Efficiently to customize and optimize your recon process - [x] Seamlessly integrate with new public and private tools - [x] Easy to scale across large number of targets - [x] Easy to synchronize the results across many places ## 💡 Usage ```bash # Example Scan Commands: ## Start a simple scan with default 'general' flow osmedeus scan -t sample.com ## Start a general scan but exclude some of the module osmedeus scan -t sample.com -x screenshot -x spider ## Start a scan directly with a module with inputs as a list of http domains like this https://sub.example.com osmedeus scan -m content-discovery -t http-file.txt ## Initiate the scan using a speed option other than the default setting osmedeus scan -f vuln --tactic gently -t sample.com osmedeus scan --threads-hold=10 -t sample.com osmedeus scan -B 5 -t sample.com ## Start a simple scan with other flow osmedeus scan -f vuln -t sample.com osmedeus scan -f extensive -t sample.com -t another.com osmedeus scan -f urls -t list-of-urls.txt ## Scan list of targets osmedeus scan -T list_of_targets.txt osmedeus scan -f vuln -T list-of-targets.txt ## Performing static vulnerability scan and secret scan on a git repo osmedeus scan -m repo-scan -t https://github.com/j3ssie/sample-repo osmedeus scan -m repo-scan -t /tmp/source-code-folder osmedeus scan -m repo-scan -T list-of-repo.txt ## Scan for CIDR with file contains CIDR with the format '1.2.3.4/24' osmedeus scan -f cidr -t list-of-ciders.txt osmedeus scan -f cidr -t '1.2.3.4/24' # this will auto convert the single input to the file and run ## Directly run on vuln scan and directory scan on list of domains osmedeus scan -f domains -t list-of-domains.txt osmedeus scan -f vuln-and-dirb -t list-of-domains.txt ## Use a custom wordlist osmedeus scan -t sample.com -p 'wordlists={{Data}}/wordlists/content/big.txt' ## Use a custom wordlist cat list_of_targets.txt | osmedeus scan -c 2 ## Start a normal scan and backup entire workflow folder to the backup folder osmedeus scan --backup -f domains -t list-of-subdomains.txt ## Start the scan with chunk inputs to review the output way more much faster osmedeus scan --chunk --chunk-parts 20 -f cidr -t list-of-100-cidr.txt ## Continuously run the scan on a target right after it finished osmedeus utils cron --for --cmd 'osmedeus scan -t example.com' ## Backing up all workspaces ls ~/workspaces-osmedeus | osmedeus report compress # Scan Usage: osmedeus scan -f [flowName] -t [target] osmedeus scan -m [modulePath] -T [targetsFile] osmedeus scan -f /path/to/flow.yaml -t [target] osmedeus scan -m /path/to/module.yaml -t [target] --params 'port=9200' osmedeus scan -m /path/to/module.yaml -t [target] -l /tmp/log.log osmedeus scan --tactic aggressive -m module -t [target] cat targets | osmedeus scan -f sample # Practical Scan Usage: osmedeus scan -T list_of_targets.txt -W custom_workspaces osmedeus scan -t target.com -w workspace_name --debug osmedeus scan -f general -t sample.com osmedeus scan --tactic aggressive -f general -t sample.com osmedeus scan -f extensive -t sample.com -t another.com cat list_of_urls.txt | osmedeus scan -f urls osmedeus scan --threads-hold=15 -f cidr -t 1.2.3.4/24 osmedeus scan -m ~/.osmedeus/core/workflow/test/dirbscan.yaml -t list_of_urls.txt osmedeus scan --wfFolder ~/custom-workflow/ -f your-custom-workflow -t list_of_urls.txt osmedeus scan --chunk --chunk-part 40 -c 2 -f cidr -t list-of-cidr.txt 💡 For full help message, please run: osmedeus --hh or osmedeus scan --hh 📖 Documentation can be found here: https://docs.osmedeus.org ``` Check out [**this page**](https://docs.osmedeus.org/installation/usage/) for full usage and the [**Practical Usage**](https://docs.osmedeus.org/installation/practical-usage/) to see how to use Osmedeus in a practical way. ## 💬 Community & Discussion Join Our Discord server [here](https://discord.gg/mtQG2FQsYA) ## License `Osmedeus` is made with ♥ by [@j3ssiejjj](https://twitter.com/j3ssiejjj) and it is released under the MIT license. ", Assign "at most 3 tags" to the expected json: {"id":"14568","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"