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.
Everything You Need to Know About DNS AttacksIt's important to understand DNS, potential attacks against it, and the tools and techniques required to defend DNS infrastructure. This report answers all the questions you were afraid to ask.
Domain Name Service (DNS) is a critical part of any organization's digital infrastructure, but it's also one of the least understood. DNS is designed to be invisible to business professionals, IT stakeholders, and many security professionals, but DNS's threat surface is large and widely targeted.
Attackers are causing a great deal of damage with an array of attacks such as denial of service, DNS cache poisoning, DNS hijackin, DNS tunneling, and DNS dangling. They are using DNS infrastructure to take control of inbound and outbound communications and preventing users from accessing the applications they are looking for. To stop attacks on DNS, security teams need to shore up the organization's security hygiene around DNS infrastructure, implement controls such as DNSSEC, and monitor DNS traffic
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: Apprentice
9/3/2020 | 9:11:02 PM
It is well known: whenever a skilled staff member leaves there are real costs to locating a replacement and training a replacement. Nothing new in this article on that front.
Listening to Twitter and another large closed info-sec email list, I'd say that the issues are more that there is a security skills shortage, little incentive to build secure systems, and a low/poor management committment to building securely coded solutions. Skill shortages are solvable by educating internal staff and then incentivizing them to do the right thing, security wise. Microsoft has proven this, as have other large firms. Something like 10-15 years ago they started making people actually be responsible for secure code.
The issue is that Sr Mgmt (C-X-O and A-VP and above) behave in a manner that protects their bonues because they are preassured by the market to "get it done and get it out", not "get it out, stable, and secure." Until the rest of the Fortune 1000 and Global 2K follow what MSFT did we will continue to battle.
Further - it is *well known* that money is reason #5 on the list. People fire managers, or companies long before dollars.
I have 15 years of sec-exp - most of the calls I get are temp 3-6 month short term at a pay rate around 60 - 80. Of the past 30 calls / inquiries in the past 60 days, only 3 were for positions equivalent to what I have on my resume - Director and above. The rest were not. Matter of fact, the best three interviews I've had in the past year came from personal 1:1 relationships.
I dropeed over 100 resumes where the PD/JD clearly matched up to the keywords in the article - I get maybe 10% engagement.
Go and listen to people applying for pen test jobs - people with a SANS certification or in some cases the OSCP. Employers run them through actual "hack this" tests, multiple times. I know a few who had to do 4 test events. It will run people ragged, esp. when the offers comes in a 50k-60k yr., in midwest metro markets.