The document discusses techniques for assessing the security of web applications. It recommends gathering evidence during the assessment and documenting vulnerabilities found, including screenshots and details of issues. Both automated scanning tools and manual testing are suggested. Scanners can find basic issues quickly but results must be verified manually. Manual testing involves techniques like exploring the app in a proxy, parameter fuzzing, authentication testing, and reviewing the server configuration. Thorough planning and methodology are important to conduct a comprehensive assessment.
Drupal is a very popular content management system that has been widely adopted by government agencies, major businesses, social networks, and more. This talk focuses on the penetration tester's perspective of Drupal and dives into streamlining the assessment and remediation of commonly observed application and configuration flaws by way of custom exploit code and security checklists.
Download the associated scripts, movies, and checklist here: https://github.com/gfoss/attacking-drupal
OWASP Top 10 vs Drupal - OWASP Benelux 2012ZIONSECURITY
OWASP Top 10 vs Drupal
Abstract: Drupal is the most used and well-known open source content management system in the world. Created by Dries Buytaert years ago it has grown with the support of a big community. Drupal 7 is already released and there is an entire ecosystem for Drupal and Drupal web agencies.
During this presentation we will discuss the findings of an automated static code analysis of Drupal 6 and Drupal 7 and how Drupal protects against the OWASP Top 10 Application Security Risks. We will explain the security weaknesses that remain when you use Drupal and what you can implement to have a secure cloud server running Drupal.
How to Shot Web - Jason Haddix at DEFCON 23 - See it Live: Details in Descrip...bugcrowd
WATCH JASON'S TALK LIVE, 8/14 @ 11AM PDT - Register Here: http://bgcd.co/DEFCON23-haddix
Jason Haddix explores successful tactics and tools used by himself and the best bug hunters. Practical methodologies, tools and tips that make you better at hacking websites and mobile apps to claim those bounties.
Follow Jason on Twitter: http://twitter.com/jhaddix
Follow Bugcrowd on Twitter: http://twitter.com/bugcrowd
Check out the latest bug bounties on Bugcrowd: https://bugcrowd.com/programs
Drupal is a very popular content management system that has been widely adopted by government agencies, major businesses, social networks, and more. This talk focuses on the penetration tester's perspective of Drupal and dives into streamlining the assessment and remediation of commonly observed application and configuration flaws by way of custom exploit code and security checklists.
Download the associated scripts, movies, and checklist here: https://github.com/gfoss/attacking-drupal
OWASP Top 10 vs Drupal - OWASP Benelux 2012ZIONSECURITY
OWASP Top 10 vs Drupal
Abstract: Drupal is the most used and well-known open source content management system in the world. Created by Dries Buytaert years ago it has grown with the support of a big community. Drupal 7 is already released and there is an entire ecosystem for Drupal and Drupal web agencies.
During this presentation we will discuss the findings of an automated static code analysis of Drupal 6 and Drupal 7 and how Drupal protects against the OWASP Top 10 Application Security Risks. We will explain the security weaknesses that remain when you use Drupal and what you can implement to have a secure cloud server running Drupal.
How to Shot Web - Jason Haddix at DEFCON 23 - See it Live: Details in Descrip...bugcrowd
WATCH JASON'S TALK LIVE, 8/14 @ 11AM PDT - Register Here: http://bgcd.co/DEFCON23-haddix
Jason Haddix explores successful tactics and tools used by himself and the best bug hunters. Practical methodologies, tools and tips that make you better at hacking websites and mobile apps to claim those bounties.
Follow Jason on Twitter: http://twitter.com/jhaddix
Follow Bugcrowd on Twitter: http://twitter.com/bugcrowd
Check out the latest bug bounties on Bugcrowd: https://bugcrowd.com/programs
Slides from presentation: "DevSec Defense: How DevOps Practices Can Drive Detection Development For Defenders"
For more information: http://www.danielbohannon.com/presentations/
Silent web app testing by example - BerlinSides 2011Abraham Aranguren
A practical OWASP Testing Guide walk-through focused on passive and semi passive web app testing techniques
NOTE: Use the "Download" option at the top to see the presentation as a PDF properly
This was presented at the March 16th, 2016 WordPress Meetup in Hamilton and describes WordPress Security and best practices that should be taken to protect any WordPress website against hackers whom target WordPress websites and impact your Google reputation and online presence.
We cannot “firewall” or “patch” our way to secure websites. In the past, security professionals thought firewalls, Secure Sockets Layer (SSL), patching, and privacy policies were enough. Today, however, these methods are outdated and ineffective, as attacks on prominent, well-protected websites are occurring every day. Most every organization in the world have something in common – they have had websites compromised in some way. No company or industry is immune. Programmers need to learn to build websites differently. This talk will review the top coding techniques developers need to master in order to build a low-risk, high-security web application.
Top Ten Proactive Web Security Controls v5Jim Manico
It is not easy to build a secure, low-risk or risk-managed web application. Firewalls, “policy” and other traditional information security measures serve as either an incomplete or useless measure in the pursuit of web application security.
As software developers author the code that makes up a web application, they need to do so in a secure manner. All tiers of a web application, the user interface, the business logic, the controller, the database code and more – all need to be developed with security in mind. This can be a very difficult task and developers are often set up for failure. Most developers did not learn about secure coding or crypto in school. The languages and frameworks that developers use to build web applications are often lacking critical core controls or are insecure by default in some way. There may be inherent flaws in requirements and designs. It is also very rare when organizations provide developers with prescriptive requirements that guide them down the path of secure software. When it comes to web security, developers are often set up to lose the security game.
This document was written by developers for developers, to assist those new to secure development. It aims to guide developers and other software development professionals down the path of secure web application software development.
This document is neither scientific nor complete. In fact it is a bit misguided. There are more than 10 issues that developers need to be aware of. Some of these “top ten” controls will be very specific, others will be general categories. Some of these items are technical, others are process based. Some may argue that this document includes items that are not even controls at all. All of these concerns are fair. Again, this is an awareness document meant for those new to secure software development. It is a start, not an end.
Cross Site Scripting (XSS) Defense with JavaJim Manico
Cross Site Scripting Defense is difficult. The Java Programming language does not provide native key defenses necessary to throughly prevent XSS. As technologies such as Content Security Policy emerge, we still need pragmatic advice to stop XSS in legacy applications as well as new applications using traditional Java frameworks. First generation encoding libraries had both performance and completeness problems that prevent developers from through, production-safe XSS defense. This talk will deeply review the OWASP Java Encoder Project and the OWASP HTML Sanitizer Project and give detailed code samples highlighting their use. Additional advice on next-generation JavaScript and JSON workflows using the OWASP JSON Sanitizer will also be reviewed.
The presentation focus on some known and unknown methods of android pentetration testing. I have taken help from many resources which I have mentioned in PPT.
Slides from presentation: "DevSec Defense: How DevOps Practices Can Drive Detection Development For Defenders"
For more information: http://www.danielbohannon.com/presentations/
Silent web app testing by example - BerlinSides 2011Abraham Aranguren
A practical OWASP Testing Guide walk-through focused on passive and semi passive web app testing techniques
NOTE: Use the "Download" option at the top to see the presentation as a PDF properly
This was presented at the March 16th, 2016 WordPress Meetup in Hamilton and describes WordPress Security and best practices that should be taken to protect any WordPress website against hackers whom target WordPress websites and impact your Google reputation and online presence.
We cannot “firewall” or “patch” our way to secure websites. In the past, security professionals thought firewalls, Secure Sockets Layer (SSL), patching, and privacy policies were enough. Today, however, these methods are outdated and ineffective, as attacks on prominent, well-protected websites are occurring every day. Most every organization in the world have something in common – they have had websites compromised in some way. No company or industry is immune. Programmers need to learn to build websites differently. This talk will review the top coding techniques developers need to master in order to build a low-risk, high-security web application.
Top Ten Proactive Web Security Controls v5Jim Manico
It is not easy to build a secure, low-risk or risk-managed web application. Firewalls, “policy” and other traditional information security measures serve as either an incomplete or useless measure in the pursuit of web application security.
As software developers author the code that makes up a web application, they need to do so in a secure manner. All tiers of a web application, the user interface, the business logic, the controller, the database code and more – all need to be developed with security in mind. This can be a very difficult task and developers are often set up for failure. Most developers did not learn about secure coding or crypto in school. The languages and frameworks that developers use to build web applications are often lacking critical core controls or are insecure by default in some way. There may be inherent flaws in requirements and designs. It is also very rare when organizations provide developers with prescriptive requirements that guide them down the path of secure software. When it comes to web security, developers are often set up to lose the security game.
This document was written by developers for developers, to assist those new to secure development. It aims to guide developers and other software development professionals down the path of secure web application software development.
This document is neither scientific nor complete. In fact it is a bit misguided. There are more than 10 issues that developers need to be aware of. Some of these “top ten” controls will be very specific, others will be general categories. Some of these items are technical, others are process based. Some may argue that this document includes items that are not even controls at all. All of these concerns are fair. Again, this is an awareness document meant for those new to secure software development. It is a start, not an end.
Cross Site Scripting (XSS) Defense with JavaJim Manico
Cross Site Scripting Defense is difficult. The Java Programming language does not provide native key defenses necessary to throughly prevent XSS. As technologies such as Content Security Policy emerge, we still need pragmatic advice to stop XSS in legacy applications as well as new applications using traditional Java frameworks. First generation encoding libraries had both performance and completeness problems that prevent developers from through, production-safe XSS defense. This talk will deeply review the OWASP Java Encoder Project and the OWASP HTML Sanitizer Project and give detailed code samples highlighting their use. Additional advice on next-generation JavaScript and JSON workflows using the OWASP JSON Sanitizer will also be reviewed.
The presentation focus on some known and unknown methods of android pentetration testing. I have taken help from many resources which I have mentioned in PPT.
Web Application Security 101 - 04 Testing MethodologyWebsecurify
In part 4 of Web Application Security 101 we will dive deep into the standard testing methodology used by penetration testers and vulnerability researchers when testing web application for security vulnerabilities.
I'm take picture from here and there by goggling not mentioning all source please let me know if anyone has any objection. This presentation was presented in “securITy” Information Security Conference at BASIS SoftExpo 2012
Web Application Penetration Testing i have completed this online course for www.cybrary.it this is fantastic website for IT Engineer,Network Engineer and Software Engineer....
The ABCs of Source-Assisted Web Application Penetration Testing With OWASP ZA...Denim Group
There are a number of reasons to use source code to assist in web application penetration testing such as making better use of penetration testers’ time, providing penetration testers with deeper insight into system behavior, and highlighting specific sections of so development teams can remediate vulnerabilities faster. Examples of these are provided using the open source ThreadFix plugin for the OWASP ZAP proxy and dynamic application security testing tool. These show opportunities attendees have to enhance their own penetration tests given access to source code.
This presentation covers the “ABCs” of source code assisted web application penetration testing: covering issues of attack surface enumeration, backdoor identification, and configuration issue discovery. Having access to the source lets an attacker enumerate all of the URLs and parameters an application exposes – essentially its attack surface. Knowing these allows pen testers greater application coverage during testing. In addition, access to source code can help to identify potential backdoors that have been intentionally added to the system. Comparing the results of blind spidering to a full attack surface model can identify items of interest such as hidden admin consoles or secret backdoor parameters. Finally, the presentation examines how access to source code can help identify configuration settings that may have an adverse impact on the security of the deployed application.
Introduction to Web Application Penetration TestingAnurag Srivastava
Web Application Pentesting
* Process to check and penetrate the security of a web application or a website
* process involves an active analysis of the application for any weaknesses, technical flaws, or vulnerabilities
* Any security issues that are found will be presented to the system owner, together with an assessment of the impact, a proposal for mitigation or a technical solution.
This is a bug bounty hunter presentation given at Nullcon 2016 by Bugcrowd's Faraz Khan.
Learn more about Bugcrowd here: https://bugcrowd.com/join-the-crowd
Assessing the security posture of a web application is a common project for a penetration tester and a good skill for developers to know. In this talk, We’ll go over the different stages of a web application pen test, from start to finish. We’ll start with tools used during the discovery phase to utilize OSINT sources such as search engines, sub-domain brute-forcing and other methods to help you get a good idea of targets “footprint”, automated scanners and their use, all the way to manual testing and tools used for fuzzing parameters to find potential SQL injection vulnerabilities. We’ll also discuss pro-tips and tricks that we use while conducting a full application penetration assessment. After this talk, you should have a good understanding of what is needed as well as where to start on your journey to hacking web apps.
Ekoparty 2017 - The Bug Hunter's Methodologybugcrowd
Goals of this Presentation:
- Outline and provide an actionable methodology for effectively and efficiently testing for, and finding security vulnerabilities in web applications
- Cover common vulnerability classes/types/categories from a high level
- Provide useful tools and processes that you can take right out into the world to immediately improve your own bug hunting abilities
With IoT being the buzz and all operating systems being integrated with central network and intruder in that can create major devastations than an IT system. For example, if someone can intrude into an electric utility network and operate on "SCADA" and entire network going down can be a bizarre or just assume the control system configured for addressing backup mechanism being turn down can result in blackouts.
Preventing Such havocs is what security framework should look into.
DevOoops (Increase awareness around DevOps infra security)
DevOps is increasingly blending the work of both application and network security professionals. In a quest to move faster, organisations can end up creating security vulnerabilities using the tools and products meant to protect them. What happens when these tools are used insecurely or - even worse - they are just insecure? Technologies discussed will encompass AWS, Puppet, Hudson/Jenkins, Vagrant, Docker and much, much more. Everything from common misconfigurations to remote code execution.
The Hacking Game - Think Like a Hacker Meetup 12072023.pptxlior mazor
Stay safe, grab a drink and join us virtually for our upcoming "The Hacking Game - Think Like a Hacker" meetup to learn how hackers can compromise applications, advanced data protection methods and how to focus on fixing your most critical vulnerabilities.
AD113 Speed Up Your Applications w/ Nginx and PageSpeededm00se
My slide deck from my session, AD113: Speed Up Your Applications with Nginx + PageSpeed, at MWLUG 2015 in Atlanta, GA at the Ritz-Carlton.
For more, see:
- https://edm00se.io/self-promotion/mwlug-ad113-success
- https://github.com/edm00se/AD113-Speed-Up-Your-Apps-with-Nginx-and-PageSpeed
The Dirty Little Secrets They Didn’t Teach You In Pentesting Class Chris Gates
Derbycon 2011
This talk is about methodologies and tools that we use or have coded that make our lives and pentest schedule a little easier, and why we do things the way we do. Of course, there will be a healthy dose of Metasploit in the mix.
Analysis of the quality of libraries in the Packagist universe. Introduction to some tools for assessing package quality. Concepts associated with quality.
First Section:
Continuous Delivery as a software engineering approach.
(This is beneficial for Project Managers, DEVs & QAs.)
1. Projects Case Studies to explain why you should adopt Continuous Delivery.
2. Advantages & Reasons for releasing software more frequently.
3. How to make a Reliable / Production Ready Software.
4. Ingredients of Continues Delivery.
5. Tools/ approaches to choose while using Continues Delivery Methodology.
Second Section:
Technical side of Continuous Delivery.
(This is more beneficial for DEVs/ QAs than Project Managers.)
1. Testing a Software.
2. Measuring Code Quality / Analytic to visualize teams performances.
3. Tools: Code Syntax Checker, Testing Framework, Build Automation, Automated Reporting/ Analytic Dashboard.
4. Continuous Delivery Automation over Cloud using Travis CI - Live demonstration.
Third Section:
1. Sample Projects for audience to adopt right tools for development, testing & deployments.
2. Q&A.
-------------------------------------------------
By Waqar Alamgir http://waqaralamgir.tk
Similar to DEF CON 23 - Hacking Web Apps @brentwdesign (20)
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
The Metaverse and AI: how can decision-makers harness the Metaverse for their...Jen Stirrup
The Metaverse is popularized in science fiction, and now it is becoming closer to being a part of our daily lives through the use of social media and shopping companies. How can businesses survive in a world where Artificial Intelligence is becoming the present as well as the future of technology, and how does the Metaverse fit into business strategy when futurist ideas are developing into reality at accelerated rates? How do we do this when our data isn't up to scratch? How can we move towards success with our data so we are set up for the Metaverse when it arrives?
How can you help your company evolve, adapt, and succeed using Artificial Intelligence and the Metaverse to stay ahead of the competition? What are the potential issues, complications, and benefits that these technologies could bring to us and our organizations? In this session, Jen Stirrup will explain how to start thinking about these technologies as an organisation.
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
SAP Sapphire 2024 - ASUG301 building better apps with SAP Fiori.pdfPeter Spielvogel
Building better applications for business users with SAP Fiori.
• What is SAP Fiori and why it matters to you
• How a better user experience drives measurable business benefits
• How to get started with SAP Fiori today
• How SAP Fiori elements accelerates application development
• How SAP Build Code includes SAP Fiori tools and other generative artificial intelligence capabilities
• How SAP Fiori paves the way for using AI in SAP apps
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Enhancing Performance with Globus and the Science DMZGlobus
ESnet has led the way in helping national facilities—and many other institutions in the research community—configure Science DMZs and troubleshoot network issues to maximize data transfer performance. In this talk we will present a summary of approaches and tips for getting the most out of your network infrastructure using Globus Connect Server.
Secstrike : Reverse Engineering & Pwnable tools for CTF.pptx
DEF CON 23 - Hacking Web Apps @brentwdesign
1. Hacking Web Apps
Brent White
Security Consultant
At Solutionary
Twitter: @brentwdesign
Can you set your password to "password"?
2. Disclosure Statement
The content within this
presentation represents the
opinions and thoughts of the
presenter and in no way
represent the thoughts or
opinions of Solutionary, NTT,
NTT Com Security, or any of
NTT’s subsidiaries.
3. === Kick Off ===
A few things must happen before
the assessment starts:
• Kick-off call
• Rules of engagement doc
– When
– Limits
– Scope
– Point of contacts
4. === Evidence Gathering ===
A report is
expected at the
end of the
assessment.
• The more
evidence you
collect, the
easier this
makes your life.
5. === Evidence Gathering ===
KeepNote is my first choice.
– Available for Linux, Windows and Mac.
– Paste screenshots, Create embedded pages
and folders.
I'll group things based on vulnerability:
– Folder named "Default Server Pages" and
each page will be the host & port.
– Color-code the folder based on risk-rating.
(personal preference)
– Easy exporting of the KeepNote notebook as
.html files & easy copy/paste into your
program of choice while report writing.
– Dradis is another popular choice in Kali.
7. === Evidence Gathering ===
Document:
– HTTP Request and Response for each
vulnerability
– Any unscheduled downtime or issues
– Changes in test data
• Creation of additional accounts,
passwords, or client-provided data
• Intentional or inadvertent modification
of any static data resource
– Log all monetary transactions
• For a refund
10. === Evidence Gathering ===
• Call out the specific issue during the write-up,
so the client can see exactly what was sent.
– If a screenshot, outline the vulnerability.
– If text, highlight the vulnerability.
11. === Evidence Gathering ===
List all known
affected
pages and
Parameters for a
vulnerability.
12. === Evidence Gathering ===
• Have a methodology and
checklist to go by during
each assessment.
– OWASP has a good
methodology and
checklist.
– Helps to keep you
on track
13. === Discovery / OSINT ===
• Search engines, Pastebin,
ShodanHQ, Recon-NG, etc., for
anything related to the
application.
– This is a manual and time-consuming
process, but not one to be ignored!
– Email archives, logins, dev help
forums
– Any leaked credentials, known
previous hacks?
– Sites like urlvoid.com to check for
known active malware/threats for the
domain
14. === Discovery / OSINT ===
I have found DB-type, schemas and
test credentials through old
development help forums that were
STILL valid!
16. === Automated Scanning ===
"Why do you
run automated
tools?
You're
supposed to be
a hacker."
17. === Automated Scanning ===
• HUGE time-saver with
assessments!
– Wide range of tests, quickly
– Finds “low-hanging fruit”
• A vuln scan is
NOT a penetration
assessment!
19. === Automated Scanning ===
• Even though scanners help,
their findings must still be
verified.
• Don’t just rely on the scanner, but
use it in addition to manual
testing.
20. === Automated Scanning ===
• Nessus
– Looks at the host and web app.
Covers everything from SSL/TLS
layer, content discovery, basic
CGI vulns and more.
• IBM App Scan
– More web app focused for things
such as SQL/LDAP injections, CSRF
and XSS, etc...
21. === Automated Scanning ===
• BurpSuite Pro
– Built-in "Active" scanner, content
spider and content discovery brute-
forcer tools.
• Nikto
– Great for finding default pages,
known vulnerable scripts, CGI
testing and more
– Also built in to Nessus, but can add
a great deal of time to the scan
– I prefer to use this separately,
outside of Nessus. It gives me more
control.
22. === Automated Scanning ===
– Identifies known WP vulnerabilities
– Enumerates themes, plug-ins and usernames
– Also other content-management system
scanners out there for Joomla, Drupal and
more.
24. === Automated Scanning ===
• There are many more pre-
installed options in Kali.
– Find them in drop-down menu bar:
Kali Linux > Web Applications > Web
Vulnerability Scanners
• Other scanners available:
– Saint
– Nexpose
25. === Automated Scanning ===
• PRO TIPS:
– You want to verify the settings of
the automated scanner. Don't just
blindly click "scan" after entering
a URL.
– Make sure that you're not using
something that's checking for
Denial-of-Service (DoS) unless
specifically requested by the
client.
– Number of threads/connections at a
time? Don't flood the host.
26. === Automated Scanning ===
• PRO TIPS:
– Add any pages/functions the client
has asked you to avoid. (Password
reset page, sign-up page, "Contact"
form, etc...)
– Might need to specify a "Page not
found" or Error 404 page to help
weed out false-positives for file
discovery.
– Configure the log-in process and
credentials for authenticated scans.
– You must take the time to verify the
results and remove false-positives!!
28. === Manual Testing ===
Automated Scanner results:
– Document the vulnerabilities that
are legitimate. Can you take it
further than the scanner?
• For example, if the scanner suspects
SQL injection, see if you can exploit
that with something like SQLMap.
29. === Manual Testing ===
Explore the application through
a proxy program like BurpSuite
Pro.
– Manually explore the app while the
"Spider" and "Content Discovery"
tools are running.
– OWASP's "DirBuster" is a brute
force tool to find files and
directories.
30. === Manual Testing ===
• Review the server response to
help verify what the server is
running (IIS, Apache)
• Look for parameters to fuzz
– How do they handle characters and
commands outside of the normal
actions?
• Parameters can be directly in
the URL. They are also found in
HTTP POST requests
31. === Manual Testing ===
• Try Cross-site Scripting (XSS)
payloads, Cross-site Request Forgery
(CSRF), SQL/LDAP injection, Local
File Inclusion (LFI) and Remote File
Inclusion (RFI)
– BurpSuite Pro has lists available that
you can load for file discovery, XSS,
SQLi, usernames and more. There are also
several places to download your own
lists, or make your own.
– "Xenotix" by OWASP is a XSS tester.
– Save the POST or GET request and execute
with SQLMap to search for SQL injection
32. === Manual Testing ===
• Is sensitive info being passed
through the URL in a GET request?
– Usernames, Passwords, Session ID, etc...
• Look for valuable comments in the
source code of the HTTP Responses
– I've found internal IPs, database names,
usernames, "hidden" admin URLs, database
calls in JavaScript and more!
– This is certainly a manual process and
is time-consuming. However, a thorough
and consistent review will pay off.
34. === Manual Testing ===
• Authentication - can it by
bypassed or broken?
– Can you access URLs and functions as
an unauthenticated user that you
could while logged in?
– Can you re-use the session token
after logging off? Is there a "log
off" feature?
– Can you have multiple sessions as
the same user at the same time?
– What are the password requirements?
– Can you re-use a previous password?
35. === Manual Testing ===
• Look at the host, not just the
web app
– Identify the web server platform.
Apache, IIS?
• If it's an old/outdated install, look for
exploits
– Is there an admin portal available?
• cPanel, Apache Tomcat Manager, etc...
– Are there test and default
credentials available?
– Search for backup, default and
obsolete files.
– Is directory browsing enabled? What
about directory rights?
36. === Manual Testing ===
• Look at the host, not just the
web app
– Look for dangerous HTTP methods
• ie...PUT, COPY, DELETE, TRACE
– Are they vulnerable to directory
traversal, Shellshock, Heartbleed,
etc...?
– Use Nmap to see what ports/services
are open to the public. Is it just
80 & 443? Or, are their other things
available too? Check them out.
37. === Manual Testing ===
• Look at the host, not just the
web app
– Look at SSL/TLS settings for known
and weak cipher vulnerabilities and
expired or untrusted certificates.
• Use SSLScan in Kali or
"TestSSLServer.jar". Qualys SSL Labs is a
good online resource too but there could
be a potential privacy issue.
– SSL Enforcement - Can you access
HTTPS areas by HTTP?
38. === Manual Testing ===
• Check out the methodology from
OWASP as well as several
checklists that are available
to ensure that you're covering
all aspects.
• Practice in a lab!
• Then....
40. Hacking Web Apps
Brent White
Security Consultant
Twitter: @brentwdesign
www.solutionary.com
Editor's Notes
Before you can start tearing into a web application for a customer, there are a few things that need to happen.
There are rules and goals that need to be established for the assessment that happen during the scoping and kick-off discussions.
Since scoping and contracts make me sleepy, I will omit the details.
The kick-off call is where the rubber starts hitting the road, and exists to bridge the gap between the legal contract and the final report using the Rules of Engagement document, also known as the RoE.
The RoE answers the questions of who, when and what and identifies the boundaries between what is and is not allowed during the actual assessment.
After the contents of this document have been agreed upon, you are good to go on executing the assessment.
At the end of every assessment, a report is expected.
The more evidence you collect and the better it’s organized can really help shorten the time it takes to write the report.
Before I start anything, I set up documents to keep evidence, notes and progress.
DON’T LIMIT TO A CHECKLIST! It’s just a thing to keep you on track.
There are many different areas of a web application that need to be looked at in order to conduct a thorough penetration assessment.