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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
How To Avoid Collateral Damage In Cybercrime Takedowns
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
Joe Stanganelli,
 User Rank: Ninja
7/3/2015 | 10:42:27 AM
Re: More Stringent Vetting Process
> Even though you used reductio ad absurdum to make it

What's wrong with that?  :p  It's a technique, not a logical fallacy.

> I don't think registration of trusted parties is comparable to a myriad of ID's.

Just another form of multifactor identification.  ;)

In any case, tell NSTIC that...
RyanSepe
RyanSepe,
 User Rank: Ninja
7/2/2015 | 7:42:08 AM
Re: More Stringent Vetting Process
Very much agree with your statement. Even though you used reductio ad absurdum to make it as I don't think registration of trusted parties is comparable to a myriad of ID's.

To your point, balance is important. Otherwise, other methods that provide an increased ease of use will be leveraged and those could contain even less security measures then the previously mentioned. This premise is not exclusive to OpenDNS.
Joe Stanganelli
Joe Stanganelli,
 User Rank: Ninja
6/30/2015 | 11:03:41 PM
Re: More Stringent Vetting Process
Well, that's always the detriment/tradeoff, isn't it?  Alas, security and accessibility are fated to be eternal mortal foes.

We could secure access to email and other systems rather well by eliminating networks altogether by requiring face-to-face authentication at a designated computer terminal with three forms of government ID, along with eye and fingerprint scans, but that would be highly impractical.  Cybersecurity is only partly about protection; it's about finding the balance -- the line -- in that tradeoff between functionality and protection.
RyanSepe
RyanSepe,
 User Rank: Ninja
6/25/2015 | 11:37:23 AM
More Stringent Vetting Process
I think a better approach from a security standpoint would be a more stringent registration practice. This way, all malicious intenders would have a more difficult time getting into the "group". This would minimize the collateral damage substantially as any outside the database could be purged with minimal risk. Some would slip through obviously but revocation is always available upon discovery. Benefits: It would strengthen security posture. Detriments: It would take longer to register due to more stringent protocols and handling. This is also dependent on a centralized model of DNS providers.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Everything You Need to Know About DNS Attacks
It'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
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-33196
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences. Cross site scripting (XSS) can be triggered by review volumes. This issue has been fixed in version 4.4.7.
CVE-2023-33185
PUBLISHED: 2023-05-26
Django-SES is a drop-in mail backend for Django. The django_ses library implements a mail backend for Django using AWS Simple Email Service. The library exports the `SESEventWebhookView class` intended to receive signed requests from AWS to handle email bounces, subscriptions, etc. These requests ar...
CVE-2023-33187
PUBLISHED: 2023-05-26
Highlight is an open source, full-stack monitoring platform. Highlight may record passwords on customer deployments when a password html input is switched to `type="text"` via a javascript "Show Password" button. This differs from the expected behavior which always obfuscates `ty...
CVE-2023-33194
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences on the web.The platform does not filter input and encode output in Quick Post validation error message, which can deliver an XSS payload. Old CVE fixed the XSS in label HTML but didn’t fix it when clicking save. This issue was...
CVE-2023-2879
PUBLISHED: 2023-05-26
GDSDB infinite loop in Wireshark 4.0.0 to 4.0.5 and 3.6.0 to 3.6.13 allows denial of service via packet injection or crafted capture file