Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
What Do You Mean My Security Tools Dont Work on APIs?!!
Newest First  |  Oldest First  |  Threaded View
svarughese
50%
50%
svarughese,
User Rank: Apprentice
7/24/2020 | 11:48:58 AM
Re: More apt means of analyzing weakness
There are many tools that allow for test for API from a dynamic perspective here is a video that walks you through it with AppScan: https://www.youtube.com/watch?v=8IUg_Nz-TsQ&t=6s
planetlevel
50%
50%
planetlevel,
User Rank: Author
7/7/2015 | 2:15:02 PM
Re: More apt means of analyzing weakness
Please read my response to @jgilliam
planetlevel
50%
50%
planetlevel,
User Rank: Author
7/7/2015 | 2:14:25 PM
Re: More apt means of analyzing weakness
Great question, and an important topic.

I think we can agree that the goal is to find all the security vulnerabilities in an application as early in the process and with the minimal amount of effort and expertise required.

Ordinarily, then only way to tell whether a security vulnerability is really present is to exploit it.  That means that you need experts, have to craft exploits, etc...  Actually, static analysis doesn't require exploit, but it generates so many false positives, that you end up having to verify all the findings with an exploit anyway.

But the vast majority vulnerabilities *can* be observed without exploit, if you've instrumented the application so that you can see all the security relevant activity.  For example, if you walk into your house and nothing forces you to unlock a door... then you know an attacker could do the same.

In a web service, instrumentation can watch the data come from a JSON request, flow through the application, and reach a SQL query, without being validated, encoded, or parameterized.  Instrumentation has established that the application is vulnerable to SQL injection, and we didn't have to exploit it.

This approach can be used on a very broad range of application security vulnerabilities and is extremely accurate. All you have to do is use the application normally, and the instrumentation can tell you whether anything happened (or failed to happen) that an attacker could exploit.

There are, of course, some parts of the code that aren't normally executed.  For those, you have to send some specially crafted input.  But even those cases don't require exploit, just the right data to make the code execute so that the instrumentation can watch how the code runs.

You can (and should) use instrumentation throughout the lifecycle to gain security insight from the first moment a developer codes and tests locally, to continuous integration, QA testing, and staging.

Gartner calls this approach IAST (Interactive Application Security Testing), and the speed, accuracy, and process advantages over SAST and DAST are dramatic.  Neither SAST or DAST achieves good code coverage, and what's worse is that you'll never know what parts of the code were missed.

 
kbannan100
100%
0%
kbannan100,
User Rank: Moderator
7/2/2015 | 6:32:49 PM
Re: More apt means of analyzing weakness
Sounds like that to me, too! 

--KB

Karen J.Bannan, commenting on behalf of IDG and FireEye. 
jgillam
50%
50%
jgillam,
User Rank: Apprentice
6/29/2015 | 9:44:34 AM
Re: More apt means of analyzing weakness
It almost sounds like you are suggesting that it might be better to just test the security of things (houses, code) through normal use rather than with by attacking it.  Hopefully that wasn't your intention.  Application security testing (like any security testing) must be conducted with both regular and irregular usage, not just one or the other.  

I think you mean to say that in an ideal world we should be catching all the bad stuff during devepment cycles.  And I absolutely agree with that.  It is a failing of many organizations that applications are built and then tested rather than built while being tested.  However the types of tools mentioned in the article (DAST and SAST) should be used for that pre-production testing and particularly DAST tools should definitely be hitting the application or api or whatever with both "normal" traffic as well as attack traffic.  And if something breaks... well it is a good thing it just broke during a test, right?
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
6/26/2015 | 2:43:37 PM
Re: More apt means of analyzing weakness
I agree to an extent. From a functionality standpoint you will most likely run into issues due to cross-app cryptography inconsistency. But if the app is stand alone internally and wasn't web based, this train of thought detracts from the scope of the article, then you could have a strong cryptology that has not been introduced publicly. Potentially making it more secure....if you have high expertise in cryptology of course.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/26/2015 | 9:40:13 AM
Re: Dropwizard API security
Yes, I read that. Interesting. Thank you.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/26/2015 | 9:39:41 AM
Re: More apt means of analyzing weakness
Today's frameworks are design in a way that security kept in mind. The only thing the developers should be doing to follow the guidelines. When they start becoming creative such as creating their own cryptography that is where you end up with problems.
planetlevel
50%
50%
planetlevel,
User Rank: Author
6/25/2015 | 10:26:00 PM
Dropwizard API security
Here's an interesting example of a security flaw in a popular framework used to build APIs.  https://github.com/dropwizard/dropwizard/issues/768

 

 
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
6/25/2015 | 11:44:13 AM
More apt means of analyzing weakness
The last part of this article makes a very good point. Analyzing the application through normal use could yield better results than attacking. You would be able to discover the security pitfalls of your home through normal use and analysis instead of attacking it with mock intruding events. In the end, you could and probably would end up breaking things. Same with app security.


I also think its a good idea to point out that in the coding phase is when app sec should be continually reviewed. Today's agile methodology is very good at acknowledging this principle. If you don't ingrain security at every phase of the SDLC, it is hopeless to expect that post-creation testing will yield desirable results.


Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Zero Trust doesn't have to break your budget!
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31476
PUBLISHED: 2021-06-16
This vulnerability allows remote attackers to execute arbitrary code on affected installations of Foxit PhantomPDF 10.1.3.37598. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the han...
CVE-2021-31477
PUBLISHED: 2021-06-16
This vulnerability allows remote attackers to execute arbitrary code on affected installations of GE Reason RPV311 14A03. Authentication is not required to exploit this vulnerability. The specific flaw exists within the firmware and filesystem of the device. The firmware and filesystem contain hard-...
CVE-2021-32690
PUBLISHED: 2021-06-16
Helm is a tool for managing Charts (packages of pre-configured Kubernetes resources). In versions of helm prior to 3.6.1, a vulnerability exists where the username and password credentials associated with a Helm repository could be passed on to another domain referenced by that Helm repository. This...
CVE-2021-32691
PUBLISHED: 2021-06-16
Apollos Apps is an open source platform for launching church-related apps. In Apollos Apps versions prior to 2.20.0, new user registrations are able to access anyone's account by only knowing their basic profile information (name, birthday, gender, etc). This includes all app functionality within th...
CVE-2021-32243
PUBLISHED: 2021-06-16
FOGProject v1.5.9 is affected by a File Upload RCE (Authenticated).