I have talked about three issues related to security, involving security audits and insights, source code security testing, data backup and recovery, today we will talk about access control and data credibility .
In the virtual world of the Internet, countless people interact and communicate in it, creating massive amounts of data and information. In this world, there are naturally malicious users who are deliberately unpredictable, hoping to obtain benefits through information. Therefore, service providers usually adopt a series of access control measures to isolate untrusted visitors.
So what is access control ?
Access control is to control the requested resource access based on authorization, prevent unauthorized access, and avoid unauthorized use, leakage, destruction, and tampering.
After preventing and controlling access rights, companies also need to care about the security of the data itself, including the credibility of the data submission, the compliance and quality of the submission, to avoid risk storage and affect online security.
The link is aimed at data credibility. Cloud-effect Codeup provides code GPG signature and rejects unsigned submissions; it supports code owner verification and restricts the owner of the submission record.
In terms of quality control, Cloud Effect Codeup refines the control of read and write permissions, supports the code submission card point mechanism, and guarantees the quality of submission.
Next, let's take a look at how to use these security protection functions of Cloud Effect Codeup.
Access control-IP whitelist
First of all, access control is to prevent danger from coming in. Codeup supports restrictions on the access IP of the warehouse, including page access restrictions and deployment key access restrictions.
- Page access restrictions: Including all the page access of Codeup, deployment key access, code cloning, downloading, submitting, merging and other behaviors are consistently restricted;
- Deployment key access: Fully consider the risk scenarios of deployment keys being embezzled due to poor management by personnel, and prohibit IP outside the whitelist from using deployment keys to access the corporate code base to strengthen the code base security;
Access control-code is not placed on the disk
Modern enterprises often need to hire outsourcing teams to support development work. However, due to the strong fluidity of outsourcing and relatively weak standardization, enterprises usually hope to limit the downloading rights of some personnel to the code, but how to carry out development work without downloading the code? Cloud-effect Codeup provides solutions for such scenarios.
If the code does not fall to the disk, the data does not fall on the local disk, to ensure that the code is not accidentally or maliciously taken away and leaked. It supports the setting of which roles are allowed to download the code to the local, and developers who cannot download the code are allowed to use the cloud WebIDE for development work.
Trustworthy data-GPG signature
GPG signature can prevent submission of forgery incidents. Although Git is password-level security, it is not foolproof. When the user's password is leaked, or someone wants to maliciously forge another person's submission, it is possible to impersonate a trusted person and submit malicious code to your code repository. You can use GPG to sign your submission record (Commit) or tag (Tag) locally, and Codeup will verify these signatures to ensure that the submission record or tag comes from a trusted source.
The data is credible-submit the owner to check
Before starting to use git for version management, we all know that user configuration needs to be done first.
git config --global user.name "your name"
git config --global user.email "your mailbox"
Maybe you use it every day, but do you know the difference between the author (Author) and the committer (Committer) who submit the record?
Git itself allows rewriting history, or submitting code on behalf of others. Usually, when we use git log to view historical commit records, the author is displayed. We often use Author as the attribution basis for code statistics. From this perspective, the author is directly linked to the code contributors. Therefore, in scenarios such as counting code contributions, it is necessary to standardize the correspondence between the owner of the submitted code and the currently logged-in user on the server.
When executing git commit, you can use --author to specify who is the contributor of this commit record. There are also such examples in the open source community. Although I did not use your code, I used your creativity and still regard you as the author to show respect for originality.
So simply understand that Author is the first author and Committer is the person who generated Commit. Codeup supports checking the authenticated cloud-effect primary mailbox of the currently logged-in user for Author and Committer. If the mailbox information cannot be matched, you can warn or prohibit its push to ensure the accuracy of the code contribution owner and avoid the failure of matching users. Contribution calculation distortion.
Data security-submission permission restriction
For enterprises, submitting to a remote library is usually a serious process. In order to standardize the submission format and restrict permissions, Codeup supports the submission rule settings at the enterprise and warehouse levels.
First of all, in the submission and push rules, support:
- Submit comment check: Commit Message must be described in accordance with the prescribed regular format, and push is allowed only when it matches;
- Submit email check: the submitter's (Committer) mailbox information needs to match the regular expression before it can be pushed;
- Prohibit forced push;
- Code Owner Check: Check whether the email of the author and submitter in the submission match with the primary email of the user on the cloud effect side. You can set two security levels: warning and prohibiting push;
In addition, in terms of submission permission control, support through the protection branch setting:
- Push rules: You can choose which roles are allowed to directly push code, and you can control that users are not allowed to directly submit to the protected branch, but must be merged and submitted after automated testing and manual review through merge requests to ensure that the contents of important branches are merged Credible and safe
- Merging rules: which types of roles have the authority to merge codes can be set;
In the most demanding scenario of data security, if each submission is required to undergo automated inspection and manual review, it can be set to not allow anyone to submit the code directly, and all submissions must be merged in after reviewing the merge request.
However, this situation may produce a lot of temporary development branches, which are not easy to manage. Don’t worry. Cloud-effect Codeup has complete support for the backbone-based R&D model, based on the innovative Agit-Flow (Alibaba centralized Git workflow). ), without creating a new branch, making creating a code review as easy as executing a git push command. Developers don’t need to switch tools and shorten the code review creation process, which originally took a few minutes to complete, to a few seconds. Isn’t it cool?
More capabilities
In addition to the above rich security features, there are more practical security capabilities waiting for you to discover, such as:
- Support DingTalk integrated and unified member authority security management, such as DingTalk organization member synchronization, automatic clearing of cloud effect side authority after Dingding organization member resigns, etc.;
- Enterprise-level code encryption is about to be released to ensure that the storage layer code data is highly encrypted. In the case of unauthorized keys, no one including the cloud efficiency service provider can decipher the stored content, strengthening the security of user data storage;
This article is the original content of Alibaba Cloud and may not be reproduced without permission.