Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Don Y <blockedofcourse@foo.invalid>
Newsgroups: sci.electronics.design
Subject: Re: Win11 explorer bug?
Date: Fri, 13 Dec 2024 13:52:19 -0700
Organization: A noiseless patient Spider
Lines: 29
Message-ID: <vji6qd$3jsoc$1@dont-email.me>
References: <vjg7dh$kf$2@nnrp.usenet.blueworldhosting.com>
 <vjgm11$396oa$1@dont-email.me>
 <vjhupn$1ds9$1@nnrp.usenet.blueworldhosting.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 13 Dec 2024 21:52:31 +0100 (CET)
Injection-Info: dont-email.me; posting-host="00f08a375bca5e0fb2fe68936c34f7cb";
	logging-data="3797772"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19BSChsHe5ZJD66N7xn5tr6"
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.2.2
Cancel-Lock: sha1:Kzx/vKgNCstq1pwEdjjW0ifftUk=
Content-Language: en-US
In-Reply-To: <vjhupn$1ds9$1@nnrp.usenet.blueworldhosting.com>
Bytes: 2476

On 12/13/2024 11:35 AM, Edward Rawde wrote:
> "Don Y" <blockedofcourse@foo.invalid> wrote in message news:vjgm11$396oa$1@dont-email.me...
>> On 12/12/2024 7:50 PM, Edward Rawde wrote:
>>> I'm getting 441 header line too long while trying to reply to Don Y in the other thread so I'm going to leave it there.
>>>
>>> Some organizations are obviously doing a lot better then others at cybersecurity.
>>
>> <https://www.crn.com/news/security/2024/10-major-cyberattacks-and-data-breaches-in-2024-so-far>
>>
>> at least, the ones that we KNOW about...
>>
>>
> 
> They are all large organizations rather than a single location with a single firewall.
> 
> Large organisations don't have a single individual doing firewall configuration and security for the entire organisation.

No.  They have automated tools doing this work.  No one spends their time
manually browsing log files.

> The ones who have breaches more likely have managers who don't want anything touched if it's working.
> 
> So the individual who suggests that changes should be made to restrict database connections to nothing other than known IP addresses
> or networks, rather than having them open to the entire world, is likely to be ignored. This is, of course, just one of the myriad
> reasons why breaches occur.
> 
>