How to Use Palo Alto Networks New-Feature Request

[kiwi]

 Did you know that you can request new features? If you notice a missing functionality or are in need of an enhancement, here's what to do.

Have you ever found yourself in a situation where you want to test or configure something specific on your device, only to find out that it's not supported (yet)? I know I have—and I'm certain many of you have, too. In fact, the two most-replied-to discussions on LIVEcommunity are:

• Feature Request Link 
• What Is Still Missing Or Needs To Be Improved In PA Next Generation Firewalls 

If you find yourself in a similar situation, you can reach out to your Palo Alto Networks representative. You'll send them all the details about the feature in question, and they'll take the necessary steps to have a Feature Request created for you. They'll give you a Feature Request ID (FRID). Each FRID can then be voted on by other Palo Alto Networks customers. Based on urgency, number of votes, and other factors, PAN will then decide which new features will be considered for new software and/or hardware releases.

The official FRID-list from Palo Alto Networks isn't publicly available, but @Remo created a very nice list of current publicly known FRIDs. So, instead of immediately reaching out to your local SE, you can browse the list and its replies to find your item, and then add your vote to it. Currently, you can't add your vote yourself—that must be done through your local Palo Alto Networks sales rep.

Do you have an ID that you would like other customers to add their vote on? Feel free to promote your FRID in the discussions area and ask others to up-vote your request.

PAN-OS is already a feature rich firewall operating system, however there's always room for improvement, for example:

• You've noticed that your firewall doesn't have an extendable umbrella to protect you from rain in your datacenter 
• Each time the firewall blocks a threat, it should be able to play the purge siren to let you and your management know it is doing a great job (thanks @reaper for this much-needed feature)
  

So there it is! Now you know the process for requesting new features for a more secure future. Are there other features you would like to see? Do you have FRIDs that you would like to promote, so others can vote on them? Feel free to add them to the comments section below or go to discussion topics I mentioned earlier.

Thank you for taking time to read this blog! Don't forget to hit the Like (thumbs up) button and to Subscribe to the LIVEcommunity Blog area.

Kiwi out!

[bmarks]

I would like to request a feature on behalf of several clients using GlobalProtect. SSL VPNs in the past (e.g. JUNOS Pulse & Pulse Secure) have integrated the ability to pass-thru ActiveDirectory Password Management & Expiration Notifications through the VPN Client on the Endpoint. This does not appear to be a feature of GlobalProtect. I have a client using LDAPS with GlobalProtect in an ALWAYS ON situation Internal & External to the LAN. Their users are required to change AD passwords every 90 days, and they end up locking their accounts. GP Authentication Override is unaware of the change and caches the previous password for 24 hrs. Turning off SSO is not an option, makes the VPN completely unusable. Is there a FR already submitted? Is this feature on the roadmap? Any update on this would be must helpful. Appreciated!!

[ChristianOCD]

Hello,

I would like to request a feature to support path monitoring of DHCP type interfaces.

If the customer is using multiple WAN-interfaces with PPPoE/DHCP, then failover is not possible without specifying next-hop address statically (which is not feasible, since also the default-gateway changes in a PPPoE/DHCP setup).

My idea would be for example to add a new textbox "path-monitor IP-address" within Network -> Interfaces -> ethernet1/1 -> IPv4 (set to DHCP).

Then with a security policy allowing that ping monitor, the DHCP interface would use its DHCP-IP-Address and the DHCP-Default-Gateway to perform the ping to the desired target (e.g. 8.8.8.8). If this is not pingable, then the DHCP-default-route will be removed.

[paulvandersteen]

I have a RFE "ID 5092" but did not see it in release notes that it is implemented, and also not in the public list "https://live.paloaltonetworks.com/t5/general-topics/feature-request-list/td-p/209128"

Is it possible to check this somewhere?

As far as i can read: No.

Regards

Paul