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
6/9/2017 | 1:14:57 PM
A project requirement I see missing from many a project plan is exactly the things you are referring to, including milestones for data integrity checks before, during and after projects, whether they are one-off requests for an overnight tweak or a year-long project. Luckily for my team we work hand-in-hand with teams like Security and Compliance. We treat all requests the same, we care for the data in the same manner regardless the project. But the requirements should still be documented as many projects may overlook such "minutia".
Time to Market should not compromise integrity and all considerations related to Security and Compliance should be built into the day-to-day operations of every team member who has charge over sensitive data. And, the requirements for such data management written into project plans, no matter how small large, and the operational mind-set of every user with access well trained to avoid breaches of this type.