[{"_1":2,"_154":-5,"_155":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_133":134},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":-5,"_85":86,"_124":-5,"_125":11,"_126":17,"_127":11,"_128":-5,"_129":11,"_130":-5,"_131":132},"canonicalUrl","https://hub.docker.com/r/danielfett/yesses/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","danielfett","reponame","yesses","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":11,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2019-09-19T14:27:34.87994Z","description","","is_private","last_updated","2020-06-16T12:05:53.545321Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",253,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# yesses #\n\nSimple tool to enumerate domains and IPs and test those domains and\nIPs for basic network and web security properties.\n\nyesses provides a number of modules that each perform a certain task.\nFor example, the module `discover Domains and IPs` queries DNS servers\nfor IP addresses. Each module has a number of defined inputs (in this\ncase, for example, domain names) and outputs (e.g., IP addresses and\ndomain names expanded from CNAMEs). These outputs are called \"findings\".\n\nModules can be combined by feeding the findings of one module into the\ninput of another module. For example, the module `discover Webservers`\ncan use the domain names and IP addresses from `discover Domains and\nIPs` as inputs. This enables a dynamic scanning of infrastructures\nwithout configuring every domain name, IP address, etc. manually.\n\nAfter the execution of each module, alerts can be defined. Alerts can\ntrigger when certain elements are contained (or are not contained) in\nthe output of a module; alerts can also be triggered when — compared\nto the previous run of yesses — new elements appear in the output of a\nmodule. \n\nAlerts are processed by one or more user-defined outputs. yesses comes\nwith an HTML template output and Slack notification output.\n\n## TL;DR ##\n\nHave a look at the [example configuration file](docs/examples/example.yml). yesses uses a fairly human-readable syntax; most things should be self-explanatory. If not, read on! \n\n## Table of Contents ##\n\n * [Usage](#user-content-usage)\n * [Concepts](#user-content-concepts)\n * [Configuration File](#user-content-configuration-file)\n * [Discovery and Scanning Modules](#user-content-discovery-and-scanning-modules)\n * [Output Modules](#user-content-output-modules)\n\n# Usage #\n\n```\nusage: run.py [-h] [--config [CONFIG]] [--verbose] [--resume] [--repeat N]\n [--fresh] [--test] [--unittests] [--no-cache]\n [--generate-readme [PATH]]\n MODULE ...\n\nTool to scan for network and web security features\n\noptional arguments:\n -h, --help show this help message and exit\n --config [CONFIG], -c [CONFIG]\n Config file in yaml format. Required unless --test or\n --generate-readme are used.\n --verbose, -v Increase debug level to show debug messages.\n --resume, -r Resume scanning from existing resumefile.\n --repeat N Repeat last N steps of run (for debugging). Will\n inhibit warnings of duplicate output variables.\n --fresh, -f Do not use existing state files. Usage of this\n required when datastructures in this application\n changed.\n --test Run a self-test. This executes the examples contained\n in all modules.\n --unittests Run all tests which are defined in /tests/test_cases.\n --no-cache If '--unittests' is specified the test environment\n will be rebuild from scratch.\n --generate-readme [PATH]\n Run a self-test (as above) and generate the file\n README.md using the test results. Optional: path to\n write file to, defaults to location of this script.\n\nmodules:\n Run a module directly without configuration file. To get help on the usage\n of a module, run this command with 'MODULE --help'. Remember that module\n names must be in quotes or the space must be escaped.\n\n MODULE Available modules: 'scan Dnssec', 'scan Header\n Leakage', 'scan Information Leakage', 'scan Ports',\n 'scan TLS Settings', 'scan TLS Settings Qualys', 'scan\n Web Security Settings', 'discover Domains And IPs',\n 'discover Error Paths', 'discover Hidden Paths',\n 'discover Linked Paths', 'discover TLS Certificates',\n 'discover Webservers'\n\n```\n\n## Concepts ##\n\nA **run** of yesses consists of a call to one or more **modules**. A\nmodule, as described above, performs one or more checks. Each module\naccepts a custom set of input values and output values. The details\nfor each module are described below.\n\nThere exists a global dictionary of facts, or **findings** which can\nbe used as input for other modules or to create alerts based on rules\non the findings. At the start of the run, the findings dictionary is\nempty, but can be pre-filled with **static data** in the configuration\nfile, e.g., a list of domains to scan. When a module is called, **input\nvalues** can be taken from the findings dictionary (using the `use`\nkeyword).\n\nThe module produces an **output dictionary** containing the module's own\nfindings. Selected keys from this output dictionary can be merged into\nthe global findings dictionary. (If necessary, the keys can be\nre-named before merging to avoid collisions.)\n\n**Rules** can be defined on the new global findings dictionary to create\nalerts if necessary. Roughly speaking, these rules can check that (a)\ncertain dictionary keys do or do not contain entries, (b) no values\nhave been added or removed since the last run, or that (c) two lists\nof entries overlap fully or do not overlap at all.\n\nWhen rules are violated, **alerts** can be created. Alerts can have\nfour different severity levels. Alerts can then be used in the\n**output** of the run, either to create reports or for immediate\nnotifications.\n\n**Data** in the global findings list, and in inputs and outputs of\nmodules is loosely typed. This can be explained best using an example.\nThe following could be the global findings list after the `discover\nDomains and IPs` module was run:\n\n```YAML\nDNS-Entries:\n- domain: example.com\n ip: 93.184.216.34\n- domain: example.com\n ip: 2606:2800:220:1:248:1893:25c8:1946\nDomains:\n- domain: example.com\nIPs:\n- ip: 93.184.216.34\n- ip: 2606:2800:220:1:248:1893:25c8:1946\n```\n\nUnder each key in the global findings list, a list of entries can be\nfound. Each entry contains one or more keys (`domain` and/or\n`ip`). yesses expects that each member of a list contains the same\nkeys.\n\nWhen a module expects an input having certain keys (which can be found\nin the module description), inputs with additional keys can be used.\nFor example, the module `scan Ports` expects a range of IPs as input,\neach entry having the key `ip`. Therefore, `DNS-Entries` or `IPs`\ncould be used as inputs for `scan Ports`. E.g., given the above global\nfindings list, the following would be valid:\n\n```YAML\n - scan Ports:\n ips: use DNS-Entries\n (...)\n```\n\n\n## Configuration file ##\n\nAn example for a configuration file can be found in `docs/examples/example.yml`.\n\nyesses configuration files are YAML files (input and output values\nshown below and in the generated HTML files are shown in YAML syntax\nas well).\n\nConfiguration files should adhere to the following top-level structure:\n\n```YAML\ndata: # data: Predefined variables in the global findings list; can be used in the rest of the document\n Variable-Name: # Custom variable name\n - value: some-value # Custom variable values\n - value: another-value\n Another-Variable:\n\nrun: # run: List of steps to be run in each test\n - discover Step Name: # Step names are documented below\n step-specific: 42 # Variables here depend on the individual steps\n find: # find: What output values to merge into the global findings list\n - Finding1 as New-Var # rename output to something else before merging (avoid collisions)\n - Finding2\n expect: # expect: rules on the output to create alerts\n - no New-Var, otherwise alert high\n - some Finding2, otherwise alert medium\n \n - scan Another Step:\n some-value: use Finding2 and New-Var # re-use existing values from global findings\n\noutput: # output: one or more modules to create output\n - Template: # output module name\n filename: some-filename.html\n template: templates/html/main.j2\n \n```\n\n### `data` ###\n\n`data` is self-explanatory given the example above: It contains keys\nand respective values that make up the initial global findings list.\n\n### `run` ###\n\n`run` contains the steps that are executed, in the order defined here,\nwithin the yesses run. Each step is described using three keywords:\nthe step's identifier, `find`, and `expect`, as explained in the\nfollowing:\n\nThe **step's identifier** (like `scan Ports` or `discover Domains and\nIPs`). Valid keys can be found in the module description below. Under\nthis key, input values for the respective module are defined. The keys\nthat can be used here can be found in the module description. Each key\ncan either contain the literal input data (e.g.: `protocols: ['tcp']`,\nsee also the examples below) or a `use`-expression. These start with\nthe keyword `use` and contain on or more keys from the global findings\nlist (multiple keys are separated by \"and\"). Example: `use DNS-Names\nand My-Arbitrary-Input`.\n \n**`find`**: This key defines which output names (see module\ndescription) are merged into the global findings dictionary. Duplicate\nnames are not allowed, i.e., if a name already exists in the global\nfindings, an error message is shown. Keys can be renamed before\nmerging using an expression like `Key-Name as New-Key-Name`.\n \n**`expect`**: This key defines the alerts triggered after the specific\nstep. Rules can refer to any entry in the global findings dictionary,\ninclude the ones added by the step itself. Rules must adhere to one of the\nfollowing forms:\n\n 1. (no|some) [new] FINDINGS, otherwise alert (informative|medium|high|very high)\n 1. (no|some|all) FINDINGS1 in FINDINGS2, otherwise alert (informative|medium|high|very high)\n 1. FINDINGS1 [not] equals FINDINGS2, otherwise alert (informative|medium|high|very high)\n\nThe first form checks if findings exist (or do not exist). With the\n`new` keyword, it checks if, compared to the last run, additional\nentries have been found. yesses does this by creating a file with the\nextension `.state` that stores the findings of the last run. If this\nfile is deleted between runs, all findings will be reported as new.\n\nThe second form checks if there is some, no, or a complete overlap\nbetween the lists FINDINGS1 and FINDINGS2. Note that, if the entries\nin these list contain different set of keys, only keys common to both\nlists are matched.\n\nThe third form checks if the lists FINDINGS1 and FINDINGS2 contain the\nsame elements (in any order) and no extra elements.\n\n### `output` ###\n\n`output` defines what yesses does with the created alerts. See\n[below](#user-content-output-modules) for a list of available modules\nand their usage.\n\n# Discovery and Scanning Modules #\n\nThe following modules are currently provided by yesses. For each\nmodule, a short description in given plus a list of input and output\nfields. The field names can be used in the yaml configuration file. \n\n\n\n## `scan Dnssec` ##\nUse the DNSSEC Scanner Python package to check the DNSSEC configuration\n of domain names. The DNSSEC Scanner provides log, warning and error messages\n for the DNSSEC validation process.\n \n\n\n### Examples ###\n

show example(s)

\n\n#### Check DNSSEC configuration of dnssec-deployment.org ####\nConfiguration:\n```YAML\n - scan Dnssec:\n domains:\n - domain: dnssec-deployment.org\n find:\n - DNSSEC-Logs-Domains\n - DNSSEC-Warnings-Domains\n - DNSSEC-Errors-Domains\n - DNSSEC-Summary-Domains\n - DNSSEC-Other-Error-Domains\n\n```\nFindings returned:\n```YAML\nDNSSEC-Errors-Domains:\n- domain: dnssec-deployment.org\n errors: []\nDNSSEC-Logs-Domains:\n- domain: dnssec-deployment.org\n logs:\n - '. zone: KSK 20326 record validated, using DS 20326'\n - '. zone: DNSKEY 20326,33853,48903 record validated, using KSK 20326'\n - '. zone: org. DS 9795,9795 record validated, using ZSK 48903'\n - 'org. zone: KSK 9795 record validated, using DS 9795'\n - 'org. zone: DNSKEY 9795,17883,33209,37022 record validated, using KSK 9795'\n - 'org. zone: DNSKEY 9795,17883,33209,37022 record validated, using KSK 17883'\n - 'org. zone: DNSKEY 9795,17883,33209,37022 record validated, using ZSK 37022'\n - 'org. zone: dnssec-deployment.org. DS 47809 record validated, using ZSK 37022'\n - 'dnssec-deployment.org. zone: KSK 47809 record validated, using DS 47809'\n - 'dnssec-deployment.org. zone: DNSKEY 25218,47809,50850 record validated, using\n KSK 47809'\n - 'dnssec-deployment.org. zone: dnssec-deployment.org. A record validated, using\n ZSK 50850'\n - 'dnssec-deployment.org. zone: dnssec-deployment.org. NS record validated, using\n ZSK 50850'\n - 'dnssec-deployment.org. zone: dnssec-deployment.org. SOA record validated, using\n ZSK 50850'\n - 'dnssec-deployment.org. zone: dnssec-deployment.org. MX record validated, using\n ZSK 50850'\n - 'dnssec-deployment.org. zone: dnssec-deployment.org. TXT record validated, using\n ZSK 50850'\n - 'dnssec-deployment.org. zone: dnssec-deployment.org. NSEC record validated, using\n ZSK 50850'\n - 'dnssec-deployment.org. zone: dnssec-deployment.org. AAAA record validated, using\n ZSK 50850'\nDNSSEC-Other-Error-Domains: []\nDNSSEC-Summary-Domains:\n- domain: dnssec-deployment.org\n note: 'Found RR sets: A, NS, SOA, MX, TXT, NSEC, AAAA'\n status: 0\nDNSSEC-Warnings-Domains:\n- domain: dnssec-deployment.org\n warnings: []\n\n```\n\n\n\n\n

\n\n### Inputs ###\n\n| Name | Description | Required keys |\n|------------------|----------------|----------------------------------------------------------|\n| `domains` (required) | List of domain names to scan their DNSSEC configuration. | `domain` |\n| `parallel_requests` | Number of parallel DNSSEC scan commands to run. | |\n\n\n\n\n#### Default for `parallel_requests` ####\n```YAML\n10\n```\n\n\n\n### Outputs ###\n\n| Name | Description | Provided keys |\n|------------------|----------------|----------------------------------------------------------|\n| `DNSSEC-Logs-Domains` | Log messages for the verification process of each domain. | `domain`, `logs` |\n| `DNSSEC-Warnings-Domains` | Warning messages for the verification process of each domain. | `domain`, `warnings` |\n| `DNSSEC-Errors-Domains` | Error messages for the verification process of each domain. | `domain`, `errors` |\n| `DNSSEC-Summary-Domains` | DNSSEC status (0=SECURE|1=INSECURE|2=BOGUS) and a note for the found RR sets. | `domain`, `status`, `note` |\n| `DNSSEC-Other-Error-Domains` | Domains that could not be scan because fo some error. `error` contains the error description. | `domain`, `error` |\n\n\n\n## `scan HeaderLeakage` ##\nThis module searches for potentially sensitive much information in\nHTTP headers. It checks if the 'Server' attribute contains too much\ninformation and if the 'X-Powered-By' and/or the 'X-AspNet-Version'\nattribute is set.\n\n \n\n\n\n\n\n### Inputs ###\n\n| Name | Description | Required keys |\n|------------------|----------------|----------------------------------------------------------|\n| `pages` (required) | Required. URLs with headers to search for information leakage. | `url`, `header` |\n\n\n\n\n\n### Outputs ###\n\n| Name | Description | Provided keys |\n|------------------|----------------|----------------------------------------------------------|\n| `Leakages` | Potential information leakages. | `url`, `header` |\n\n\n\n## `scan InformationLeakage` ##\nScan HTML, JavaScript and CSS files for information leakages. This\nis done by a search with regular expressions for email and IP\naddresses and strings that look like paths in the visible text of a\nHTML site or in HTML, JavaScript and CSS comments. For paths, there is\nalso a list of common directories to determine whether a path is a\nreal path or not. Furthermore, there is a list with common file\nendings to check if a path ends with a file name or a string is a file\nname. All the regex expressions are searching only for strings that\nare either at the beginning or end of a line or which have whitespace\nbefore or after.\n\n \n\n\n### Examples ###\n

show example(s)

\n\n#### Check example strings for information leakage ####\nConfiguration:\n```YAML\n - scan Information Leakage:\n pages:\n - url: page0\n data: \"\n\n\n\n \n\n

Title

\n\n

Text with path /home/user/secret/key.pub

Website 192.168.2.196 /usr/share/docs/ajdlkf/adjfl\n\n\n\n\"\n - url: page1\n data: \"

bla Gitea Version: 1.11.0+dev-180-gd5b1e6bc5

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\"\n - url: page2\n data: \"/*! modernizr 3.6.0 (Custom Build) | MIT *\n\n* https://modernizr.com/download/?-svgclippaths-setclasses !*/ \n\n!function(e,n,s){function o(e) // Comment three\n\n{var n=f.className,s=Modernizr._con /* Last \n\n multi \n\n line \n\n comment */ flakjdlfjldjfl\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\"\n search_regex:\n - type: new_regex\n regex: (^|\\s)a{3}(\\s|$)\n find:\n - Leakages\n \n```\nFindings returned:\n```YAML\nLeakages:\n- finding: 192.168.2.196\n found: visible_text\n type: ip\n url: page0\n- finding: /home/user/secret/key.pub\n found: visible_text\n type: path\n url: page0\n- finding: /usr/share/docs/ajdlkf/adjfl\n found: visible_text\n type: path\n url: page0\n- finding: test@example.com\n found: html_comment\n type: email\n url: page0\n- finding: /var/home/bla\n found: html_comment\n type: path\n url: page0\n- finding: aaa\n found: html_comment\n type: new_regex\n url: page0\n- finding: secret.txt\n found: html_comment\n type: file\n url: page0\n- finding: 'Version: 1.11.0'\n found: visible_text\n type: version-info\n url: page1\n\n```\n\n\n\n\n

\n\n### Inputs ###\n\n| Name | Description | Required keys |\n|------------------|----------------|----------------------------------------------------------|\n| `pages` (required) | Required. Pages to search for information leakage. | `url`, `data` |\n| `search_regex` | Own regular expression to search in pages (will be added to the existing ones). | `type`, `regex` |\n| `dir_list` | List with common directories to determine whether a string is a path. | |\n| `file_ending_list` | List with common file endings to determine whether a string is a file name. | |\n\n\n\n\n#### Default for `search_regex` ####\n```YAML\n{}\n```\n\n\n#### Default for `dir_list` ####\n```YAML\nassets/information_leakage/common-directories.txt\n```\n\n\n#### Default for `file_ending_list` ####\n```YAML\nassets/information_leakage/common-file-endings.txt\n```\n\n\n\n### Outputs ###\n\n| Name | Description | Provided keys |\n|------------------|----------------|----------------------------------------------------------|\n| `Leakages` | Potential information leakages | `url`, `type`, `found`, `finding` |\n\n\n\n## `scan Ports` ##\nUses `nmap` to scan for open ports.\n \n\n\n### Examples ###\n

show example(s)

\n\n#### scan ports on Google DNS server ####\nConfiguration:\n```YAML\n - scan Ports:\n ips: \n - ip: '8.8.8.8'\n protocols: ['tcp']\n find:\n - Host-Ports\n - HTTPS-Ports\n - Other-Port-IPs\n expect:\n - no Host-Ports, otherwise alert high\n \n```\nFindings returned:\n```YAML\nHTTPS-Ports:\n- &id001\n ip: 8.8.8.8\n port: 443\n protocol: tcp\nHost-Ports:\n- ip: 8.8.8.8\n port: 53\n protocol: tcp\n- *id001\nOther-Port-IPs:\n- ip: 8.8.8.8\n\n```\nAlerts created (details hidden for brevity):\n\n| Severity | Rule | #Findings |\n|----------|------|-----------|\n| AlertSeverity.HIGH | `no Host-Ports, otherwise alert high` | 1 |\n\n\n\n\n\n

\n\n### Inputs ###\n\n| Name | Description | Required keys |\n|------------------|----------------|----------------------------------------------------------|\n| `ips` (required) | Required. IP range to scan (e.g., `use IPs`). | `ip` |\n| `protocols` | List of protocols (`udp`, `tcp`,...) in nmap's notations to scan. | |\n| `ports` | Port range in nmap notation (e.g., '22,80,443-445'); default (None): 1000 most common ports as defined by nmap. | |\n| `named_ports` | A mapping of names to ports. This can be used to control the output of this module. | `name`, `port` |\n| `protocol_arguments` | Command-line arguments to provide to nmap when scanning for a specific protocol. | `protocol`, `arguments` |\n\n\n\n\n#### Default for `protocols` ####\n```YAML\n- tcp\n```\n\n\n#### Default for `ports` ####\n```YAML\nnull\n```\n\n\n#### Default for `named_ports` ####\n```YAML\n- name: SSH\n port: 22\n- name: HTTP\n port: 80\n- name: HTTPS\n port: 443\n```\n\n\n#### Default for `protocol_arguments` ####\n```YAML\n- arguments: -sU\n protocol: udp\n- arguments: -sT\n protocol: tcp\n```\n\n\n\n### Outputs ###\n\n| Name | Description | Provided keys |\n|------------------|----------------|----------------------------------------------------------|\n| `Host-Ports` | Each open port on a scanned IP (with IP, protocol, and port). | `ip`, `protocol`, `port` |\n| `*-Ports` | For certain protocols (SSH, HTTP, HTTPS), a list of hosts that have this port open (with IP, protocol, and port). | `ip`, `protocol`, `port` |\n| `Other-Port-IPs` | List of IPs that have any other ports open. | |\n\n\n\n## `scan TLSSettings` ##\nUses the sslyze library to scan a webserver's TLS configuration and\ncompare it to the Mozilla TLS configuration profiles.\n\n \n\n\n### Examples ###\n

show example(s)

\n\n#### Check TLS settings on badssl.com ####\nConfiguration:\n```YAML\n - scan TLS Settings:\n domains:\n - domain: mozilla-intermediate.badssl.com\n tls_profile: intermediate\n find:\n - TLS-Profile-Mismatch-Domains\n - TLS-Validation-Fail-Domains\n - TLS-Certificate-Warnings-Domains\n - TLS-Vulnerability-Domains\n - TLS-Okay-Domains\n - TLS-Other-Error-Domains\n expect:\n - some TLS-Okay-Domains, otherwise alert medium\n\n```\nFindings returned:\n```YAML\nTLS-Certificate-Warnings-Domains: []\nTLS-Okay-Domains: []\nTLS-Other-Error-Domains: []\nTLS-Profile-Mismatch-Domains:\n- domain: mozilla-intermediate.badssl.com\n errors:\n - must not support TLSv1\n - must not support TLSv1.1\n - must support TLSv1.3\n - client must choose the cipher suite, not the server (Protocol TLSv1)\n - client must choose the cipher suite, not the server (Protocol TLSv1.1)\n - client must choose the cipher suite, not the server (Protocol TLSv1.2)\n - must not support ECDHE-RSA-AES128-SHA\n - must not support AES256-SHA\n - must not support AES256-GCM-SHA384\n - must not support ECDHE-RSA-AES128-SHA256\n - must not support DES-CBC3-SHA\n - must not support ECDHE-RSA-DES-CBC3-SHA\n - must not support DHE-RSA-AES128-SHA256\n - must not support DHE-RSA-DES-CBC3-SHA\n - must not support DHE-RSA-AES256-SHA\n - must not support EDH-RSA-DES-CBC3-SHA\n - must not support AES128-SHA256\n - must not support AES128-GCM-SHA256\n - must not support ECDHE-RSA-AES256-SHA\n - must not support DHE-RSA-AES128-SHA\n - must not support AES128-SHA\n - must not support ECDHE-RSA-AES256-SHA384\n - must not support AES256-SHA256\n - must not support DHE-RSA-AES256-SHA256\n - must support TLS_AES_128_GCM_SHA256\n - must support ECDHE-RSA-CHACHA20-POLY1305\n - must support TLS_AES_256_GCM_SHA384\n - must support TLS_CHACHA20_POLY1305_SHA256\n - HSTS header not set\n - certificate lifespan too long (is 785, should be less than 730)\n - OCSP stapling must be supported\nTLS-Validation-Fail-Domains: []\nTLS-Vulnerability-Domains: []\n\n```\nAlerts created (details hidden for brevity):\n\n| Severity | Rule | #Findings |\n|----------|------|-----------|\n| AlertSeverity.MEDIUM | `some TLS-Okay-Domains, otherwise alert medium` | 0 |\n\n\n\n\n\n

\n\n### Inputs ###\n\n| Name | Description | Required keys |\n|------------------|----------------|----------------------------------------------------------|\n| `domains` (required) | List of domain names to scan. | `domain` |\n| `tls_profile` | The Mozilla TLS profile to test against (`old`, `intermediate`, or `modern`). | |\n| `ca_file` | Path to a trusted custom root certificates ","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",3416153638,"orgData","recentTags",[87],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_46":113,"_114":90,"_115":29,"_116":52,"_53":117,"_118":119,"_120":104,"_121":113,"_122":62,"_123":17},"content_type","creator",7687917,"full_size",110161787,"id",69400357,"images",[97],{"_98":99,"_100":101,"_102":44,"_103":104,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":92,"_59":62,"_112":-5},"architecture","amd64","digest","sha256:269b5dbe71dfe99eefd36e4e4d61e727f00d289174fe019cc5e717b24ba1e4c4","features","last_pulled","2026-09-23T15:12:17.10948636Z","last_pushed","2020-06-16T12:05:53Z","os","linux","os_features","os_version","size","variant","2020-06-16T12:05:52.930291Z","last_updater","last_updater_username","media_type","latest","repository",7725712,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":135,"_142":143,"_131":152,"_153":11},{"_36":136,"_38":137,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":138,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":139,"_75":11,"_76":141,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":140},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_144":60,"_145":-5,"_146":-5,"_147":148},"count","next","previous","results",[149],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":150,"_46":113,"_114":90,"_115":29,"_116":52,"_53":117,"_118":119,"_120":104,"_121":113,"_122":62,"_123":17},[151],{"_98":99,"_100":101,"_102":44,"_103":104,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":92,"_59":62,"_112":-5},[],"canDeleteTags","actionData","errors"]

danielfett/yesses

Tags for danielfett/yesses