admin-2
/
Infosec_Reference
mirror of https://github.com/rmusser01/Infosec_Reference
1
1
Fork 0
Code Issues 0 Projects 0 Releases 0 Wiki Activity
Clone of https://github.com/rmusser01/Infosec_Reference . For those who would prefer to not be tracked by MS.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
410 Commits
1 Branch
51 MiB
 
 
Tree: 60ff8da689
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '60ff8da689'
${ noResults }
Infosec_Reference/README.md

7.6 KiB
Raw Blame History

InfoSec_Reference

An Information Security Reference That Doesn't Suck

Goal:

  • Be an awesome Information Security Reference
  • List of techinques, tools and tactics to learn from/reference.
    • Rich resource of infosec knowledge for anyone to browse through as a jumping off point for various niches OR as a reference/recall method for stuff.
    • Something like a "Yellow Pages" in the sense of you know something exists, but what was it called....
      • 'If you give a man a fish, he is hungry again in an hour. If you teach him to catch a fish, you do him a good turn.'
  • Always accepting more links/stuff. Feel free to make a pull request or a complaint through a pull request or filing a bug
  • Why Do You Care?
    • Don't have to constantly google for tools/reminder.
    • Easily browsable list of tools, techniques, papers, and research in all sorts of areas.
    • Want to read some good info.
  • Why Do I Care?
    • I do this as a resource to learn and help others, and offer it publicly as a way of giving back to the general community.
    • To be clear, these aren't personal notes. I keep this repo maintained as a way of having pointers to information that I feel might help build someone's skillset or increase their understanding of attacks/methods/defenses. This is not meant to condone illegal or malicious activities.
  • This page

Index - Table of Contents