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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
What Do You Mean My Security Tools Don’t Work on APIs?!!
Newest First  |  Oldest First  |  Threaded View
svarughese
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
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
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
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
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
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
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
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
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
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.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Practical Network Security Approaches for a Multicloud, Hybrid IT World
The report covers areas enterprises should focus on for their multicloud/hybrid cloud security strategy: -increase visibility over the environment -learning cloud-specific skills -relying on established security frameworks -re-architecting the network
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-30333
PUBLISHED: 2022-05-09
RARLAB UnRAR before 6.12 on Linux and UNIX allows directory traversal to write to files during an extract (aka unpack) operation, as demonstrated by creating a ~/.ssh/authorized_keys file. NOTE: WinRAR and Android RAR are unaffected.
CVE-2022-23066
PUBLISHED: 2022-05-09
In Solana rBPF versions 0.2.26 and 0.2.27 are affected by Incorrect Calculation which is caused by improper implementation of sdiv instruction. This can lead to the wrong execution path, resulting in huge loss in specific cases. For example, the result of a sdiv instruction may decide whether to tra...
CVE-2022-28463
PUBLISHED: 2022-05-08
ImageMagick 7.1.0-27 is vulnerable to Buffer Overflow.
CVE-2022-28470
PUBLISHED: 2022-05-08
marcador package in PyPI 0.1 through 0.13 included a code-execution backdoor.
CVE-2022-1620
PUBLISHED: 2022-05-08
NULL Pointer Dereference in function vim_regexec_string at regexp.c:2729 in GitHub repository vim/vim prior to 8.2.4901. NULL Pointer Dereference in function vim_regexec_string at regexp.c:2729 allows attackers to cause a denial of service (application crash) via a crafted input.