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 Security Operations Center (SOC) Framework Project"

From OWASP
Jump to: navigation, search
m (Project Leader)
(Presentation uploaded, Link of presentation added in Quick Download and Presentation Heading, Name of Eduardo Estevao added in Other Contributors, Formatting done on Description)
 
(15 intermediate revisions by the same user not shown)
Line 6: Line 6:
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
| 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">
+
==OWASP SOC Framework Project==
−
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.
+
A documented Framework for Cyber Security Operations Center (SOC), to develop its Strategy and Design; Setting up , Operate, Manage, Govern, Improve and Innovate SOC.  
−
</span>
 
  
−
==The OWASP Security Principles==
+
Currently there is no such framework available from any Government, Non-Government or Commercial Organization.
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
==Description==
−
<span style="color:#ff0000">
+
A documented Framework for Cyber Security Operations Center (SOC), to develop its Strategy and Design; Setting up , Operate, Manage, Govern, Improve and Innovate SOC.
−
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>
 
  
−
A documented architecture framework for Security Operations Center (SOC), to develop its Strategy and Design, Setting up , Operate, Manage, Govern, Improve and Innovate SOC. Currently there is no such framework available from any Government, Non-Government or Commercial Organization.
+
Currently there is no such framework available from any Government, Non-Government or Commercial Organization.
  
−
This Framework will address at least following:
+
The Deliverable of this project will be as follows:
  
−
A) Model
+
Security Operations Center (SOC) Framework
  
−
1. Distributed
+
''<u>Trainings:</u>''
  
−
2. Centralized
+
Security Operations Center (SOC) Analyst
  
−
3. Collaborative
+
Security Operations Center (SOC) Manager
  
−
4. Constituency
+
''<u>Other Documents:</u>''
  
−
5. Managed
+
Security Operations Center (SOC) Assessment
  
−
6. Hybrid
+
Security Operations Center (SOC) Maturity Model
−
 
 
−
B) Process Flow
 
−
 
 
−
1. Identify
 
−
 
 
−
2. Consolidation
 
−
 
 
−
3. Correlation
 
−
 
 
−
4. Intelligence
 
−
 
 
−
5. Monitoring
 
−
 
 
−
6. Alert
 
−
 
 
−
7. Reporting
 
−
 
 
−
8. Dashboard
 
−
 
 
−
9. Detection
 
−
 
 
−
a) Signatures
 
−
 
 
−
b) Behavior
 
−
 
 
−
10. Analysis
 
−
 
 
−
11. Communication
 
−
 
 
−
12. Prioritizing
 
−
 
 
−
13. Escalation
 
−
 
 
−
14. Authority
 
−
 
 
−
15. Response
 
−
 
 
−
a) Manual
 
−
 
 
−
b) Automated
 
−
 
 
−
c) Active
 
−
 
 
−
d) Passive
 
−
 
 
−
16. Containment
 
−
 
 
−
17. Forensic Investigation
 
−
 
 
−
18. Recovery
 
−
 
 
−
19. Learning
 
−
 
 
−
20. Optimization
 
−
 
 
−
a) Blacklisting
 
−
 
 
−
b) White-listing
 
−
 
 
−
21. Metrics
 
−
 
 
−
C) People & Skills
 
−
 
 
−
1. SOC Analyst
 
−
 
 
−
2. Incident Handler
 
−
 
 
−
3. SOC Expert
 
−
 
 
−
4. Admins
 
−
 
 
−
5. SOC Manager
 
−
 
 
−
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:
 
−
 
 
−
* Least Privilege
 
−
* Perimeter Security
 
−
* Defence in Depth
 
−
 
 
−
However, we regularly see designs without '''separation of privilege'''!
 
−
 
 
−
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>
 
−
 
 
−
A documented architecture framework for Security Operations Center (SOC), to develop its Strategy and Design, Setting up , Operate, Manage, Govern, Improve and Innovate SOC.
 
−
 
 
−
'''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==
 
==Licensing==
 +
'''The OWASP SOC Framework is free to use.'''
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
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 to this one.
−
<span style="color:#ff0000">
 
−
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!!!'''
 
−
'' 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 -->
+
''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.''
−
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
 
  
−
== What is OWASP Security Principles Project? ==
+
<!-- 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;" |
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
== What is OWASP SOC Framework Project? ==
−
<span style="color:#ff0000">
+
The end goal is to document a Framework for Cyber Security Operations Center (SOC), which will guide in Strategy Design, Setting up , Operate, Manage, Govern, Improve and Innovate a SOC. Currently there is no such framework available from any Government, Non-Government or Commercial Organization.
−
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.
+
Once this is well organised, I think it would be great to publish this through the 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.
+
This document should serve as a guide to technical Architects, Designers, Implementers, Managers, Administrators, Experts, Incident Handlers, and Analysts about their roles and responsibilities in a Cyber Security Operation Center (SOC).
  
 
== Presentation ==
 
== Presentation ==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
[https://www.owasp.org/images/0/0a/OWASP_Security_Operations_Centre_%28SOC%29_Framework_Project_Presentation.pdf OWASP SOC Framework]<br>
−
<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 ==
 
== Project Leader ==
  
Line 181: Line 58:
 
== Related Projects ==
 
== Related Projects ==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
* [[OWASP Open Cyber Security Framework Project]]
−
<span style="color:#ff0000">
 
−
This is where you can link to other OWASP Projects that are similar to yours.
 
−
</span>
 
−
 
 
−
* [[OWASP_CISO_Survey]]
 
  
 
== Openhub ==
 
== Openhub ==
Line 196: Line 68:
  
 
== Quick Download ==
 
== Quick Download ==
−
 
+
* [https://www.owasp.org/images/0/0a/OWASP_Security_Operations_Centre_%28SOC%29_Framework_Project_Presentation.pdf OWASP SOC Framework Presentation - PDF]
−
<!-- 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 ==
 
== News and Events ==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
* [21 Feb 2019] Presentation Published
−
<span style="color:#ff0000">
+
* [24 Jan 2018] [https://youtu.be/amJGiqEm48s Presentation at SecOps Europe 2018]
−
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.
+
* [2 May 2017] Project Initiation
−
</span>
+
* [3 Mar 2017] Project Request
 +
* [Feb 2017] Project Conception
  
−
* [20 Nov 2013] News 2
+
== In Print ==
−
* [30 Sep 2013] News 1
 
  
−
== In Print ==
+
Coming Soon
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
== Mailing List ==
−
<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
+
* [https://lists.owasp.org/mailman/listinfo/owasp-socframework-project Mailing List]
  
 
==Classifications==
 
==Classifications==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
{| width="200" cellpadding="2"
−
<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"
 
 
   |-
 
   |-
 
   | rowspan="2" align="center" valign="top" width="50%" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]
 
   | rowspan="2" align="center" valign="top" width="50%" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]
Line 248: Line 102:
 
|}
 
|}
  
−
=FAQs=
+
=OWASP SOC Framework=
 +
OWASP Security Operations Center (SOC) Framework will address at least following:
  
−
<!-- 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>
 
  
 +
A) Model
 +
# Distributed
 +
# Centralized
 +
# Collaborative
 +
# Constituency
 +
# Managed
 +
# Hybrid
 +
B) Process Flow
 +
# Identify
 +
# Consolidation
 +
# Correlation
 +
# Intelligence
 +
# Monitoring
 +
# Alert
 +
# Reporting
 +
# Dashboard
 +
# Detection (Signatures/ Behavior)
 +
# Analysis
 +
# Communication
 +
# Prioritizing
 +
# Escalation
 +
# Authority
 +
# Response (Manual/  Automated/ Active/ Passive)
 +
# Containment
 +
# Forensic Investigation
 +
# Recovery
 +
# Learning
 +
# Optimization (Blacklisting/ White-listing)
 +
# Metrics
 +
C) People & Skills
 +
# SOC Analyst
 +
# Incident Handler
 +
# SOC Expert
 +
# Admins
 +
# SOC Manager
  
 +
=FAQs=
 
==How can I participate in your project?==
 
==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.  
 
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.  
Line 264: Line 151:
 
= Acknowledgements =
 
= Acknowledgements =
  
−
==Contributors==
+
Project Leader
−
 
+
* [[User:Faisal.naqvi|Muhammad Faisal Naqvi]]
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project.
 
−
Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project.
 
−
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.
 
−
</span>
 
−
 
 
−
The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project  [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].
 
  
−
The first contributors to the project were:
+
Other Contributors
−
 
+
* Eduardo Estevao
−
* [https://www.owasp.org/index.php/User:Dennis_Groves Dennis Groves]
+
* Your Name can also appear here
−
* [https://github.com/sublimino Andrew Martin]
 
−
* [https://github.com/Lambdanaut Josh Thomas]
 
−
* '''YOUR NAME BELONGS HERE'''
 
  
 
= Road Map and Getting Involved =
 
= Road Map and Getting Involved =
−
 
−
<!-- 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 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.
 
−
</span> 
 
−
 
−
<span style="color:#ff0000">
 
−
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>
 
−
 
−
Currently there is no Security Operations Center (SOC) framework available from any Government, Non-Government or Commercial Organization.
 
  
 
The project road map is to develop, review and publish the following documents by 2018:
 
The project road map is to develop, review and publish the following documents by 2018:
Line 301: Line 166:
 
Security Operations Center (SOC) Framework
 
Security Operations Center (SOC) Framework
  
−
Trainings & Presentations:
+
Trainings:
  
 
Security Operations Center (SOC) Analyst
 
Security Operations Center (SOC) Analyst
−
 
−
Security Operations Center (SOC) Expert
 
  
 
Security Operations Center (SOC) Manager
 
Security Operations Center (SOC) Manager
Line 316: Line 179:
  
 
Involvement in the development and promotion of the 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 the project is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:
−
 
+
* Translations
−
Translations
+
* Support for Training Development
−
 
+
* Helping find references to some of the areas
−
Industry Verticals Recommendations and Case Study
+
* Project administration support.
−
 
 
−
As of October 2013, the priorities are:
 
−
* 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!
 
−
You do not have to be a security expert in order to contribute.
 
−
Some of the ways you can help:
 
−
* Helping find references to some of the principles.
 
−
* Project administration support.  
 
 
* Wiki editing support.
 
* Wiki editing support.
−
* Writing support for the book.
+
* Writing support for the book
−
 
+
For involvement in the project or for any feedback/ query, please contact the Project Leader here: [https://www.linkedin.com/in/mfaisalnaqvi/ '''Muhammad Faisal Naqvi,''' ''CISSP, CISA, AMBCI, ITIL, ISMS LA n Master'']
−
=Project About=
+
__NOTOC__ <headertabs></headertabs>
−
 
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
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.
 
−
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project
 
−
</span>
 
−
 
 
−
{{:Projects/OWASP_Example_Project_About_Page}}
 
−
 
 
−
 
 
−
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
−
__NOTOC__ <headertabs></headertabs>  
 
−
 
 
 
[[Category:OWASP Project]]   
 
[[Category:OWASP Project]]   
 
[[Category:OWASP_Builders]]  
 
[[Category:OWASP_Builders]]  
 
[[Category:OWASP_Defenders]]   
 
[[Category:OWASP_Defenders]]   
 
[[Category:OWASP_Document]]
 
[[Category:OWASP_Document]]

Latest revision as of 07:16, 21 February 2019

OWASP Project Header.jpg

OWASP SOC Framework Project

A documented Framework for Cyber Security Operations Center (SOC), to develop its Strategy and Design; Setting up , Operate, Manage, Govern, Improve and Innovate SOC.

Currently there is no such framework available from any Government, Non-Government or Commercial Organization.

Description

A documented Framework for Cyber Security Operations Center (SOC), to develop its Strategy and Design; Setting up , Operate, Manage, Govern, Improve and Innovate SOC.

Currently there is no such framework available from any Government, Non-Government or Commercial Organization.

The Deliverable of this project will be as follows:

Security Operations Center (SOC) Framework

Trainings:

Security Operations Center (SOC) Analyst

Security Operations Center (SOC) Manager

Other Documents:

Security Operations Center (SOC) Assessment

Security Operations Center (SOC) Maturity Model

Licensing

The OWASP SOC Framework is free to use.

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 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.

What is OWASP SOC Framework Project?

The end goal is to document a Framework for Cyber Security Operations Center (SOC), which will guide in Strategy Design, Setting up , Operate, Manage, Govern, Improve and Innovate a SOC. Currently there is no such framework available from any Government, Non-Government or Commercial Organization.

Once this is well organised, I think it would be great to publish this through the 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, Designers, Implementers, Managers, Administrators, Experts, Incident Handlers, and Analysts about their roles and responsibilities in a Cyber Security Operation Center (SOC).

Presentation

OWASP SOC Framework

Project Leader

Muhammad Faisal Naqvi


Related Projects

Openhub

Quick Download

News and Events

  • [21 Feb 2019] Presentation Published
  • [24 Jan 2018] Presentation at SecOps Europe 2018
  • [2 May 2017] Project Initiation
  • [3 Mar 2017] Project Request
  • [Feb 2017] Project Conception

In Print

Coming Soon

Mailing List

Classifications

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

OWASP Security Operations Center (SOC) Framework will address at least following:


A) Model

  1. Distributed
  2. Centralized
  3. Collaborative
  4. Constituency
  5. Managed
  6. Hybrid

B) Process Flow

  1. Identify
  2. Consolidation
  3. Correlation
  4. Intelligence
  5. Monitoring
  6. Alert
  7. Reporting
  8. Dashboard
  9. Detection (Signatures/ Behavior)
  10. Analysis
  11. Communication
  12. Prioritizing
  13. Escalation
  14. Authority
  15. Response (Manual/ Automated/ Active/ Passive)
  16. Containment
  17. Forensic Investigation
  18. Recovery
  19. Learning
  20. Optimization (Blacklisting/ White-listing)
  21. Metrics

C) People & Skills

  1. SOC Analyst
  2. Incident Handler
  3. SOC Expert
  4. Admins
  5. SOC Manager

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?

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.

Project Leader

Other Contributors

  • Eduardo Estevao
  • Your Name can also appear here

The project road map is to develop, review and publish the following documents by 2018:

Main Project:

Security Operations Center (SOC) Framework

Trainings:

Security Operations Center (SOC) Analyst

Security Operations Center (SOC) Manager

Other Documents:

Security Operations Center (SOC) Assessment

Security Operations Center (SOC) Maturity Model

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

  • Translations
  • Support for Training Development
  • Helping find references to some of the areas
  • Project administration support.
  • Wiki editing support.
  • Writing support for the book

For involvement in the project or for any feedback/ query, please contact the Project Leader here: Muhammad Faisal Naqvi, CISSP, CISA, AMBCI, ITIL, ISMS LA n Master

Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Security_Operations_Center_(SOC)_Framework_Project&oldid=247700"