preface
This article has included making https://github.com/ponkans/F2E (a big monster is finishing the front-end knowledge skill tree), welcome to Star, continuously updated 💧
What, you haven’t even used GitHub? Just kidding, poof
I believe that every engineer has his or her own GItHub. As an open source platform, it brings us a lot of convenience, but if it is not properly used, it is easy to cause information leakage.
For example, there is a typical GitHub sensitive information disclosure vulnerability: employees of XXX company accidentally upload private information such as internal account number and password to GitHub, and malicious attackers use the information to attack the enterprise after discovering it. (You know, there are consequences. Poof!)
At this time, some partners are going to say, is there a security team, does the security side not do the corresponding protection measures? But that’s not what happened.
General start-up companies, the overall development of security awareness is very weak (but this is not completely the pot of development), let alone the security team, early capital is tight, quickly make the business run, operation system to keep up, product optimization, iteration is the core. So the safety side of the problem, it is easy to be ignored ~
A mature enterprise is likely to have a security team, after all, security is really important
The follow-up will slowly write some front-end security related articles, today only talk about GitHub information leakage how to prevent
So, to summarize the above questions:
- The safety awareness of enterprise employees is weak
- There is no professional security team to do code leak prevention
Ok, now that we’ve identified the problem, let’s talk about how to fix it.
The solution
Conscious side (hit auxiliary)
Generally speaking, the awareness of the safety side of the new is relatively weak, especially a lot of young partners just out of work.
Therefore, simple security training can be carried out for new employees to make them aware of the risk of uploading code to GitHub, and this system can be clearly identified as the red line of the enterprise system.
Technical Side (Front Line charge)
- Intranet isolation: Information leakage directly affects the interfaces that are exposed to the Extranet and exploited by attackers.
- Real-time monitoring (key) : a network isolation, although most of the scene has made no attack on the company, but, after all, is the enterprise factor would be more (such as the company’s assets, credit, etc.), so we need to do real-time monitoring, real-time monitoring can be found in the first place leakage of information and find the corresponding one to delete.
Isn’t there a security team? Who will develop the real-time monitoring system?
Since there is no development, then we can use open source, open source deployment, direct use of good ~
We use Docker to launch the project directly with one click.
Create monitoring tasks based on the enterprise.
According to the monitoring result, process the data.
Strange simple test, the speed is still very fast, real-time is very good.
conclusion
GitHub MONITOR is an open source system that can be used for sensitive information leaks.
- For details of the GitHub leak, recommend the friend security introduction article: https://feei.cn/gsil/
- About making MONITOR system USES the details, please go to the website for: https://github.com/VKSRC/Github-Monitor
Like the small partner to add a concern, a praise oh, Thanksgiving 💕😊
Contact me/public number
Wechat search “water monster” or scan the qr code below reply “add group”, I will pull you into the technical communication group. Honestly, in this group, even if you don’t talk, just reading the chat is a kind of growth. (Ali technical experts, aobing authors, Java3y, mogujie senior front end, Ant Financial security experts, all the big names).
The water monster will also be regular original, regular with small partners to exchange experience or help read the resume. Add attention, don’t get lost, have a chance to run together 🏃 ↓↓↓
