Company-Provided Assets: Messages, Reasons, & Statuses Ingrid Assets can be added from the Infrastructure page (add asset). The source of added assets are considered to be “company-provided.” They also include the following details: Messages A message is displayed in the Company-Provided Assets page when an error or failed validation occurs. It can be one of the following: Message Instructions Shell companies cannot have infrastructure directly associated with them You tried to add infrastructure to a shell company, which cannot have infrastructure directly associated with them. Select another company in the ratings tree that has at least one domain or IP/CIDR. Active CIDR already exists in the company you selected Infrastructure is already attributed. For more details, please reach out to Bitsight Support. Active domain already exists in the company you selected Active CIDR already exists in a different organization Active domain already exists in a different organization Domain request limit reached Please try requesting smaller portions of the infrastructure (e.g. a smaller CIDR block with fewer IP addresses). IPV4 CIDRs request limit reached IPV6 CIDRs request limit reached IPV4 CIDRs daily request limit reached Please try again on a different day. IPV6 CIDRs daily request limit reached IPV4 CIDRs entity request limit reached Your company-provided asset has reached a limit. For more details, please reach out to Bitsight Support. IPV6 CIDRs entity request limit reached Error adding CIDR (Internal error) Please try again later. Could not create CIDRs Invalid company guid (API only) Use the company unique identifier [entity_guid] of an entity you have access to. Invalid domain name (API only) Check the domain name and try again. Reasons Field Slug Name Development/Testing infrastructure dev Office assets office Dynamically scaled cloud assets cloud Publicly visible backend systems pub Other other Statuses Field Description Pending The request was submitted and is being validated. Error The validation has failed. Added The request was successfully completed. The new infrastructure is visible in the Attribution tab. Expired The request exceeded the maximum time for processing. The infrastructure was not added. April 20, 2023: Help and troubleshooting. March 31, 2023: Published. Related articles Control and Responsibility for IP Addresses and Domains Attack Surface: Infrastructure Self-Published Companies Infrastructure Management Finding Behavior Feedback 2 comments Sort by Date Votes Allen Shymchuk May 26, 2026 20:25 From the GUI, when adding a new asset the REASON drop-down appears to be MANDATORY and displays… Development/Testing infrastructure Office assets Dynamically scaled cloud assets Publicly visible backend systems Other Suggested Infrastructure … what is ‘Suggested Infrastructure’… and what is it's SLUG NAME?Are we allowed to add our own… could that explain why this is NOT in your list above?Is there a site-side switch that makes REASON mandatory when adding new assets?Thank you. 0 Allen Shymchuk May 29, 2026 17:55 I have answered part of my question…The (mandatory) REASON for using the API to POST Assets accepts the (undocumented) slug ‘suggested’ for Suggested Infrastructure.https://help.bitsighttech.com/hc/en-us/articles/12330523659159-POST-Add-Assets-in-Bulk#request-add-assetsThank you. 0 Please sign in to leave a comment.