Statically-Informed Dynamic Analysis Tools to Detect Algorithmic Complexity Vulnerabilities

2016 ◽  
Author(s):  
Benjamin Holland ◽  
Ganesh Ram Santhanam ◽  
Payas Awadhutkar ◽  
Suresh Kothari
Keyword(s):  
Dynamic Analysis ◽  
Algorithmic Complexity ◽  
Analysis Tools

scholarly journals Hypervisor-assisted dynamic malware analysis

Cybersecurity ◽  
2021 ◽  
Vol 4 (1) ◽  
Author(s):  
Roee S. Leon ◽  
Michael Kiperberg ◽  
Anat Anatey Leon Zabag ◽  
Nezer Jacob Zaidenberg
Keyword(s):  
Dynamic Analysis ◽  
Static Analysis ◽  
Cyber Security ◽  
Malware Analysis ◽  
Analysis Tools ◽  
Significant Performance

AbstractMalware analysis is a task of utmost importance in cyber-security. Two approaches exist for malware analysis: static and dynamic. Modern malware uses an abundance of techniques to evade both dynamic and static analysis tools. Current dynamic analysis solutions either make modifications to the running malware or use a higher privilege component that does the actual analysis. The former can be easily detected by sophisticated malware while the latter often induces a significant performance overhead. We propose a method that performs malware analysis within the context of the OS itself. Furthermore, the analysis component is camouflaged by a hypervisor, which makes it completely transparent to the running OS and its applications. The evaluation of the system’s efficiency suggests that the induced performance overhead is negligible.

Evaluation of Dynamic Analysis Tools for Software Security

2018 ◽  
Vol 9 (3) ◽  
pp. 34-59 ◽  
Author(s):  
Michael Lescisin ◽  
Qusay H. Mahmoud
Keyword(s):  
Dynamic Analysis ◽  
Software Security ◽  
Safety Issue ◽  
Memory Safety ◽  
Safety Issues ◽  
Security Issues ◽  
Analysis Tools ◽  
Significant Difference ◽  
Secure Software ◽  
Input Validation

This article discusses the development of secure software by means of dynamic analysis tools. A secure software-based system should have security checks and balances integrated throughout its entire development lifecycle, including its deployment phase. Therefore, this article covers both using software security tools for testing code in development as well as monitoring code in deployment to ensure that it is operating securely. The security issues discussed in this article will be split into two categories – memory safety issues and input validation issues. Memory safety issues concern problems of unauthorized memory access such as buffer overflows, stack overflows, use-after-free, double-free, memory leaks, etc. Although not strictly a memory safety issue, concurrency issues, such as data races, will be considered as memory safety issues in this article. Input validation issues concern problems where untrusted input is directly passed to handlers which are designed to handle both data and commands. Examples of this include path traversal, SQL injection, command injection, JavaScript/HTML injection, etc. As a result of this significant difference between these two types of security vulnerabilities, two sets of tools are evaluated with one set focusing on memory safety issues and the other on input validation issues. This article explores the benefits and limitations of current software dynamic analysis tools by evaluating them against both the authors test cases as well as the OWASP Benchmark for Security Automation and proposes solutions for implementing secure software applications.

scholarly journals Design and implementation of a tracer driver: Easy and efficient dynamic analyses of constraint logic programs

2008 ◽  
Vol 8 (5-6) ◽  
pp. 581-609
Author(s):  
LUDOVIC LANGEVINE ◽  
MIREILLE DUCASSÉ
Keyword(s):  
Dynamic Analysis ◽  
Low Cost ◽  
Logic Programs ◽  
Design And Implementation ◽  
On Demand ◽  
Front End ◽  
Analysis Tools ◽  
Dynamic Analyses ◽  
Constraint Logic Programs ◽  
High Level

AbstractTracers provide users with useful information about program executions. In this article, we propose a “tracer driver”. From a single tracer, it provides a powerful front-end enabling multiple dynamic analysis tools to be easily implemented, while limiting the overhead of the trace generation. The relevant execution events are specified by flexible event patterns and a large variety of trace data can be given either systematically or “on demand”. The proposed tracer driver has been designed in the context of constraint logic programming (CLP); experiments have been made within GNU-Prolog. Execution views provided by existing tools have been easily emulated with a negligible overhead. Experimental measures show that the flexibility and power of the described architecture lead to good performance. The tracer driver overhead is inversely proportional to the average time between two traced events. Whereas the principles of the tracer driver are independent of the traced programming language, it is best suited for high-level languages, such as CLP, where each traced execution event encompasses numerous low-level execution steps. Furthermore, CLP is especially hard to debug. The current environments do not provide all the useful dynamic analysis tools. They can significantly benefit from our tracer driver which enables dynamic analyses to be integrated at a very low cost.

scholarly journals ADVANCED AND RAPID DEVELOPMENT OF DYNAMIC ANALYSIS TOOLS FOR JAVA

2010 ◽  
Vol 10 (1) ◽  
pp. 75-90
Author(s):  
Alex Villazón ◽  
Danilo Ansaloni ◽  
Philippe Moret
Keyword(s):  
Dynamic Analysis ◽  
Rapid Development ◽  
Analysis Tools

scholarly journals DrPin: A dynamic binary instumentator for multiple processor architectures

2020 ◽  
Author(s):  
Luis Fernando Antonioli ◽  
Ricardo Pannain ◽  
Rodolfo Azevedo
Keyword(s):  
Dynamic Analysis ◽  
Static Analysis ◽  
Binary Code ◽  
Binary Analysis ◽  
Linux Kernel ◽  
Processor Architectures ◽  
Backward Compatibility ◽  
Analysis Tools ◽  
Multiple Processor ◽  
Dynamic Binary Analysis

Modern applications rely heavily on dynamically loaded shared libraries, making static analysis tools used to debug and understand applications no longer sufficient. As a consequence, dynamic analysis tools are being adopted and integrated into the development and study of modern applications. Building tools that manipulate and instrument binary code at runtime is difficult and error-prone. Because of that, Dynamic Binary Instrumentation (DBI) frameworks have become increasingly popular. Those frameworks provide means of building dynamic binary analysis tools with low effort. Among them, Pin 2 has been by far the most popular and easy to use one. However, since the release of the Linux Kernel 4 series, it became unsupported, and Pin 3 broke backward compatibility. In this work we focus on studying the challenges faced when building a new DBI (DrPin) that seeks to be compatible with Pin 2 API, without the restrictions of Pin 3, that also runs multiple architectures (x86-64, x86, Arm, Aarch64), and on modern Linux systems.

Finding decision support requirements for effective intelligence analysis tools

2005 ◽  
Author(s):  
William Elm ◽  
Scott Potter ◽  
James Tittle ◽  
David Woods ◽  
Justin Grossman ◽  
...  
Keyword(s):  
Decision Support ◽  
Intelligence Analysis ◽  
Analysis Tools

Improving Production System Performance Using Overall Equipment Effectiveness

2020 ◽  
Vol 6 (1) ◽  
Author(s):  
Lance Clarence ◽  
Wan Muhammad Noor Sarbani Mat Daud
Keyword(s):  
Production System ◽  
System Performance ◽  
Intelligent System ◽  
Global Market ◽  
Equipment Failure ◽  
Intuitive Knowledge ◽  
Analysis Tools ◽  
New Process ◽  
Knowledge Delivery

In the competition among organization on the global market, no organization will tolerate losses. Overall Equipment Effectiveness (OEE) overall is a new process in which the efficiency of a system is calculated and complicated manufacturing issues are truly simplified to simple and intuitive knowledge delivery. It thinks about the exceptionally important measures of productivity. An endeavour has been done to measure and analyse existing Overall Equipment Effectiveness (OEE) at company Kirino in hope to reduce unplanned downtime losses on equipment failure and tooling damage to maximize the productivity. The methods used to analyse these various causes were analysis tools and Intelligence Systems. After knowing the causes of various activities that leads to high rates of defects, then recommendations for improvements that could be used by company Kirino were ready to be made using intelligent system as a medium of solution

Sign in / Sign up

Export Citation Format

Share Document