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

Latest revision as of 16:22, 17 December 2019

Main
FAQs
Acknowledgements
Road Map and Getting Involved
Project About

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

Christopher M Frenz
Christian Diaz

Download

Spanish Translation

Spanish Version 1.4

Presentation

News and Events

Scripts

Compute Phishing Domain Substitutions

Classifications

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:

Christopher M Frenz
Christian Diaz

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): Christopher Frenz
how	can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: N/A
Project Roadmap: Not Yet Created
Key Contacts
Contact Christopher Frenz to contribute to this project Contact Christopher Frenz to review or sponsor this project

current release
Not Yet Published
last reviewed release
Not Yet Reviewed

other releases

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

Latest revision as of 16:22, 17 December 2019

The OWASP Anti-Ransomware Guide

Project Description

Licensing

Project Leaders

Download

Spanish Translation

Presentation

News and Events

Scripts

Classifications

How can I participate in your project?

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

Contributors

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

Reference

Tools

@@ Line 7: / Line 7: @@
 | 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 Security Principles==
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+==The OWASP Anti-Ransomware Guide==
-<span style="color:#ff0000">
-	This is where you need to add your more robust project description. A project description should outline the purpose of the project, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, and project leaders should ensure that the description is meaningful.
-</span>
-Inevitably applications are designed with security principles architects knew about, security folks included. However, as this project demonstrates there are far more than just a 'few' principles, most of which never make it into the design.
-For example, security design happens with perhaps a handful of principles:
+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.
-* Least Privilege
+==Project Description==
-* Perimeter Security
-* Defence in Depth
-However, we regularly see designs without '''separation of privilege'''!
+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.
-Think about that, most web applications today have all their eggs in a single basket. The business logic, the identities, passwords, products, policy enforcement, security rules are all found in the same application database that makes up the typical website! It is little wonder then, that attacks on the database have been so completely devastating, since there is no separation of privilege!
-The aim of this project, is to identify and describe a minimum functional set of principles that must be present in a secure design.
-==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.
 ==Licensing==
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+'''The OWASP Anti-Ransomware guide is free to use. In fact it is encouraged!!!
-<span style="color:#ff0000">
+'' Additionally, we also encourage you to contribute back to the project.
-	A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see [https://www.owasp.org/index.php/OWASP_Licenses OWASP Licenses]. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects.
-</span>
-'''The OWASP Security Principles are free to use. In fact it is encouraged!!!
+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.
-'' Additionally, I also encourage you to contribute back to the project. I have no monopoly on this knowledge; however, we all have pieces of this knowledge from our experience. Let's begin by putting our individual pieces together to make something great. Great things happen when people work together.
-The OWASP Security Principles are 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 -->
 | valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
-== What is OWASP Security Principles Project? ==
+== Project Leaders ==
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+* [https://www.owasp.org/index.php/User:Cfrenz Christopher M Frenz]
-<span style="color:#ff0000">
+* Christian Diaz
-	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.
+== 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]
-This document should serve as a guide to technical architects and designers outlining the fundamental principles of security.
+== Spanish Translation ==
+* [https://www.owasp.org/images/3/39/Guia_Contra_Ransomware.pdf Spanish Version 1.4]
 == Presentation ==
+* [https://youtu.be/bPyNzP7Gqig VMworld 2017]
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+* [https://www.slideshare.net/cfrenz/mockincidentsnymjcsc2016 NYMJCSC Presentation]
-<span style="color:#ff0000">
-	This is where you can link to slide presentations related to your project.
-</span>
-AppSec USA 2013 [https://github.com/OWASP/Security-Principles/tree/master/Presentations/AppSec%20NYC%202013]
-== Project Leader ==
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
-<span style="color:#ff0000">
-	A project leader is the individual who decides to lead the project throughout its lifecycle. The project leader is responsible for communicating the project’s progress to the OWASP Foundation, and he/she is ultimately responsible for the project’s deliverables. The project leader must provide OWASP with his/her real name and contact e-mail address for his/her project application to be accepted, as OWASP prides itself on the openness of its products, operations, and members.
-</span>
-* [https://www.owasp.org/index.php/User:Dennis_Groves Dennis Groves]
-== Related Projects ==
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
-<span style="color:#ff0000">
-	This is where you can link to other OWASP Projects that are similar to yours.
-</span>
-* [[OWASP_CISO_Survey]]
-== Openhub ==
-* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]
-<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
-| valign="top"  style="padding-left:25px;width:200px;" |
-== Quick Download ==
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
-<span style="color:#ff0000">
-	This is where you can link to your repository.
-</span>
-The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.
-However, if you like you may also download the master repository from the following links:
-* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]
-* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]
 == News and Events ==
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+* [http://nymjcsc.org/ 2016 NYMJCSC]
-<span style="color:#ff0000">
+* [https://iapp.org/news/a/why-the-wannacry-outbreak-should-be-a-wake-up-call/ IAPP Privacy Tech]
-	This is where you can link to press your project has been a part of. Appropriate press includes: Project Leader interviews, articles written about your project, and videos about your project.
+* [http://vmware.cioreview.com/cxoinsight/mitigating-malware-attacks-with-a-nsx-enabled-zero-trust-network-nid-24589-cid-71.html CIO Review]
-</span>
+* [http://www.laprensagrafica.com/2017/06/27/ataques-ciberneticos-solo-iran-en-aumento-a-menos-que-se-tomen-estas-medidas La Prensa Grafica]
-* [20 Nov 2013] News 2
+== Scripts ==
-* [30 Sep 2013] News 1
+* [https://www.owasp.org/images/b/b8/DomainSubs.zip Compute Phishing Domain Substitutions]
-== In Print ==
+==Classifications==
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
-<span style="color:#ff0000">
-	This is where you place links to where your project product can be downloaded or purchased, in the case of a book.
-</span>
-This project can be purchased as a print on demand book from Lulu.com
-==Classifications==
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
-<span style="color:#ff0000">
-	Here is where you can let the community know what project stage your project is currently in, whether the project is a builder, breaker, or defender project, and what type of project you are running.
-</span>
     {| width="200" cellpadding="2"
     |-
     | align="center" valign="top" width="50%" rowspan="2"| [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]
-   | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]]
     |-
     | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]
@@ Line 165: / Line 79: @@
 =FAQs=
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
-<span style="color:#ff0000">
-	Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'
-</span>
 ==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 programmer can I participate in your project?==
+==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 programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.
+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.
 = Acknowledgements =
@@ Line 192: / Line 100: @@
 = Road Map and Getting Involved =
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+Road Map
-<span style="color:#ff0000">
-	A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.
+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.
-</span>
-<span style="color:#ff0000">
+Get Involved
-	Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active.
-</span>
-As of October 2013, the priorities are:
+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:
-* Finish the referencing for each principle.
-* Update the Project Template.
-* Use the OWASP Press to develop a book.
-* Finish and publish the book on Lulu.
-Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!
+    Suggest Additional Security Controls
-You do not have to be a security expert in order to contribute.
+    Proof Reading
-Some of the ways you can help:
+    Graphic Design
-* Helping find references to some of the principles.
+    Educate local communities
-* Project administration support.
-* Wiki editing support.
-* Writing support for the book.
 =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}}
+}}