Friday, March 29, 2024

Default Setup – A New Option to Set Up Code Scanning on GitHub

The GitHub code scanning feature has been enhanced with a new option called “default setup,” designed to assist developers in setting up code scanning with only a few clicks and make it easier to configure it automatically.

GitHub’s code scanning is powered by the CodeQL code analysis engine. This engine supports many languages and compilers, including those that power GitHub’s code analysis. Only the following language repositories have the new option available to them:- 

Over the next six months, Walker Chabbott, GitHub’s product marketing manager, declared that the company is looking at expanding its support to a number of languages, GitHub Said.

How to use the new code scanning setup option?

Here are the simple steps you need to follow in order to use the new option for setting up code scanning:-

  • First of all, in your repo’s settings, you have to navigate to “Code security and analysis”.
  • Then click the “Set up” drop-down menu.
  • After that choose the Default option.
  • That’s it, now you are done.

The default configuration summary will be automatically generated based on repository contents when you click on this ‘Default’ option.

There are a number of things that fall under this category, including:-

  • Languages detected in the repository
  • Query packs that will be used
  • Events that will trigger scans

This option will be customizable in the future so that users can choose what works best for them. When you click “Enable CodeQL,” it will begin scanning the repo for vulnerabilities to help you create more secure software by finding and patching the flaws it discovers.

Since Semmle code-analysis platform was acquired by GitHub in September 2019, the CodeQL code-analysis engine has been added to its capabilities to further enhance the GitHub platform.

In May 2020, GitHub Satellite announced the first beta version of its code scanning solution, and in September 2020, the service was made generally available.

In addition to code scanning, GitHub offers an advanced security feature for GitHub Enterprise private repositories as part of its advanced security features, which is free for all public repositories on GitHub.

Network Security Checklist – Download Free E-Book

Website

Latest articles

Beware Of Weaponized Air Force invitation PDF Targeting Indian Defense And Energy Sectors

EclecticIQ cybersecurity researchers have uncovered a cyberespionage operation dubbed "Operation FlightNight" targeting Indian government...

WarzoneRAT Returns Post FBI Seizure: Utilizing LNK & HTA File

The notorious WarzoneRAT malware has made a comeback, despite the FBI's recent efforts to...

Google Revealed Kernel Address Sanitizer To Harden Android Firmware And Beyond

Android devices are popular among hackers due to the platform’s extensive acceptance and open-source...

Compromised SaaS Supply Chain Apps: 97% of Organizations at Risk of Cyber Attacks

Businesses increasingly rely on Software as a Service (SaaS) applications to drive efficiency, innovation,...

IT and security Leaders Feel Ill-Equipped to Handle Emerging Threats: New Survey

A comprehensive survey conducted by Keeper Security, in partnership with TrendCandy Research, has shed...

How to Analyse .NET Malware? – Reverse Engineering Snake Keylogger

Utilizing sandbox analysis for behavioral, network, and process examination provides a foundation for reverse...

GoPlus’s Latest Report Highlights How Blockchain Communities Are Leveraging Critical API Security Data To Mitigate Web3 Threats

GoPlus Labs, the leading Web3 security infrastructure provider, has unveiled a groundbreaking report highlighting...
Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Mitigating Vulnerability Types & 0-day Threats

Mitigating Vulnerability & 0-day Threats

Alert Fatigue that helps no one as security teams need to triage 100s of vulnerabilities.

  • The problem of vulnerability fatigue today
  • Difference between CVSS-specific vulnerability vs risk-based vulnerability
  • Evaluating vulnerabilities based on the business impact/risk
  • Automation to reduce alert fatigue and enhance security posture significantly

Related Articles