Both SAST and DAST are complementary to each other. The best approach is to include both SAST and DAST.
SAST: Inspects underlying source code, requires understanding of source design, Is utilized early in the development cycle and the average cost to remediate issues is low
DAST: Requires the application running, performs hacker-like (black box) testing,
Utilized much later in the development cycle and the average cost to remediate issues is higher
If we look at OWASP Top 10 2021 changes, SAST or DAST will not cover all of them individually. In addition, we also need SCA to be done to look at open source vulnerabilities.
Principal Advisor at Pro4:Six CISO Services and Consulting
User
2020-06-30T14:50:22Z
Jun 30, 2020
SAST and DAST are not mutually exclusive and should be used in conjunction with each other. One should be used by the developers to ensure security is being addressed as they are writing the code. The other is used for evaluating existing applications already in production to ensure they are not susceptible to any new vulnerabilities that have been discovered.
The real question is which should have a higher priority when it comes to introducing the concepts into your application security model. Unfortunately, there is no single answer to which comes first. It all depends on your organizations culture, business model, and your relationships with the various impacted groups.
For application security you ideally need SAST, SCA and DAST. You need all three as they essentially measure different things:
SAST identifies bad coding practices that potentially could be exploited
SCA identifies known vulnerabilities in the libraries and components you are using and this is the main attack vector on applications.
DAST identifies some of the weaknesses that SAST and SCA identified, but also identifies weaknesses in the configuration. You might have the perfect application code with zero vulnerabilities, but if it is misconfigured, for instance using a default password, it still can be breached.
If you have to choose, look at SCA and then DATS first as that gives you the best bang for your buck from a risk reduction perspective
It’s a false choice of a question but DAST exist because folks don’t trust their SAST tool. DAST is good about true positives but bad about false negatives. SAST just has a reputation for false positives but a new generation of SAST tools do a much better job.
VP and Sr. Manager at a financial services firm with 1,001-5,000 employees
Real User
2020-06-24T22:48:26Z
Jun 24, 2020
Both. They are not in competition with each other. SAST is used for analyzing your written code for practices and patterns that are risky or vulnerable. DAST is used @ runtime for analyzing the app for vulnerabilities as shown in other ways on the runtime memory stack, etc. Both provide different value.
Automating security for a CI/CD pipeline is essential in ensuring the safety and reliability of your applications. Security automation helps organizations automate the process of validating security policies, patching vulnerabilities, ensuring regulatory compliance with industry standards, and maintaining application integrity.
When considering automating security for your CI/CD pipeline there are three main components you should pay attention to: Policy Validation, Vulnerability Scanning & Patching, and Regulatory Compliance & Governance.
Policy Validation aims to ensure that all changes made during deployment align with existing organizational policies. Automated policy validation should use configuration management tools such as Ansible or Puppet to scan source code repositories like GitHub or GitLab for any changes made prior to deployments into production environments. This can be integrated into continuous integration pipelines so that any non-compliant changes are flagged before reaching an active environment.
Vulnerability Scanning & Patching ensures that any known vulnerabilities which may have been introduced via a new code commit or change in existing infrastructure configurations will be identified prior to deployment allowing appropriate remediation action to take place such as blocking the release until fixes can be applied or automatically applying patches where possible before the change is deployed in production environments. These activities can also be automated by integrating scanning tools such as Nmap directly into CI/CD pipelines so they execute at each stage performing active scans on exposed networks and services before allowing progression through the pipeline toward production systems.
Finally, Regulatory Compliance & Governance involves recognizing issues that require manual authorization from an administrator before consideration of an automated fix or deployment occurs (such as legal/privacy restrictions). It also includes monitoring external sources related to potential threats relevant specifically related to your organization (such as data breaches on other organizations), overseeing audit logs produced from actions taken within both source control platforms and cloud provider resources used within the CI/CD pipeline itself (for example developer keys used when accessing private resources). Automation here would include continually analyzing audit logs generated from activities performed throughout various stages of the delivery process permitting immediate detection of anomalies against expected behavior based on user roles assigned within each project being worked upon.
Network Security Services at ACE Managed Securty Services
Mar 20, 2023
When it comes to security and automation, there's no such thing as too much. That's why it makes sense to take steps to automate security for your CI/CD pipeline. Automation can help reduce the time spent on manual tasks and ensure that your code is secure before it makes its way into production. Here are some tips for automating security for your CI/CD pipeline:
1. Use a static application security testing (SAST) solution to scan code for vulnerabilities. SAST solutions can help identify and fix known issues quickly and efficiently.
2. Run regular scans of your codebase using a dynamic application security testing (DAST) tool. This will help identify any new security issues in real time.
3. Use a container scanning tool to check all your images and containers for vulnerabilities or misconfigurations. This will help ensure that no malicious code can enter the pipeline.
4. Utilize an API scanner to detect potential API vulnerabilities in your applications, such as SQL injection, cross-site scripting, and parameter tampering.
5. Implement a Web Application Firewall (WAF) to protect your applications from attacks like DDoS or brute force attacks. This can help prevent attackers from accessing sensitive information.
Using IaC to automate the provisioning of infrastructure removes that task from your devs or admins. They don't need to manually provision and manage infra resources such as operating systems, servers, and storage every time they start deploying or developing an app. With IaC, you provision via templates, which helps enforce rules, policies, and consistency.
There are a bunch of cloud-supplier and third-party tools that automate the enforcement of rules and policies for IaC. All of them, to varying extents, aim at making sure your infrastructure is secure and compliant.
A couple of the better-known solutions are HashiCorp Terraform and Red Hat Ansible Automation Platform. Both are advanced-level platforms for implementing complicated applications.
Terraform is an open-source tool that allows you to define and manage your infrastructure as code. You can define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. It includes resource planning, provisioning, and validation. Terraform can also be used with policy as code tools, such as Open Policy Agent, to enforce security policies on IaC.
Red Hat Ansible Automation Platform enables you to create, share, and manage automation, including for development and operations as well as security and network teams.
The major cloud providers also enter the fray, of course. AWS CloudFormation enables you to model and provision both AWS and third-party application resources in your cloud environment. You can use either programming languages or a text file to model and provision automatically and securely for all application resources, regions, and accounts. Azure Resource Manager enables you to provision and manage infrastructure and configuration with declarative definition files using JSON templates. And Google Cloud Deployment Manager uses template and configuration files to deploy Google's Cloud Storage, Compute Engine, and Cloud SQL, configured to work together.
Chef InSpec is an open-source tool with human- and machine-readable language for testing and auditing infrastructure as code. It includes a domain-specific language for defining tests and can be used to validate that infrastructure code meets compliance and security requirements.
Pulumi bills itself as "guaranteeing the infrastructure software supply chain." It has integrations with the major CI/CD platforms, enabling validation of change through testing of built-in policies.
And Spacelift's calling card says that it is "the most flexible IaC management platform."
IaC tools such as-
Terraform
Ansible
AWS CloudFormation
Azure Resource Manager
Google Cloud Deployment Manager
Chef
Puppet
SaltStack
( R )
Vagrant
Promote the best practices which are necessary to make the process of building and configuring the infrastructure more competitive and effective, reducing the costs and effort involved.
We’re launching an annual User’s Choice Award to showcase the most popular B2B enterprise technology products and we want your vote!
If there’s a technology solution that’s really impressed you, here’s an opportunity to recognize that. It’s easy: go to the PeerSpot voting site, complete the brief voter registration form, review the list of nominees and vote. Get your colleagues to vote, too!
...
What is OWASP?
The OWASP or Open Web Application Security Project is a nonprofit foundation dedicated to improving software security. It operates under an open community model, meaning that anyone can participate in and contribute to OWASP-related online chats and projects. The OWASP ensures that its offerings (online tools, videos, forums, events, etc.) remain free and are easily accessible t...
Hi community members,
Here is our new Community Spotlight for YOU. We publish it to help you catch up on recent contributions by community members.
Do you find it useful? Please comment below!
Trending
Top HCI in 2022
What are the main differences between XDR and SIEM?
Articles
Top 5 Ethernet Switches in 2022
SASE: what is it and what are the main benefits?
Questions
Che...
Privacy Concerns in an RPA Implementation Program.
The biggest concern we (as RPA solution implementors) have faced when interacting with clients and customers were:
1. Regulatory and Compliance issues.
2. InfoSec and Security issues.
3. Audit Issues.
Regulatory and Compliance Issues: There is a huge penalty if the wrong data gets updated and emails are sent to customers by the regulatory...
ICT is getting more and more complex: today I have several systems in Chicago, several more in Amsterdam and if you need to protect your environment you will need to check on-premises, the cloud at Amazon, and the cloud at Microsoft Azure.
Why is Performance related to security?
For the following reasons:
Today we need more than one tool to protect our environment. You need anti-spoofing...
The easiest way to remember the role of each:
SCA & SAST = Am I Vulnerable
DAST & IAST = Am I Exploitable (In some cases together, they complement SAST)
RASP & WAF = Can I Protect Myself (Fixing the code is the primary option)
Both SAST and DAST are complementary to each other. The best approach is to include both SAST and DAST.
SAST: Inspects underlying source code, requires understanding of source design, Is utilized early in the development cycle and the average cost to remediate issues is low
DAST: Requires the application running, performs hacker-like (black box) testing,
Utilized much later in the development cycle and the average cost to remediate issues is higher
If we look at OWASP Top 10 2021 changes, SAST or DAST will not cover all of them individually. In addition, we also need SCA to be done to look at open source vulnerabilities.
SAST and DAST are not mutually exclusive and should be used in conjunction with each other. One should be used by the developers to ensure security is being addressed as they are writing the code. The other is used for evaluating existing applications already in production to ensure they are not susceptible to any new vulnerabilities that have been discovered.
The real question is which should have a higher priority when it comes to introducing the concepts into your application security model. Unfortunately, there is no single answer to which comes first. It all depends on your organizations culture, business model, and your relationships with the various impacted groups.
For application security you ideally need SAST, SCA and DAST. You need all three as they essentially measure different things:
SAST identifies bad coding practices that potentially could be exploited
SCA identifies known vulnerabilities in the libraries and components you are using and this is the main attack vector on applications.
DAST identifies some of the weaknesses that SAST and SCA identified, but also identifies weaknesses in the configuration. You might have the perfect application code with zero vulnerabilities, but if it is misconfigured, for instance using a default password, it still can be breached.
If you have to choose, look at SCA and then DATS first as that gives you the best bang for your buck from a risk reduction perspective
It’s a false choice of a question but DAST exist because folks don’t trust their SAST tool. DAST is good about true positives but bad about false negatives. SAST just has a reputation for false positives but a new generation of SAST tools do a much better job.
Both. They are not in competition with each other.
SAST is used for analyzing your written code for practices and patterns that are risky or vulnerable.
DAST is used @ runtime for analyzing the app for vulnerabilities as shown in other ways on the runtime memory stack, etc.
Both provide different value.
Look into RASP vs DAST vs IAST as well.