Loading
SPE - Block agent communication

Hi!

Have a question about blocking agent's communication with Snow Inventory server. I have an example for SPE version of Snow Software:

Case - there is the customer created in SMACC with a active agreement for SLM. Customer deploys inventory agents in his infrastructure for data gathering (AD, manual etc.).

Agents are configured to send data directly to the Master Server, not to the Service Gateway (base endpoint address is provided).

After customer agreement expiration, I will not be able to see data in SLM, but inventory agents still communicate with Master Server.

What are the best practises to cut off agent's communication with Master Server, to avoid population for Snow Inventory database? 

There are some ideas form my side:

  1. Use Service Gateway for each customer, and after customer's agreement expiration, ask to customer uninstall SG.
  2. Generate unique DNS names for each customer and use them in Master Server as an alternate endpoint.

Best regards,

Viktors


  • Although I'm happy that they've added the functionality within Inv Server, I have to say that the simplest way is to use dedicated DNS names for customers. This then stops the traffic to the server rather than the server receiving them and then deciding not to process them. We've done it this way from the start with our SPE environment for this very reason.
  • I believe the latest version of Snow Inventory Server (5.3.0 revision 336) has the ability to ignore/block SiteNames. I cant find the official release note Tom
    • Richard Warfvinge (Flexera Software)

      The way to do this is listed in the User Guide for Snow Inventory 5.3, section 8.3 regarding Site Name certificate authentication. Basically, by listing a site name in this configuration but omitting the fingerprint any inventory files with that site name will be deleted. If the site name is not in the list then it will always be accepted, so you only include (without certificate thumbprint) the site names you want to block. 
      Expand Post
  • Hi I discovered the same issue with old customers: Since all agents are configured to point to the same DNS no mater who the customer is, all the agents that are not uninstalled from the inventoried data will keep sending data to the inventory server. To solve this I did as you thought of in point 2: Generate unique DNS names for each customer and use them in Master Server as an alternate endpoint. I hope it helps Anouar Ben Jemia
    • Community Manager (Flexera Software)

      Hi Andreas, I have a correction on your post. Snow Inventory Server 5.3.0 is currently able to filter incoming data, but only for files, which come in via https. There is currently no possibility to block files via http. Please refer to PRB0041511, if you have further questions. /marcel
      • Hi Marcel, (PRB0041511) What is the situation right now (Feb 2020) with INV 6.x? The SiteNameAuthenticationList still works only with data coming in on the INV master server via HTTPS? That should explain why it doesn't work in my test. Or is the system case sensitive (upper/lowercase)? Thanks! Dirk
      • Hi Marcel, Thank you for the headsup. How would one go about multiple sites from one customer? COMPANY-NETHERLANDS COMPANY - GERMANY COMPANY - CHINA Could we simply use % like: <SiteNameAuthenticationList>   <Site SiteName="COMPANY% "></Site> </SiteNameAuthenticationList> Or should we define hem one by one like: <SiteNameAuthenticationList>   <Site SiteName="COMPANY-NETHERLANDS "> </Site>   <Site SiteName="COMPANY- GERMANY "> </Site>   <Site SiteName="COMPANY- CHINA "> </Site> </SiteNameAuthenticationList> Thanks in advance, Andreas
        Expand Post
  • Oliver Berger (Flexera Software)

    Hi Viktors, after key expiration, the Data will still be processed by Snow Inventory, but not by Snow License Manager any more. I don't think there are "Best Practices" established. Service Gateways requires bidirectional communication. So the customer would need to open his firewalls a tiny bit. At the very first, ask the Customer to stop sending you corporate data without underlying NDA or agreement or cause. Maybe the Company's CSO is the right person to ask, if this could be "accelerated".  Some more ideas: let the customer create a local dns alias pointing to your inventory server. removing it would help the customer to stop unwanted communication quick. one Service gateway per Customer in your environment one dedicated port per Customer in your Inventory Server Blocking the customers IP-Ranges in your firewalls. since a while, Inventory 5 is able to handle custom ssl keys to de/encrypt snowpack files. Create a key per customer, add it to the Client and the Server. Remove it at the server, if the customer quits, will stop processing it.  I definitely like removing a root cause, instead of fighting it's effects. Which means uninstalling the snow components provided, according to the agreement.  Best, Oliver
    Expand Post
10 of 13

Related  Product Forums


                     → Flexera One



                      → Snow Atlas



                      → FlexNet Manager



                      → Snow License Manager



                       → App Broker


       Need help finding an answer?


        Ask a Question →


Loading
SPE - Block agent communication