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.
Developing and Testing an Effective Breach Response PlanWhether or not a data breach is a disaster for the organization depends on the security team's response and that is based on how the team developed a breach response plan beforehand and if it was thoroughly tested. Inside this report, experts share how to:
-understand the technical environment,
-determine what types of incidents would trigger the plan,
-know which stakeholders need to be notified and how to do so,
-develop steps to contain the breach, collect evidence, and initiate recovery.
Incident Readiness and Building Response Playbook
In this special report, learn the Xs and Os of any good security incident readiness and response playbook.
Tweet This
1 Comments
User Rank: Strategist
1/30/2019 | 3:40:31 PM
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......