Introducing Magalix Github Actions

Overview

Nowadays, embedding security within the development lifecycle has been crucial to organizations in order to mitigate threats and security attacks against their applications and infrastructure. Tech teams now are adopting security-as-code and shifting left practices to apply security guardrails as early as possible in the development cycle to reduce cybersecurity risks.

Magalix Github Actions is one step further to ensure customers have airtight cloud-native infrastructure throughout their software lifecycle, and help security, ops, and development teams on their journey to shift security left and enforce security and compliance early in the SDLC.

Magalix and GitHub Actions

With GitHub Actions, teams can now automate, customize, and execute their software development workflows in their own repository. Allowing for any customization, teams have the flexibility to create and share any jobs, such as CI/CD. And now, Magalix is now fully integrated with GitHub Actions.

With Magalix GitHub actions, teams will be able to get early feedback on their infrastructure-as-code (IaC) compliance and security, accelerate shipping of secure and compliant infrastructure, and catch any vulnerabilities at run-time.

Teams can now carry out comprehensive security checks, and enforce security policies at commit time and get instantaneous results right inside their developers’ favorite git tool, Github.

“One of our product goals is to support tech teams to shift their security left. With GitHub actions, we wanted to give our customers the ability to have security policies scanning integrated within their day-to-day workflows and to enable them to detect policy violations as early as possible in their SDLC. Having Github actions set up provides an extra layer of protection, which helps tech teams maintain security and compliance seamlessly within their Kubernetes clusters,” said Mostafa Megahid, Technical Product Manager at Magalix.

How to Use GitHub Actions

It’s really easy to get started with Magalix GitHub Actions,  you will need to do the following: 

1. Once you've signed in to your  Magalix account and connected your first Kuberenetes cluster, you will have access to setup KubeGuard.
2. If you don’t already have a guard that’s set up, go to KubeGuard and set up a new guard and add the policies you need to enforce at commit time.
3. Once it’s set up, copy the guard URL
4. In GitHub, add the guard URL to your secrets
5. Add the following action YAML to the repo you want to enforce the guard policies on.

 
# .github/workflows/magalix.yml
name: Magalix

on:
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]

jobs:
  magalix:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
    - name: Magalix
      uses: magalixcorp/magalix-action@main
      with:
        webhook: $	

After that, users will be able to see the violations report after each new commit or merge request right inside their GitHub dashboard.

To get a feel of how GitHub Actions works with Magalix Platform, start a committment-free 30-day trial.