Managing Domains

in scope and out of scope domains hexiosec asm uses 'in scope' and 'out of scope' to control how much of an attack surface to scan since everything on the internet is connected, we need to ensure the scope of a hexiosec asm scan is appropriately focussed 'in scope' nodes, be they domains, ip addresses, components, etc , are connected back to one of the seed nodes via a valid path a subdomain (or child) of a seed domain will be in scope however, the domain of a 3rd party script used on the seed domain's website will be 'out of scope' simply put, if it is 'in scope', then hexiosec asm has determined that the risks associated with the asset are your responsibility if it is out of scope, then hexiosec asm can't be sure it is yours, and you will need to add it as a seed to get hexiosec asm to inspect it further to view the 'out of scope' nodes, go to the 'out of scope' page on a scan, and you can add nodes to scope as seeds note, this will depend on permissions csv file export this feature is not available to all license plans, please contact us if you would like to discuss adding this feature to your hexiosec asm account to enable you to extract information related to in scope domains found in a scan, including dns data, risks, asns, cloud hosting and certificates, hexiosec asm provides an export button on the domains page data is exported as a csv (comma separated values) file, which uses , as the cell separator the file includes an initial heading row the exported data will match the data you currently have filtered in the app to export a selection of the domains, e g domains related to a certain asn, simply apply the filter before using the export button the generated csv file outputs the following columns "id","domain","stale","name server","seed","dns destination","services","certificates","cloud regions","asns","entities","critical risks","high risks","medium risks","low risks" id "\<domain id>" the domain id domain "\<domain>" the domain name stale "\<yes|no>" if the domain is stale (see report terminology ) name server "\<yes|no>" if the domain is a dns name server seed "\<yes|no>" if the domain is a seed dns destination "\<ip|domain>,\<ip|domain>, " \[0 or more values] either ip addresses for dns a records associated with the domain domains for dns cnames associated with the domain services "\<domain\ port>,\<domain\ port>, " \[0 or more values] services on the domain certificates "\<certificate>,\<certificate>, " \[0 or more values] certificates used by the domain cloud regions "\<cloud region>,\<cloud region>, " \[0 or more values] cloud regions for any associated cloud providers asns "\<asn>,\<asn>, " \[0 or more values] asn (autonomous system number) network names entities "\<entity>|\<entity>, " \[0 or more values] names of entities responsible for the asns critical risks "\<risk count>" count of critical risks associated with the domain high risks "\<risk count>" count of high risks associated with the domain medium risks "\<risk count>" count of medium risks associated with the domain low risks "\<risk count>" count of low risks associated with the domain