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
Security Doesn't Trust IT and IT Doesn't Trust Security
Newest First  |  Oldest First  |  Threaded View
BradleyRoss
BradleyRoss,
User Rank: Moderator
5/9/2019 | 5:17:45 PM
Not trusting
The meetings I attended involved ten or twelve people with every person saying that they were in charge.  The next statement was usually that whatever went wrong, it was somebody else's fault.

In several cases, Security set requirements that were expensive and useless, but then said that it was up to IT to find the funding for the changes.  If Security wants to set policy, it has to do a number of things

Set clear policies and enforce them on everybody, including the C-Suite and themselves

If Security wants to set policies, it has to justify the required expenditure and be honest about the expenditures.  If they can't justify the expenses to the top executives, how is IT going to do it.  If Security has to make themselves unpopular, that is their job.

Be willing to justify their requirements, listen to the users, and be willing to admit when they are wrong.

Recognize that there are many people in IT who actually are far more knowledgable about computer security than they are.  I shouldn't have to explain customer requirements on security to the security staff.  I had a person in Security who told me that he didn't understand a government document.  I went through it, and found a list of referenced documents in the first few pages that contained glossaries and background information.  His response was that nobody had told him to read the other document which contained background material and a glossary.  I repeated that the preface stated that you had to go by the other document.  He said that he didn't care what the preface said, he was only told to follow the rest of the document.

Don't tell people that they are just too stupid to understand how brilliant they are.  I've actually encountered that.

When you receive a letter from the customer stating that you used to have the best and the brightest, but they were replaced by people who were far less competent than those that they replaced but believed themselves to be far more competent, don't state that you don't understand what they are trying to say.

If you really want to impress people, make sure that you specify the character encoding on your web pages.  The little black diamonds with question marks inside don't help your credibility.  If you don't specify it, your browser will probably use either UTF-8 or ISO-8850-1 according to how the browser is set up, but that won't necessarily match what was used in the page.  If you don't know what I'm talking about,don't pass yourself off as a computer expert.

Finally, you have to realize that people who worry about losing control never had it in the first place and never will.
BradleyRoss
BradleyRoss,
User Rank: Moderator
5/9/2019 | 5:17:44 PM
Not trusting
The meetings I attended involved ten or twelve people with every person saying that they were in charge.  The next statement was usually that whatever went wrong, it was somebody else's fault.

In several cases, Security set requirements that were expensive and useless, but then said that it was up to IT to find the funding for the changes.  If Security wants to set policy, it has to do a number of things

Set clear policies and enforce them on everybody, including the C-Suite and themselves

If Security wants to set policies, it has to justify the required expenditure and be honest about the expenditures.  If they can't justify the expenses to the top executives, how is IT going to do it.  If Security has to make themselves unpopular, that is their job.

Be willing to justify their requirements, listen to the users, and be willing to admit when they are wrong.

Recognize that there are many people in IT who actually are far more knowledgable about computer security than they are.  I shouldn't have to explain customer requirements on security to the security staff.  I had a person in Security who told me that he didn't understand a government document.  I went through it, and found a list of referenced documents in the first few pages that contained glossaries and background information.  His response was that nobody had told him to read the other document which contained background material and a glossary.  I repeated that the preface stated that you had to go by the other document.  He said that he didn't care what the preface said, he was only told to follow the rest of the document.


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
Incorporating a Prevention Mindset into Threat Detection and Response
Threat detection and response systems, by definition, are reactive because they have to wait for damage to be done before finding the attack. With a prevention-mindset, security teams can proactively anticipate the attacker's next move, rather than reacting to specific threats or trying to detect the latest techniques in real-time. The report covers areas enterprises should focus on: What positive response looks like. Improving security hygiene. Combining preventive actions with red team efforts.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-25878
PUBLISHED: 2022-05-27
The package protobufjs before 6.11.3 are vulnerable to Prototype Pollution which can allow an attacker to add/modify properties of the Object.prototype. This vulnerability can occur in multiple ways: 1. by providing untrusted user input to util.setProperty or to ReflectionObject.setParsedOption ...
CVE-2021-27780
PUBLISHED: 2022-05-27
The software may be vulnerable to both Un-Auth XML interaction and unauthenticated device enrollment.
CVE-2021-27781
PUBLISHED: 2022-05-27
The Master operator may be able to embed script tag in HTML with alert pop-up display cookie.
CVE-2022-1897
PUBLISHED: 2022-05-27
Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.
CVE-2022-20666
PUBLISHED: 2022-05-27
Multiple vulnerabilities in the web-based management interface of Cisco Common Services Platform Collector (CSPC) Software could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the interface. These vulnerabilities are due to insufficient va...