This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "OWASP Anti-Ransomware Guide Project"

From OWASP
Jump to: navigation, search
(→‎The OWASP Security Principles)
 
(21 intermediate revisions by the same user not shown)
Line 7: Line 7:
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
 
−
<span style="color:#ff0000">
 
−
Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project.
 
−
</span>
 
  
 
==The OWASP Anti-Ransomware Guide==
 
==The OWASP Anti-Ransomware Guide==
Line 17: Line 14:
 
Open up any newspaper or news site and an increasingly common headline is becoming “hospital held for ransom”.  While hospitals and other organizations often have downtime procedures that let them revert back to paper for dealing with power outages and other disasters, it is still a nightmare scenario to find your entire organization's IT infrastructure screeching to a halt all because someone clicked on a malicious link or opened a questionable email attachment.  Moreover, many organizations have a significant number of legacy systems that make security a challenge and beyond very basic security provisions often do not have a corporate culture that is heavily focused on information security.  This has left many organizations struggling with how to handle ransomware attacks.  The below is meant to serve as a comprehensive defense in depth based checklist and guide to preventing ransomware from taking a foothold in your organization as well as ensuring the proper procedures are in place to deal with an actual ransomware outbreak in your environment.  Given the prevalence of Windows systems as ransomware targets, the guide is geared towards a Windows environment but is designed to be product agnostic.  Please note that the list is designed to be comprehensive and as such not all controls may be applicable to all environments.
 
Open up any newspaper or news site and an increasingly common headline is becoming “hospital held for ransom”.  While hospitals and other organizations often have downtime procedures that let them revert back to paper for dealing with power outages and other disasters, it is still a nightmare scenario to find your entire organization's IT infrastructure screeching to a halt all because someone clicked on a malicious link or opened a questionable email attachment.  Moreover, many organizations have a significant number of legacy systems that make security a challenge and beyond very basic security provisions often do not have a corporate culture that is heavily focused on information security.  This has left many organizations struggling with how to handle ransomware attacks.  The below is meant to serve as a comprehensive defense in depth based checklist and guide to preventing ransomware from taking a foothold in your organization as well as ensuring the proper procedures are in place to deal with an actual ransomware outbreak in your environment.  Given the prevalence of Windows systems as ransomware targets, the guide is geared towards a Windows environment but is designed to be product agnostic.  Please note that the list is designed to be comprehensive and as such not all controls may be applicable to all environments.
  
−
==Description==
+
==Project Description==
−
 
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
This section must include a shorter description of what the project is, why the project was started, and what security issue is being helped by the project deliverable. This description will be used to promote the project so make sure the description represents your project in the best way possible.
 
−
</span>
 
−
 
 
−
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]
 
−
'''
 
−
 
 
−
Over the course of my career, I have come across and collected a number of security ''aphorisms.'' These aphorisms constitute the fundamental principles of information security.
 
−
 
 
−
None of the ideas or truths are mine, and unfortunately, I did not collect the citations. Initially, I would like to identify the correct citations for each aphorism.
 
  
−
Additionally, many are re-statements of the same idea; thus, the 'collection of ideas' defines a fundamental principle. As such, I would also like to reverse engineer the principles from the aphorisms where appropriate, as well.
+
A guide and checklist organizations can use as the basis for creating a defense in depth strategy for combating ransomware and other types of malware.
  
 
==Licensing==
 
==Licensing==
Line 38: Line 23:
 
'' Additionally, we also encourage you to contribute back to the project.  
 
'' Additionally, we also encourage you to contribute back to the project.  
  
−
The OWASP Anti-Ransomware Guide is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.
+
The OWASP Anti-Ransomware Guide is licensed under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.
  
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
−
 
−
== What is OWASP Security Principles Project? ==
 
−
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
Here you should add a short description of what your project actually does. What is the primary goal of your project, and why is it important?
 
−
</span>
 
−
 
−
The end goal is to identify, cite, and document the fundamental principles of information security. Once this is well organised, I think it would be great to publish this through the [http://scriptogr.am/dennis-groves/post/owasp-press OWASP Press]. Of course, it will always remain freely available, and any money collected will go directly into the project to absorb costs with any remaining funds going to the OWASP Foundation.
 
−
 
−
This document should serve as a guide to technical architects and designers outlining the fundamental principles of security.
 
−
 
−
== Presentation ==
 
−
 
−
Coming Soon
 
  
 
== Project Leaders ==
 
== Project Leaders ==
Line 64: Line 34:
  
 
== Download ==
 
== Download ==
 +
* [https://www.owasp.org/images/3/3f/Anti-RansomwareGuidev2.pdf Version 2.0]
 +
* [https://www.owasp.org/images/6/64/Anti-RansomwareGuidev1-7.pdf Version 1.7]
 +
* [https://www.owasp.org/images/c/ca/Anti-RansomwareGuidev1-6.pdf Version 1.6]
 +
* [https://www.owasp.org/images/4/4a/Anti-RansomwareGuidev1-5.pdf Version 1.5]
 +
* [https://www.owasp.org/images/9/98/Anti-RansomwareGuidev1-4.pdf Version 1.4]
 +
* [https://www.owasp.org/images/5/5f/Anti-RansomwareGuidev1-3.pdf Version 1.3]
 +
* [https://www.owasp.org/images/8/8b/Anti-RansomwareGuidev1-2.pdf Version 1.2]
 +
* [https://www.owasp.org/images/d/d3/Anti-RansomwareGuidev1-1.pdf Version 1.1]
 +
* [https://www.owasp.org/images/a/a8/Anti-RansomwareGuide.pdf Version 1.0]
  
 +
== Spanish Translation ==
 +
* [https://www.owasp.org/images/3/39/Guia_Contra_Ransomware.pdf Spanish Version 1.4]
  
−
* [https://www.owasp.org/images/a/a8/Anti-RansomwareGuide.pdf Version 1.0]
+
== Presentation ==
 +
* [https://youtu.be/bPyNzP7Gqig VMworld 2017]
 +
* [https://www.slideshare.net/cfrenz/mockincidentsnymjcsc2016 NYMJCSC Presentation]
  
 
== News and Events ==
 
== News and Events ==
  
−
Coming Soon
+
* [http://nymjcsc.org/ 2016 NYMJCSC]
 +
* [https://iapp.org/news/a/why-the-wannacry-outbreak-should-be-a-wake-up-call/ IAPP Privacy Tech]
 +
* [http://vmware.cioreview.com/cxoinsight/mitigating-malware-attacks-with-a-nsx-enabled-zero-trust-network-nid-24589-cid-71.html CIO Review]
 +
* [http://www.laprensagrafica.com/2017/06/27/ataques-ciberneticos-solo-iran-en-aumento-a-menos-que-se-tomen-estas-medidas La Prensa Grafica]
 +
 
 +
== Scripts ==
 +
* [https://www.owasp.org/images/b/b8/DomainSubs.zip Compute Phishing Domain Substitutions]
  
 
==Classifications==
 
==Classifications==
Line 110: Line 99:
  
 
= Road Map and Getting Involved =
 
= Road Map and Getting Involved =
 +
 +
Road Map
 +
 +
Use the feedback received from version 1 of the document and use it to create an even more robust and comprehensive version 2 of the guide.
 +
 +
Get Involved
  
 
Involvement in the development and promotion of OWASP Anti-Ransomware Guide Project is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:
 
Involvement in the development and promotion of OWASP Anti-Ransomware Guide Project is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:
Line 120: Line 115:
 
=Project About=
 
=Project About=
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
{{Template:Project About
−
<span style="color:#ff0000">
+
| project_name =OWASP Anti-Ransomware Guide
−
This page is where you need to place your legacy project template page if your project was created before October 2013. To edit this page you will need to edit your project information template. You can typically find this page by following this address and substituting your project name where it says "OWASP_Example_Project". When in doubt, ask the OWASP Projects Manager.
+
| project_description =A guide and checklist organizations can use as the basis for creating a defense in depth strategy for combating ransomware and other types of malware.  
−
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project
+
| project_license =Creative Commons Attribution-ShareAlike 3.0 license: [http://creativecommons.org/licenses/by-sa/3.0/
−
</span>
+
| leader_name1 = Christopher Frenz
−
 
+
| leader_username1 = cfrenz
−
{{:Projects/OWASP_Example_Project_About_Page}}  
+
}}  
  
  

Latest revision as of 16:22, 17 December 2019

OWASP Project Header.jpg


The OWASP Anti-Ransomware Guide

Open up any newspaper or news site and an increasingly common headline is becoming “hospital held for ransom”. While hospitals and other organizations often have downtime procedures that let them revert back to paper for dealing with power outages and other disasters, it is still a nightmare scenario to find your entire organization's IT infrastructure screeching to a halt all because someone clicked on a malicious link or opened a questionable email attachment. Moreover, many organizations have a significant number of legacy systems that make security a challenge and beyond very basic security provisions often do not have a corporate culture that is heavily focused on information security. This has left many organizations struggling with how to handle ransomware attacks. The below is meant to serve as a comprehensive defense in depth based checklist and guide to preventing ransomware from taking a foothold in your organization as well as ensuring the proper procedures are in place to deal with an actual ransomware outbreak in your environment. Given the prevalence of Windows systems as ransomware targets, the guide is geared towards a Windows environment but is designed to be product agnostic. Please note that the list is designed to be comprehensive and as such not all controls may be applicable to all environments.

Project Description

A guide and checklist organizations can use as the basis for creating a defense in depth strategy for combating ransomware and other types of malware.

Licensing

The OWASP Anti-Ransomware guide is free to use. In fact it is encouraged!!! Additionally, we also encourage you to contribute back to the project.

The OWASP Anti-Ransomware Guide is licensed under the Creative Commons Attribution-ShareAlike 3.0 license, so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.

Project Leaders

Download

Spanish Translation

Presentation

News and Events

Scripts

Classifications

New projects.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files DOC.jpg

How can I participate in your project?

All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

If I am not a security expert can I participate in your project?

Yes, you can certainly participate in the project if you are not a security expert or technical. The project needs different skills and expertise and different times during its development.

Contributors

The OWASP Anti-Ransomware Guide project is developed by a worldwide team of volunteers.

The first contributors to the project were:

Road Map

Use the feedback received from version 1 of the document and use it to create an even more robust and comprehensive version 2 of the guide.

Get Involved

Involvement in the development and promotion of OWASP Anti-Ransomware Guide Project is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help: 

   Suggest Additional Security Controls
   Proof Reading
   Graphic Design
   Educate local communities
PROJECT INFO
What does this OWASP project offer you? 		RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: OWASP Anti-Ransomware Guide
Purpose: A guide and checklist organizations can use as the basis for creating a defense in depth strategy for combating ransomware and other types of malware.
License: Creative Commons Attribution-ShareAlike 3.0 license: [http://creativecommons.org/licenses/by-sa/3.0/
who is working on this project?
Project Leader(s):
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: N/A
Project Roadmap: Not Yet Created
Key Contacts
current release
Not Yet Published
last reviewed release
Not Yet Reviewed


other releases


Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Anti-Ransomware_Guide_Project&oldid=256421"