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
US Government Cybersecurity at a Crossroads
Newest First  |  Oldest First  |  Threaded View
JBUITRON770
100%
0%
JBUITRON770,
User Rank: Apprentice
5/24/2018 | 3:37:17 AM
The post of Cybersecurity Advisor should not have been eliminated
Hi,

In 2009, I finished a Master's Thesis on information security in the U.S. Government, one conclusion was that there should be a Cybersecurity Czar (or similar) in the government, answering directly to the President, with authority over the agencies in both branches, working in conjunction with the GAO (Government Accountability Office). Further reading after I finished the thesis revealed that at least two government-watching authorities were advising a similar office.

This recent move by the Trump Administration contradicts his election platform that supported strong information security\cybersecurity in the U.S. Government. Government agencies often rely on contractors to support their security posture, because there aren't enough security experts within the various branches. The same is true at the upper echelons of government. Our government needs advisors, and doing away with the cybersecurity advisor was a large step backward.

I anticipate additional steps in the wrong direction. I hope that such steps do not happen, yet this action seems like it may be part of a trend.

thanks,

Jan Buitron, MSIA, CISSP, Doctor of Computer Science candidate


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
How Data Breaches Affect the Enterprise
Data breaches continue to cause negative outcomes for companies worldwide. However, many organizations report that major impacts have declined significantly compared with a year ago, suggesting that many have gotten better at containing breach fallout. Download Dark Reading's Report "How Data Breaches Affect the Enterprise" to delve more into this timely topic.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-43695
PUBLISHED: 2021-11-29
An unspecified version of issabelPBX is affected by a Cross Site Scripting (XSS) vulnerability. In file page.backup_restore.php, the exit function will terminate the script and print the message to the user. The message will contain $_REQUEST without sanitization, then there is a XSS vulnerability.
CVE-2021-43696
PUBLISHED: 2021-11-29
An unspecified version of twmap is affected by a Cross Site Scripting (XSS) vulnerability. In file list.php, the exit function will terminate the script and print the message to the user. The message will contain $_REQUEST then there is a XSS vulnerability.
CVE-2021-43697
PUBLISHED: 2021-11-29
An unspecified version of Workerman-ThinkPHP-Redis is affected by a Cross Site Scripting (XSS) vulnerability. In file Controller.class.php, the exit function will terminate the script and print the message to the user. The message will contain $_GET{C('VAR_JSONP_HANDLER')] then there is a XSS vulner...
CVE-2021-43698
PUBLISHED: 2021-11-29
An unspecified version of phpWhois is affected by a Cross Site Scripting (XSS) vulnerability. In file example.php, the exit function will terminate the script and print the message to the user. The message will contain $_GET['query'] then there is a XSS vulnerability.
CVE-2021-24918
PUBLISHED: 2021-11-29
The Smash Balloon Social Post Feed WordPress plugin before 4.0.1 did not have any privilege or nonce validation before saving the plugin's setting. As a result, any logged-in user on a vulnerable site could update the settings and store rogue JavaScript on each of its posts and pages.