Skip to main content

Hello everyone,

We have encountered a challenging requirement during our discovery scans for a range of IP addresses. In the scan results, some assets appear with their asset names as IP addresses instead of hostnames.

We need to filter out these assets and prevent them from being added to Password Safe. Does anyone know how we can filter out assets without hostnames that are still being added to Password Safe?

 

Thank you,

Prasad

Hey ​@prasadp87 - the scan will return all assets that exist, but they wouldn’t be onboarded as a managed system unless there is a smart rule to do so. 

 

There’s a few general notes I can recommend, but the implementation does depend on the architecture set up. (Mandatory disclosure note: If full support of modifying your specific environment is desired, that would be the realm of professional services.)

 

General Notes

Refine Discovery Scan

I would recommend investigating the IPs rather than hostnames (e.g. windows scan expected but it’s a linux device, etc.) to refine the discovery scan to be more effective to only bring online systems that are anticipated.

 

Smart Rule Targets

You can tag the assets that match the regex for an IPv4 address with an attribute (or show as smart group) and exclude that attribute (or smart group if you choose to show as smart group) from onboarding as a managed system.

Asset Smart Rule: Asset Name matches RegEx for an IPv4 Address.

 

The target smart group members:

Results of a Smart Rule that targets IPv4 addresses

 


Hello ​@prasadp87 

 

You can use a regular expression. 

This one worked for me.

^(?!^(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)$).*
 

 

Regards,

John