From: Lee <ler762@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] cybersecurity is not a talent problem
Date: Wed, 8 Nov 2023 17:47:21 -0500 [thread overview]
Message-ID: <CAD8GWst2q6L-QGhcpjBcKe9P4N3UCSF=FSHBeEqMuC96oaOB4g@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7afK5CdRpaN0Cbqk7nEkLAVHF1hzXnkzoncKWZXXkQ4w@mail.gmail.com>
On Wed, Nov 8, 2023 at 2:22 PM Dave Taht via Nnagain wrote:
>
> Paul Vixie reposted this old piece of his, even more relevant today, than 2015.
>
> https://www.linkedin.com/pulse/lack-talent-problem-cyber-paul-vixie/
I disagree. With a lot, but let's just go with this
> The "cyber" security problems that the US Government, and every other government, and every large and medium enterprise are all coping with today do not stem from lack of "cyber" talent.
Take a look at
https://oversight.house.gov/wp-content/uploads/2016/09/The-OPM-Data-Breach-How-the-Government-Jeopardized-Our-National-Security-for-More-than-a-Generation.pdf
on page 9:
The bottom line. The longstanding failure of OPM's leadership to
implement basic cyber
hugiene, such as maintaining current authorities to operate and
employing strong multi-factor
authentication, despite years of warnings from the Inspector General,
represents a failure of
culture and leadershit, not technology.
There is no substitute for talent.
Regards,
Lee
next prev parent reply other threads:[~2023-11-08 22:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 19:21 Dave Taht
2023-11-08 20:43 ` Dick Roy
2023-11-08 22:47 ` Lee [this message]
2023-11-09 0:58 ` Dick Roy
2023-11-09 2:26 ` Lee
2023-11-09 6:21 ` Dick Roy
2023-11-09 9:19 ` David Lang
2023-11-09 16:47 ` David Bray, PhD
2023-11-09 17:25 ` David Lang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAD8GWst2q6L-QGhcpjBcKe9P4N3UCSF=FSHBeEqMuC96oaOB4g@mail.gmail.com' \
--to=ler762@gmail.com \
--cc=nnagain@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox