Most companies have hundreds of apps so it is impractical to ensure every single app is always meeting your security policies especially when they may have third-party components embedded. Another way to approach this may be to look at zero-trust networking and micro-segmentation. Using low-cost cloud-based micro-segmentation tools you can prevent any new code from running on servers and apps.
Furthermore, keep legacy software and OS operational that may not be receiving security updates anymore. Even if a third-party component gets infected the zero-trust approach will prevent it from launching. Additionally, if a device did get infected with ransomware the micro-segmentation would prevent the ransomware from moving laterally throughout the network - this is an area most networks are not protected -
Summary
Micro-segmentation and zero-trust are recommended by Gartner and Forrester as a key initiative for every enterprise. It will help you secure applications and will add a lot more security, visibility and control to your network.
Search for a product comparison in Application Security Tools
I would check the authentication steps required. How does the data storage work in-app? Encryption and if any ciphering algorithm is used in applications.
Multiple aspects need to be looked at. I'm listing a few critical ones:
1. Hidden passwords and secrets within the application.
2. Check IaaC, Docker, K8 scripts - do they have the right configuration? Wrt Kubernetes and "Hardening Guidance" were released by NSA and CISA (Cybersecurity Technical Report). You need to check if these checks are successful.
3. Validate open-source security vulnerabilities (SCA). This is one area that many projects miss out on and is a very important one to focus on. Read the May 12 release (from US Whitehouse) around this.
4. Do dynamic application security testing using the application URL, in addition to static code check.
Application Security solutions need to work for developers and facilitate their interaction with AppSec including things like training/education. It needs to be fast enough to work on the main CI/CD pipeline and it needs to be trustworthy.
Secure User access solution, (2 factor authentication etc). Ability to provide only the required user access privileges based on user type. Secure communication between user and application and application and database. Encryption of database depending on sensitivity of data.
Applications is not an easy task -- especially when the application is in a constant state of flux to accommodate and adapt to business needs. One of the most important, yet overlooked aspects of application security is to know what you are defending and to understand it properly. It's critical to have an understanding of an application from the outside-in of what technologies it relies on; potential risks associated with it; and organizational impact associated with a security breach in that application.
Properly understanding an application allows you to identify possible weak spots and also helps you narrow down your scope during testing, as well as knowing what vulnerabilities, bad coding practices and patches your organization need to watch out for. It's good to also keep in mind that understanding a target is the first step an attacker takes -- knowing about, and fixing that bug or mis-configuration before an attacker exploits it is the aim of the game.
Furthermore, while aiming to prevent security vulnerabilities is a step in the right direction towards reducing your risk surface, preventive measures alone are not going to provide you with evidence to back-up your efforts. Even the best and brightest security conscious engineers miss a vulnerability or a patch now and then -- it’s part of being human.
You need to back-up your application security efforts with frequent testing. Unfortunately, it’s very difficult to manually pen-test an application at the speed at which new code gets deployed. Moreover, manual testing can get very costly very quickly, and is not salable. Automated security testing helps organizations test for vulnerabilities against an increasingly growing threat surface very quickly and in a scalable manner at a low, predictable costs, meaning that new code can roll off the assembly line faster without compromising your application's security baseline.
So in summary, know what you're trying to secure well, test continuously, and leverage the agility of automated testing to build security into applications as opposed to bolting it on.
The most important aspect to look for in Application Security should be about Data Handling. It should be able to answer the basic questions like where does the data from the application go, who has access to the data and how long does the data need to be accessible for consumption which the Application may or may not expose.
Ingénieur solutions at a comms service provider with 51-200 employees
Real User
2015-12-03T15:43:42Z
Dec 3, 2015
I think that is important to review if the problem of maintenance which were mention before was correct. And we can also see Secure SDLC, the design, the deployment and the maintenance
Hello peers,
I am a Software Engineer at a large tech services company.
I am currently researching network security functions. What aspects of network security are more concerning to small and medium-sized enterprises?
Thank you for your help.
Regional Director at a tech services company with 11-50 employees
Mar 23, 2023
Data breaches, malware, phishing attacks, weak passwords, insider threats, and lack of security policies are some of the most concerning aspects of network security for small and medium-sized enterprises since they may not have the same level of security measures and IT staff as larger corporations.
It's important for SMEs to identify and prioritize these risks and take steps to mitigate them to protect their business and customers' data.This could include implementing strong password policies, providing security awareness training for employees, implementing firewalls and antivirus software, and regularly backing up data. In addition, SMEs should develop formalized security policies and ensure that all employees understand and follow them to maintain a secure network environment.
If we are talking strictly about the network, the issue almost all SMEs suffer from is a lack of risk visibility. Consider the risks and vulnerabilities that exist in the network from ports that are unsecured to firewall rules that are no longer effective to rogue devices that are connected and no one in IT is aware. If SMEs simply closed all of these gaps effectively, they would greatly reduce the chances that they are compromised. The second area is threat visibility - meaning an actual attack unfolding. Once an attacker - say ransomware - bypasses an endpoint, they are free to waltz around the network for weeks. I think that the latest dwell time number is over 4 weeks. Four weeks of recon, command calls, lateral movement, credential compromise, data location, etc. That is enough time to make the ransomware attack really hurt and find all the partner companies that the attacker can move to next. Most large companies have NDR in place to detect and stop attacks - greatly lowering that dwell time and damage - but SMEs cannot afford most of those tools. There are new cloud-based NDR tools that are a lot less (CyGlass), and there are great options with Managed Detection and Response (MDR) companies like Stratejm. Either path, SMEs need to deploy tools or services that watch the network for risks, vulnerabilities, and threats.
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.
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...
Most companies have hundreds of apps so it is impractical to ensure every single app is always meeting your security policies especially when they may have third-party components embedded. Another way to approach this may be to look at zero-trust networking and micro-segmentation. Using low-cost cloud-based micro-segmentation tools you can prevent any new code from running on servers and apps.
Furthermore, keep legacy software and OS operational that may not be receiving security updates anymore. Even if a third-party component gets infected the zero-trust approach will prevent it from launching. Additionally, if a device did get infected with ransomware the micro-segmentation would prevent the ransomware from moving laterally throughout the network - this is an area most networks are not protected -
Summary
Micro-segmentation and zero-trust are recommended by Gartner and Forrester as a key initiative for every enterprise. It will help you secure applications and will add a lot more security, visibility and control to your network.
I would check the authentication steps required. How does the data storage work in-app? Encryption and if any ciphering algorithm is used in applications.
@Nijesh V P Thanks for weighing in!
Multiple aspects need to be looked at. I'm listing a few critical ones:
1. Hidden passwords and secrets within the application.
2. Check IaaC, Docker, K8 scripts - do they have the right configuration? Wrt Kubernetes and "Hardening Guidance" were released by NSA and CISA (Cybersecurity Technical Report). You need to check if these checks are successful.
3. Validate open-source security vulnerabilities (SCA). This is one area that many projects miss out on and is a very important one to focus on. Read the May 12 release (from US Whitehouse) around this.
4. Do dynamic application security testing using the application URL, in addition to static code check.
- Supported Languages
- Integration into CI/CD Pipelines
- Feedback loop to various roles:
like Senior Leadership: Dashboard / High Level Metrics
Developers & Security Professionals : IDE Integration/CICD Plugins/GitHub Actions
- Suggests remediation
- Filter out false positives
- Scan for only certain vulnerability types / signatures
- Scan times vs. Code Scanning coverage
-on-premises solution
-complies with compliant standards like OWASPS,PCI, HIPPA etc
Application Security solutions need to work for developers and facilitate their interaction with AppSec including things like training/education. It needs to be fast enough to work on the main CI/CD pipeline and it needs to be trustworthy.
understand the development lifecycle and embed appropriate controls
Secure User access solution, (2 factor authentication etc). Ability to provide only the required user access privileges based on user type. Secure communication between user and application and application and database. Encryption of database depending on sensitivity of data.
Applications is not an easy task -- especially when the application is in a constant state of flux to accommodate and adapt to business needs. One of the most important, yet overlooked aspects of application security is to know what you are defending and to understand it properly. It's critical to have an understanding of an application from the outside-in of what technologies it relies on; potential risks associated with it; and organizational impact associated with a security breach in that application.
Properly understanding an application allows you to identify possible weak spots and also helps you narrow down your scope during testing, as well as knowing what vulnerabilities, bad coding practices and patches your organization need to watch out for. It's good to also keep in mind that understanding a target is the first step an attacker takes -- knowing about, and fixing that bug or mis-configuration before an attacker exploits it is the aim of the game.
Furthermore, while aiming to prevent security vulnerabilities is a step in the right direction towards reducing your risk surface, preventive measures alone are not going to provide you with evidence to back-up your efforts. Even the best and brightest security conscious engineers miss a vulnerability or a patch now and then -- it’s part of being human.
You need to back-up your application security efforts with frequent testing. Unfortunately, it’s very difficult to manually pen-test an application at the speed at which new code gets deployed. Moreover, manual testing can get very costly very quickly, and is not salable. Automated security testing helps organizations test for vulnerabilities against an increasingly growing threat surface very quickly and in a scalable manner at a low, predictable costs, meaning that new code can roll off the assembly line faster without compromising your application's security baseline.
So in summary, know what you're trying to secure well, test continuously, and leverage the agility of automated testing to build security into applications as opposed to bolting it on.
Simply, I would want to know where my risk is, with real intelligent information with metrics and not noise
Potential for vulnerability, reputation of the app and usage pattern
The most important aspect to look for in Application Security should be about Data Handling. It should be able to answer the basic questions like where does the data from the application go, who has access to the data and how long does the data need to be accessible for consumption which the Application may or may not expose.
I think that is important to review if the problem of maintenance which were mention before was correct. And we can also see Secure SDLC, the design, the deployment and the maintenance
Secure SDLC, start with security Requirements (ASVS) - Design (Threat Modeling) - Devlopment (Coding best practices & SCA) - Testing (VA/PT) - Deployment (configuration, network appliances)
Documentation and technical support if application is retail. If a developing application well defined coding standards along with documentation.
Ability to lock down configuration settings.
Data Exploring and Charting.