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
8/23/2017 | 5:22:33 PM
I don't know when actual physical voter fraud ended (that's something historians know). Dead voters don't vote until the vote counters count them, and they vote to make the totals add up. It's a pretty sophisticated system. But it only works if there aren't auditors, or maybe even observors, to keep the vote counters honest. Our system works because voters believe that vote counting fraud is small enough that it "usually" doesn't make a difference (that is, it's always somewhere else, and only a few places, and only a few votes in the House of Representatives, and "we" outvote "them").
So to protect the system, our only defense is to create an audit trail and have observors of the entire process. That means that we have to admit that the system is hackable and make it robust so that we can re-count the votes as needed (just as in the paper ballot days); allow for legal challenges as to which ballots were legally and/or legitimately cast (just as in the paper ballot days); allow for spoiled ballots (ditto); allow for potentially lost and/or rediscovered ballots (but at least not in the trunk of a car [we hope -- or is a lost and rediscovered thumb drive possible? -- politics guarantees full employment for lawyers]); and who knows what else? An armed citizen insurrection to guarantee public counting of ballots (Athens, TN, 1946)?