Git Product home page Git Product logo

deprecated-patrol-rules-github's People

Contributors

alulsh avatar matiskay avatar npeternel avatar rclark avatar tmcw avatar vsmart avatar zmully avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

deprecated-patrol-rules-github's Issues

New/unused deploy keys

  1. Detect and alert on new deploy keys
  2. keys that haven't been used in X timeframe

It appears that there is no webhook event for new deployment keys, so that may not be possible to monitor easily if there are a large number of repositories (it would require polling all repositories looking for all keys < some age)

The alert on stale keys would need to poll all repos as well, so perhaps combining them does make sense.

Notification of creation of public gists

From @alulsh:

Github-bot should have a rule that audits the creation of public Gists by team members and screens for potentially sensitive information. For example, AWS secret keys, secret access tokens, financial or sales information.

This rule would run as often as possible - either every 5 minutes (Lambda scheduling limitation) or ideally would use push notifications (webhook + SNS set up?).

Sensitive information and terms would be stored in a dictionary. If a public Gist contains a dictionary it would fire off an alert to Pager Duty. Everything else would be captured in a daily email of new public Gists that day as another control since the dictionary will not catch all examples of sensitive information, especially initially.

Detect stale CI configurations

for instance, if a repository has a travis SNS integration still enabled and a CircleCI webhook, but has no .travis.yml or a recent build, this could alert or create an issue to remove the stale configuration.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.