-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
ae65288
commit 8fa1623
Showing
23 changed files
with
1,296 additions
and
99 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,59 @@ | ||
*.gem | ||
*.rbc | ||
/.config | ||
/coverage/ | ||
/InstalledFiles | ||
/pkg/ | ||
/spec/reports/ | ||
/spec/examples.txt | ||
/test/tmp/ | ||
/test/version_tmp/ | ||
/tmp/ | ||
|
||
# Used by dotenv library to load environment variables. | ||
# .env | ||
|
||
# Ignore Byebug command history file. | ||
.byebug_history | ||
|
||
## Specific to RubyMotion: | ||
.dat* | ||
.repl_history | ||
build/ | ||
*.bridgesupport | ||
build-iPhoneOS/ | ||
build-iPhoneSimulator/ | ||
|
||
## Specific to RubyMotion (use of CocoaPods): | ||
# | ||
# We recommend against adding the Pods directory to your .gitignore. However | ||
# you should judge for yourself, the pros and cons are mentioned at: | ||
# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control | ||
# | ||
# vendor/Pods/ | ||
|
||
## Documentation cache and generated files: | ||
/.yardoc/ | ||
/_yardoc/ | ||
/doc/ | ||
/rdoc/ | ||
|
||
## Environment normalization: | ||
/.bundle/ | ||
/vendor/bundle | ||
/lib/bundler/man/ | ||
|
||
# for a library or gem, you might want to ignore these files since the code is | ||
# intended to run in multiple environments; otherwise, check them in: | ||
# Gemfile.lock | ||
# .ruby-version | ||
# .ruby-gemset | ||
|
||
# unless supporting rvm < 1.11.0 or doing something fancy, ignore this: | ||
.rvmrc | ||
|
||
# Used by RuboCop. Remote config files pulled in from inherit_from directive. | ||
# .rubocop-https?--* | ||
|
||
# Mac | ||
.DS_Store |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,66 @@ | ||
# Contributing to ADR Runbooks | ||
|
||
Thank you for your interest in contributing to Contrast Security's Application Detection and Response Runbooks. This document provides guidelines for contributions. | ||
|
||
## How to Contribute | ||
|
||
1. Fork the repository | ||
2. Create a new branch for your changes | ||
3. Make your changes | ||
4. Submit a pull request | ||
|
||
## Runbook Structure | ||
|
||
Each runbook should follow this structure: | ||
|
||
```markdown | ||
--- | ||
layout: runbook | ||
title: "Title of the Runbook" | ||
description: "Brief description of the security issue and its impact" | ||
--- | ||
|
||
# Title | ||
|
||
Brief introduction explaining the security issue. | ||
|
||
## Example Events | ||
|
||
Include example events showing different outcomes (Exploited, Blocked, etc). | ||
|
||
## Decision Tree | ||
|
||
Clear steps for triaging the event type. | ||
|
||
## Response Procedures | ||
|
||
Detailed procedures based on event outcome. | ||
|
||
## Post-Incident Activities | ||
|
||
Steps for documentation and follow-up. | ||
``` | ||
|
||
## Style Guidelines | ||
|
||
- Use clear, concise language | ||
- Include relevant code examples | ||
- Add decision trees for complex procedures | ||
- Include example events where applicable | ||
- Document post-incident procedures | ||
|
||
## Review Process | ||
|
||
1. All contributions will be reviewed for: | ||
- Technical accuracy | ||
- Adherence to style guidelines | ||
- Clarity and completeness | ||
- Formatting consistency | ||
|
||
2. Make requested changes if any are needed | ||
|
||
3. Once approved, changes will be merged | ||
|
||
## Code of Conduct | ||
|
||
Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
source 'https://rubygems.org' | ||
|
||
gem 'github-pages', group: :jekyll_plugins | ||
gem 'jekyll-remote-theme' | ||
gem 'jekyll-seo-tag' | ||
gem 'kramdown' | ||
gem 'rouge' |
Oops, something went wrong.