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
Building A Cybersecurity Program: 3 Tips
Newest First  |  Oldest First  |  Threaded View
JGarner721
JGarner721,
User Rank: Apprentice
1/28/2015 | 4:07:49 PM
Disagree but understand the stance
The most valuable asset to an organization is the informational assets. If what you describe is true, then the infrastructure is the only thing that is critical. But, every piece of hardware and software (endpoint devices, routers, anti-malware software and so on) are in place to ensure the confidentiality, integrity and availability of that information. If an organization understands the its informational assets an information security program is the starting point. That program would have the subset of a cyber security program. Otherwise, you are putting the cart ahead of the horse. I believe the discussion on cyber and information security is a positive process. I just find it interesting that everything you are referencing is addressed in current information security philosophy. Resilience and Incident response are key items addressed in CyberSecurity. These are already addressed with Business Continuity/Disaster Recovery programs and Emergency response and current Incident response elements. Where most organizations fall short is their ability to solicit intelligence, then use it for decision making and effectively forecast on their organizational threats. Two key components of any sound informational and cyber security program are; A comprehensive asset inventory and a risk assessment applied to those assets to determine the Risk Management strategy. Great Discussion!
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
1/28/2015 | 11:19:21 AM
Re: Good pragmatic advice
Thanks Jason. Useful suggestions! 
JasonSachowski
JasonSachowski,
User Rank: Author
1/27/2015 | 6:59:42 PM
Re: Good pragmatic advice
Perhaps I can give a break down into the logic of how to arrive at a definition.

1) First of all is figuring our what "Cyber" is.  Cyber, as per Oxford, is anything "relating to or characteristic of the culture of computers, information technology, and virtual reality". In essence, this can be summed up to say that all things "cyber" is all things "digital" is all things "cybersecurity".

2) Second, the term "all things" has to be translated into relevant and meaningful entities for your organization.  In other words, "all things" has to be qualified into the assets and/or systems that must be safeguarded.

3) Third, what do we mean by "safeguarding"?  If we consider the S.T.R.I.D.E. Threat Model, there are essentially two major grouping that assets and/or systems must be safeguarded against: damage and/or unauthorized access

4) Lastly, how do we safeguard against damage and/or unauthorized access? Well, as with an Information Security program there has to be an integration of people, process, and technology.
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
1/27/2015 | 9:47:23 AM
Re: Good pragmatic advice
Thanks! Are you free to share what your organization used to define security -- or can you offfer a generic example of what might work for a particular industry...
JasonSachowski
JasonSachowski,
User Rank: Author
1/27/2015 | 9:43:11 AM
Re: Good pragmatic advice
The trickest part is coming to end of job on defining what "Cybersecurity" is to an organization because of how it is being used interchangeably with "Information Security".  Getting over this speed bump requires that Stakeholders, such as InfoSec professionals and management, are aligned with what "Cybersecurity" means to your organization.  From here, everything afterwards falls into place because everybody is in agreement.
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
1/27/2015 | 8:50:20 AM
Good pragmatic advice
Great job on this blog, Jason. Wondering, in your experience, what is the trickest part of building a cybersecurity program -- and how did  you deal with the problem? 


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
Practical Network Security Approaches for a Multicloud, Hybrid IT World
The report covers areas enterprises should focus on for their multicloud/hybrid cloud security strategy: -increase visibility over the environment -learning cloud-specific skills -relying on established security frameworks -re-architecting the network
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-30333
PUBLISHED: 2022-05-09
RARLAB UnRAR before 6.12 on Linux and UNIX allows directory traversal to write to files during an extract (aka unpack) operation, as demonstrated by creating a ~/.ssh/authorized_keys file. NOTE: WinRAR and Android RAR are unaffected.
CVE-2022-23066
PUBLISHED: 2022-05-09
In Solana rBPF versions 0.2.26 and 0.2.27 are affected by Incorrect Calculation which is caused by improper implementation of sdiv instruction. This can lead to the wrong execution path, resulting in huge loss in specific cases. For example, the result of a sdiv instruction may decide whether to tra...
CVE-2022-28463
PUBLISHED: 2022-05-08
ImageMagick 7.1.0-27 is vulnerable to Buffer Overflow.
CVE-2022-28470
PUBLISHED: 2022-05-08
marcador package in PyPI 0.1 through 0.13 included a code-execution backdoor.
CVE-2022-1620
PUBLISHED: 2022-05-08
NULL Pointer Dereference in function vim_regexec_string at regexp.c:2729 in GitHub repository vim/vim prior to 8.2.4901. NULL Pointer Dereference in function vim_regexec_string at regexp.c:2729 allows attackers to cause a denial of service (application crash) via a crafted input.