You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+30-15Lines changed: 30 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,25 +1,33 @@
1
-
# Secure your CI with Cimon
1
+
# 🦫 Secure your CI with Cimon
2
2
3
-
Cimon (pronounced "Simon") detects and stops software supply-chain attacks, including those targeting SolarWinds and CodeCov, through a developer-friendly experience.
3
+

4
+
5
+
[Cimon](https://cimon.build) (pronounced "Simon") is a runtime security solution that detects and stops software supply-chain attacks on your pipeline, including those targeting SolarWinds and CodeCov, through easy onboarding and a developer-friendly experience.
4
6
5
7
By utilizing the revolutionary eBPF technology, Cimon monitors and mitigates attacks within the kernel, denying access to users' assets as soon as they arise.
6
8
9
+
Get started by installing the [GitHub App](https://github.com/marketplace/cimon-by-cycode), or learn more in our docs section - https://docs.cimon.build.
10
+
7
11
This action helps seamlessly deploy the agent into any desired GitHub Actions build. The action is based on the NodeJS engine and contains simple `pre` and `post` scripts to deploy and gracefully shut down the agent.
8
12
9
-
## Getting Started
13
+
## 🏃♂️ Getting Started with Cimon
14
+
15
+
Here's a simple three-step process to begin securing your GitHub Actions pipeline:
10
16
11
-
In order to integrate Cimon with GitHub, simply introduce the action in your GitHub Action workflow as follows:
17
+
- Step 1 - Install Cimon [GitHub App](https://github.com/marketplace/cimon-by-cycode). You will be directed to the Cimon platform once the process is complete.
18
+
- Step 2 - Generate an API key in the Cimon Platform, which consists of a client ID and a secret. These keys are used to authenticate the user and should be securely stored as GitHub Actions secrets.
19
+
- Step 3 - Add Cimon action to your workflow as the first step
20
+
21
+
We recommend starting Cimon in “Detect Mode” to allow it to learn your environment before applying preventive policies.
12
22
13
23
```yaml
14
-
steps:
15
-
- uses: cycodelabs/cimon-action@v0
16
-
with:
17
-
prevent: true
18
-
allowed-ips: ...
19
-
allowed-hosts: ...
24
+
- uses: cycodelabs/cimon-action@v0
25
+
with:
26
+
client-id: ${{ secrets.CIMON_CLIENT_ID }}
27
+
secret: ${{ secrets.CIMON_SECRET }}
20
28
```
21
29
22
-
## Usage
30
+
## 🔨 Usage
23
31
24
32
The action supports the following parameters:
25
33
@@ -43,13 +51,16 @@ The action supports the following parameters:
43
51
| `docker-password` | `false` | Password to pull image from registry (Used for debugging) |
Each pipeline run will report its findings through a security report embedded within the pipeline summary in GitHub Actions.
78
93
@@ -86,7 +101,7 @@ When the policy is set to "prevent", any security anomalies matching the profile
86
101
87
102

88
103
89
-
## Development
104
+
## 🪚 Development
90
105
91
106
Contributions to GitHub Action are welcome. After changes were made to the `src` folder, these changes should be reflected to the `dist` folder through the following build process:
92
107
@@ -103,6 +118,6 @@ The build script will update the actions' entry points code in the [dist](dist)
0 commit comments