Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

1/30/2019
11:30 AM
50%
50%

Access Control Lists: 6 Key Principles to Keep in Mind

Build them carefully and maintain them rigorously, and ACLs will remain a productive piece of your security infrastructure for generations of hardware to come.
Previous
1 of 8
Next

In an industry of constant, rapid change, an old-school security tool remains an effective piece of an overall security. Access Control Lists (ACLs) that specify precise rules for destinations and protocols allowed or forbidden, are the foundation of firewalls. And while firewalls have advanced to use analysis of packet contents and behavior, ACLs have not gone away.

There are a number of reasons why ACLs endure. The first, and most important, is that they work. ACLs are straight-forward, conceptually simple ways to limit traffic to and from known (or suspected) malicious addresses and to clear traffic to and from addresses known to be acceptable. Next, they play well with others. As Twitter user Frank Barton (@fbarton) wrote in response to a question about ACLs, "…much less cpu intensive than stateful and deep-packet. But…like Ogres, and onions…use layers. If you can block traffic at ACL, then pass remaining to “NGFW” [next-generation firewall] the fw [firewall] has less traffic to inspect."

As with all security measures, though, how an ACL is deployed will have a major impact on its effectiveness. Of course, precisely how the ACL is programmed will vary from manufacturer to manufacturer, and component to component, but there are key considerations that are true regardless of which device is hosting the ACL. Let's take a look at the principles to keep in mind to make ACLs an effective (and efficient) part of the overall security infrastructure.

(Image: photon_photo — stock.adobe.com)

 

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio

Previous
1 of 8
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
paul.dittrich
50%
50%
paul.dittrich,
User Rank: Strategist
1/30/2019 | 3:40:31 PM
Harnessing the power of ACLs
I could not agree more strongly with every point in your column.

It may be fashionable to claim there is no longer a network perimeter but I still strongly favor using the border router as a "garbage filter".

The BOGONs list? - Drop them all.  Invalid TCP flag combinations - Drop.  No Telnet in your environment?  No FTP?  No RDP?  - Block them all at the border router.

As mentioned in the post, the NGFW should take care of the deep packet inspection for only the traffic you potentially want inside your network.  That firewall should see very little traffic except for the known IPs, ports and protocols which are candidates to be allowed all the way in.

And an outbound ACL (a.k.a. egress filtering) is a very powerful weapon against data exfiltration and many types of malware.  You may still have a Trojan but if it can't phone home......
For Cybersecurity to Be Proactive, Terrains Must Be Mapped
Craig Harber, Chief Technology Officer at Fidelis Cybersecurity,  10/8/2019
A Realistic Threat Model for the Masses
Lysa Myers, Security Researcher, ESET,  10/9/2019
USB Drive Security Still Lags
Dark Reading Staff 10/9/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-16344
PUBLISHED: 2019-10-14
A cross-site scripting (XSS) vulnerability in the login form (/ScadaBR/login.htm) in ScadaBR 1.0CE allows a remote attacker to inject arbitrary web script or HTML via the username or password parameter.
CVE-2019-17575
PUBLISHED: 2019-10-14
A file-rename filter bypass exists in admin/media/rename.php in WBCE CMS 1.4.0 and earlier. This can be exploited by an authenticated user with admin privileges to rename a media filename and extension. (For example: place PHP code in a .jpg file, and then change the file's base name to filename.ph ...
CVE-2019-17579
PUBLISHED: 2019-10-14
SonarSource SonarQube before 7.8 has XSS in project links on account/projects.
CVE-2019-9745
PUBLISHED: 2019-10-14
CloudCTI HIP Integrator Recognition Configuration Tool allows privilege escalation via its EXQUISE integration. This tool communicates with a service (Recognition Update Client Service) via an insecure communication channel (Named Pipe). The data (JSON) sent via this channel is used to import data f...
CVE-2019-14838
PUBLISHED: 2019-10-14
A flaw was found in wildfly-core before 7.2.5.GA. The Management users with Monitor, Auditor and Deployer Roles should not be allowed to modify the runtime state of the server