10 Things to Test in Your Future NGFW: Prevent Credential Abuse

6,740 people reacted 2 3 min. read

This post is part of a blog series where we examine the 10 things to test in your future next-generation firewall. These 10 points will help ensure your next firewall matches the needs of your organization in its current and future states.  

There are many ways attackers can obtain stolen credentials, including phishing, malware, social engineering, brute force or black-market purchase. Once attackers have stolen credentials, they can abuse them to enter an organization, move laterally, and escalate privileges for unauthorized applications and data.


Multi-Factor Authentication: Why Should You Advocate and Test This Capability?
Implementing multi-factor authentication on the firewall helps prevent attackers from moving laterally with stolen credentials. MFA allows your organization to protect all types of applications, including legacy applications and client servers. Additionally, authentication that occurs at the firewall, before users connect to applications, moves the line of exposure farther away.


Move Beyond the Status Quo
Many organizations have an MFA solution, but it is often challenging and time-consuming to integrate with all applications. As a result, most organizations only use MFA with a handful of applications, such as a VPN gateway or a few cloud applications, leaving many others vulnerable to credential abuse.


Protection at the Network Layer
MFA is a useful tool, but it must be implemented in a way that protects all critical applications. Rather than modifying the applications themselves, use your firewall with MFA policy to control traffic to specific applications. The firewall should be able to control access and require authentication before allowing traffic to pass. Attackers operating inside the organization, even from a compromised endpoint, would not be able to complete the MFA.


Tailored User Experience
Policies for MFA that are created within the firewall should be granular, both in terms of the user and the sensitivity of the application. For example, the policy should match the frequency with which users must reauthenticate to the sensitivity of the application.


Accelerate the Time to Protection for Applications
Multi-factor authentication as a part of firewall policy improves the speed of implementation, as you only need to integrate MFA within network policy, rather than changing applications themselves. This allows for quicker deployment of protections to meet compliance. MFA on the firewall stops attackers from using stolen credentials or moving laterally within an organization, and protects all types of applications, including legacy applications and client servers.


Recommended RFP Questions

  • Does the NGFW support MFA as part of the access-control policy based on the sensitivity of the resource accessed?
  • Does the NGFW provide choices for a variety of MFA partner technologies?
  • Can the NGFW support RADIUS and API integrations with MFA partner technologies?
  • Does the NGFW support MFA policy for any type of application, including web, client-server and terminal applications?
  • Is the NGFW’s MFA capability limited to certain protocols?

Learn more about the 10 things to test for in your future NGFW.                        


Got something to say?