This feature is only available on paid plans
The Security Monitor provides an overview of all current security alerts.
The Security Monitor is available for the following languages:
- Shell script
- Visual Basic
The Security Monitor displays issues using security patterns from:
- Codacy Scalameta Pro
- ESLint (also: 1, 2, 3 and 4)
- SpotBugs (includes the plugin Find Security Bugs)
- Sonar C#
- Sonar VB.NET
- PHP Mess Detector
- Pylint (Python 2)
- Pylint (Python 3)
- PHP CodeSniffer
- XSS: XSS enables attackers to inject client-side scripts into web pages viewed by other users.
- Input validation: Input not validated may originate SQL Injection attacks for instance.
- File access: An attacker may use special paths to access files that shouldn't be accessible.
- HTTP: HTTP headers are a common attack vector for malign users.
- Cookies: An HTTP cookie is a small piece of data sent from a website and stored on the user's computer by the browser while the user is browsing.
- Unexpected behaviour: Assigning values to private APIs might lead to unexpected behavior.
- Mass assignment: Mass assignment is a feature of Rails which allows an application to create a record from the values of a hash.
- Insecure storage: Storing sensitive data using these APIs isn't safe.
- Insecure modules/libraries: Consider possible security implications associated with some modules.
- Visibility: Fields shouldn't have public accessibility.
- CSRF: Cross-Site Request Forgery (CSRF) is an attack that forces an end user to execute unwanted actions on a web application in which they're currently authenticated.
- Android: Android-specific issues.
- Malicious code: Exposed internal APIs can be accessed or changed by malicious code or by accident from another package.
- Cryptography: Cryptography is a security technique widely used and there are several cryptographic functions, but not all of them are secure.
- Command injection: Command injection is an attack in which the goal is the execution of arbitrary commands on the host operating system.
- Firefox OS: Sensitive APIs of Firefox OS.
- Auth: Authentication is present in almost all web applications nowadays.
- DoS: The Denial of Service (DoS) attack is focused on making a resource (site, application, server) unavailable for the purpose it was designed.
- SQL injection: A SQL injection attack consists of insertion or "injection" of a SQL query via the input data from the client to the application.
- Routes: Badly configured routes can give unintended access to an attacker.
- Regex: Regex can be used in a Denial of Service attack, that exploits the fact that most Regular Expression implementations may reach heavy computation situations that cause them to work very slowly (exponentially related to input size).
- SSL: Simply using SSL isn't enough to ensure the data you are sending is secure. Man in the middle attacks are well known and widely used.
- Other: Other language-specific security issues.
Each security category listed on the left-hand side of the dashboard has one of four states:
Everything is OK for this category
All the security patterns in this category are enabled, and no security issues have been found.
There are security patterns in this category that are disabled
You should enable the patterns in this category so it's verified. To enable all security patterns on the repository, click the button More and select Turn on all security patterns. If you're using configuration files, you must manually enable the listed patterns on your configuration files.
There are security issues identified for this category
Codacy can't determine if all the security patterns in this category are enabled or not
This happens when you're using configuration files to control which patterns are enabled. Ensure that you manually enable the listed patterns on your configuration files.
Share your feedback 📢
Did this page help you?
Thanks for the feedback! Is there anything else you'd like to tell us about this page?
255 characters left
We're sorry to hear that. Please let us know what we can improve:
255 characters left
Alternatively, you can create a more detailed issue on our GitHub repository.
Thanks for helping improve the Codacy documentation.
If you have a question or need help please contact email@example.com.