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
4/12/2018 | 12:45:04 PM
Though the article warns: "...while segmentation enhances an organization's security posture, it also adds complexity [more properly: complication] and costs... "; I think that assumes an outside-in, rather than a truly systemic implementation of the fact-based business rules specific to that organization, which should be used to determine segmentation and sequestering. Micro-segmentation of the network directed from an informational requirements-based mapping, ought to result in a less complicated (so less costly in terms of added infrastructure), and more importantly dynamically responsive (to dynamic organizational requirements), solution. This is, after all, a software-defined approach. It only makes sense to incorporate the application-specific informational requirements system design which is (or ought to be), already serving that organization.