ATTENTION Customers, All Partners and Employees: The Customer Support Portal (CSP) will be undergoing maintenance and unavailable on Saturday, November 7, 2020, from 11 am to 11 pm PST. Please read our blog for more information.
After some help I was able to get this going. 1. I used the miner prototype azure.cloudIPs to begin 2. Created new processor from stdlib.aggregatorIPv4Generic 3. Modified the new processor config to filter (infilter) which azure regions I needed (in my case uswest and uswest2) I posted code at the bottom of this post. 4. Build output node using prototype stdlib.feedHCGreenWithValue 5. Connected miner to modified processor then to output Currently the miner has 2595 Indicators but after going through processor output node has 326. I crosschecked against the Azure XML file and is correct Code is below
... View more
age_out: default: null interval: 257 sudden_death: true attributes: share_level: green infilters: - actions: - accept conditions: - __method == 'withdraw' name: accept withdraws - actions: - accept conditions: - type == 'IPv4' - Region Name == 'uswest' - actions: - accept conditions: - type == 'IPv4' - Region Name == 'uswest2' - actions: - drop name: drop all The above doesn't seem to work, although I'm trying to follow ->https://live.paloaltonetworks.com/t5/MineMeld-Discussions/Filtering-Azure-IP-ranges-based-on-a-subset-of-regions/td-p/193368 Any help is appreciated, I've broke my Minemeld twice in two days now. Thanks
... View more