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
5 Top Tips For Outsourced Security
Newest First  |  Oldest First  |  Threaded View
aws0513
aws0513,
User Rank: Ninja
9/25/2014 | 8:07:29 AM
Re: Outsourcing security
Definitely in the minority.

I say this because unless an organization has IT security professionals as part of their workforce, the organization management will often consider any outsourcing of any kind for any function if it is believed to be a benefit in costs (and in some cases considered a COOP benefit). 
Some older organizations may have, during their existence, learned (encountered) the risks involved with outsourcing certain functions and thus may have already implemented those functions as part of their own organization, but those are few and far between.
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
9/24/2014 | 5:03:52 PM
Re: Outsourcing security
Followup to aws0513 and  Stratustician: Do you think most companies follow your outsourcing guildines, or are you in the minority?
Stratustician
Stratustician,
User Rank: Moderator
9/23/2014 | 2:54:20 PM
Re: Outsourcing security
I absolutely agree, Access Control Policies should be kept in house due to the constant changes and the need to ensure policies are able to keep up.  I would also add data asset tagging, ie whitelisting of how data can be used.  If you are able to control how your data can be accessed and used you'll have a stronger security posture.  Oh, and let's not forget encryption keys, those should be kept in-house to avoid leakage.
aws0513
aws0513,
User Rank: Ninja
9/23/2014 | 11:51:29 AM
Re: Outsourcing security
My immediate list of security relevant functions that should not be outsourced.  There could be other functions that I have not thought of yet, but these two came to mind almost immediately.

1) User provisioning
2) Access control management

Some would think otherwise, but it is my opinion that these are "gatekeeper" functions that the organization itself should maintain.  The localized establishement of these functions would ensure consistency in access control practices and policies along with enhanced capability to identify and remediate internal security risks.  Availability of these functions is also enhanced in that the organization can more quickly gage the need for these functions based upon operations requirements.

 
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
9/23/2014 | 10:26:09 AM
Outsourcing security
Curious to know what, if any, functions Dark Reading community members would consider -- or absolutley NOT -- consider for outsourcing. And why. Thoughts anyone?


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
Black Hat USA 2022 Attendee Report
Black Hat attendees are not sleeping well. Between concerns about attacks against cloud services, ransomware, and the growing risks to the global supply chain, these security pros have a lot to be worried about. Read our 2022 report to hear what they're concerned about now.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-38235
PUBLISHED: 2022-08-16
XPDF commit ffaf11c was discovered to contain a segmentation violation via DCTStream::getChar() at /xpdf/Stream.cc.
CVE-2022-38236
PUBLISHED: 2022-08-16
XPDF commit ffaf11c was discovered to contain a global-buffer overflow via Lexer::getObj(Object*) at /xpdf/Lexer.cc.
CVE-2022-38237
PUBLISHED: 2022-08-16
XPDF commit ffaf11c was discovered to contain a heap-buffer overflow via DCTStream::readScan() at /xpdf/Stream.cc.
CVE-2022-38238
PUBLISHED: 2022-08-16
XPDF commit ffaf11c was discovered to contain a heap-buffer overflow via DCTStream::lookChar() at /xpdf/Stream.cc.
CVE-2022-36141
PUBLISHED: 2022-08-16
SWFMill commit 53d7690 was discovered to contain a segmentation violation via SWF::MethodBody::write(SWF::Writer*, SWF::Context*).