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.

Comments
Rethinking Website Spoofing Mitigation
Newest First  |  Oldest First  |  Threaded View
tdsan
tdsan,
User Rank: Ninja
8/17/2019 | 7:54:52 AM
Re: A new way of looking at a problem,

Also, a token could be issued by the company to validate their authenticity, this would be stored on the customer's browser or computer to ensure they are working with the right organization. This ensures the data is sent to the right company, even if it was not, the domain providers could provide a pop-up to the user stating that this could be a nefarious or ill-advised action, do you want to proceed or not.

One of the other options I mentioned below (from the quote in our earlier discussion) would be to add a token to the site, this would allow the browser to determine if the site was valid by using a SHA256 hash, site descriptor, and purpose all built into this number. This could be used to ensure the site is not a compromised site or if it is a site they have visited before, the browser would determine that much in the same way we use certificates. 

For me, I go to a few sites on a regular for personal and business purposes. There are others but this would help to address the security issue, not all but at least some aspects). Also, we need to start migrating the DNS environment to specifically use DNSSEC and move away from IPv4. This would be much harder for hackers to penetrate defenses because we would secure DNS traffic, reduce MITM attacks, create truly secure connections using IPSec VPN AES256 connections (all built into the protocol - IPv6). We can start identifying where the attack derived from (1-to-1 connections using IPv6) and the token would help to validate the site with the help of ML (I wanted to reiterate the point listed below because ML was only one of the points brought up in the beginning phases of the discussion).



Tokenization is the future of business and personal transactions. Blockchain is looking into that as well.

T


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
Practical Network Security Approaches for a Multicloud, Hybrid IT World
The report covers areas enterprises should focus on for their multicloud/hybrid cloud security strategy: -increase visibility over the environment -learning cloud-specific skills -relying on established security frameworks -re-architecting the network
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-30333
PUBLISHED: 2022-05-09
RARLAB UnRAR before 6.12 on Linux and UNIX allows directory traversal to write to files during an extract (aka unpack) operation, as demonstrated by creating a ~/.ssh/authorized_keys file. NOTE: WinRAR and Android RAR are unaffected.
CVE-2022-23066
PUBLISHED: 2022-05-09
In Solana rBPF versions 0.2.26 and 0.2.27 are affected by Incorrect Calculation which is caused by improper implementation of sdiv instruction. This can lead to the wrong execution path, resulting in huge loss in specific cases. For example, the result of a sdiv instruction may decide whether to tra...
CVE-2022-28463
PUBLISHED: 2022-05-08
ImageMagick 7.1.0-27 is vulnerable to Buffer Overflow.
CVE-2022-28470
PUBLISHED: 2022-05-08
marcador package in PyPI 0.1 through 0.13 included a code-execution backdoor.
CVE-2022-1620
PUBLISHED: 2022-05-08
NULL Pointer Dereference in function vim_regexec_string at regexp.c:2729 in GitHub repository vim/vim prior to 8.2.4901. NULL Pointer Dereference in function vim_regexec_string at regexp.c:2729 allows attackers to cause a denial of service (application crash) via a crafted input.