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.
Incorporating a Prevention Mindset into Threat Detection and ResponseThreat detection and response systems, by definition, are reactive because they have to wait for damage to be done before finding the attack. With a prevention-mindset, security teams can proactively anticipate the attacker's next move, rather than reacting to specific threats or trying to detect the latest techniques in real-time.
The report covers areas enterprises should focus on:
What positive response looks like.
Improving security hygiene.
Combining preventive actions with red team efforts.
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
0 Comments
User Rank: Ninja
7/26/2018 | 3:06:35 PM
→ Training needs to be put at the forftont, we need to evaluate the talent we have on staff on a consistent basis
→ Firewalls, routers, switches and other network gear needs to be follow the NSA security guidelines and framework - https://www.vmguru.com/2017/04/sizing-your-vmware-infrastructure/ (we need to add to this guideline and continue to test so we can push the envelope (or at least get close)
→ We really need to remove IPv4 from the mix of solutions and move to an IPv6 (pure) environment
→ We need to have a moc setup where we pay someone to hack the environment and we test the people there by putting them into a scenario
→ Application programming methodologies need to be reviewed by qualified hackers who have a deveopment background
→ We need to employ machine learning in the mix of products where the technology is always checking to see who is accessing what and reporting or even thwarting it
→ We need to automate the pentesting process but tailor it to our needs, get it to the point that the vulnerabilities can be mitigating by a autonomic programming change
→ We need to prioritize the threats or vulnerabilities, schedule weekend schedule patch and system updates to ensure the systems meet a certain severity level (sev1-5) and if the sev level is reviewed by outside vendor (reputable)
→ Implement next generation firewalls, endpoint monitoring, NMS, HIDS, NIDS, Zone/Layering and application integration without our existing security tools
→ We need a protocol monitoring device that identifies and baselines relationships between systems and applications, if there is an outside presence, then the system needs to tell us
→ Move pertinent data to zone 0, do not install DB on Web applications (separation of duties) and only allow data to write after a cleansing or holding area (similar to ACH) to ensure the data has not been compromised
→ If multiple records have been extracted by an outside source (Database), there needs to be a warning and action to go along with this potential threat, or at least after 10 records, then something needs to stop the data extraction (notification or autonomic stoppage)
→ If we are not doing business with a specific country, then block those countries that are not in our purvey using ACLs, NGFW with Country blocking capability
→ DNS needs to be configured with DNSSEC using specific keys that are stored in a safe place and only allow queries (recursive) to be done by systems that are internal, anything from the outside trying to access and perform lookups internally with outside IP addresses need to be thwarted
There are other things but this all I can think of right now.
Todd