OWASP Zed Attack Proxy - Revision history

HVergara: /* Features */

2024-01-07T04:16:25Z

Features

← Older revision		Revision as of 04:16, 7 January 2024
Line 27:		Line 27:
	OWASP ZAP is a comprehensive tool in web application security, equipped with various modules to detect and analyze a wide range of vulnerabilities. With features like multiple attack modes and structured scanning, it plays a crucial role in identifying and mitigating potential threats in web applications.		OWASP ZAP is a comprehensive tool in web application security, equipped with various modules to detect and analyze a wide range of vulnerabilities. With features like multiple attack modes and structured scanning, it plays a crucial role in identifying and mitigating potential threats in web applications.

	Security Scanner for Web Applications:		'''Security Scanner for Web Applications:'''
	OWASP ZAP is utilized as a security scanner specifically designed for web applications.		OWASP ZAP is utilized as a security scanner specifically designed for web applications.
	Various Modules:<ref name="ZAPPROXY. Features."/>		Various Modules:<ref name="ZAPPROXY. Features."/>

	It is equipped with various modules including:		'''It is equipped with various modules including:'''
	* '''Proxy:''' For capturing data		* '''Proxy:''' For capturing data
	* '''Fuzzer:''' For identifying vulnerabilities		* '''Fuzzer:''' For identifying vulnerabilities
Line 38:		Line 38:
	* '''Dictionary Method:''' To access files		* '''Dictionary Method:''' To access files

	Vulnerability Detection:		'''Vulnerability Detection:'''
	OWASP ZAP is capable of detecting medium and low-level risks and vulnerabilities such as<ref name="OWASP. Attacks."/>:		OWASP ZAP is capable of detecting medium and low-level risks and vulnerabilities such as<ref name="OWASP. Attacks."/>:
	* '''URL rewriting'''		* '''URL rewriting'''

HVergara: /* Resolution and Re-Testing: */

2024-01-07T04:14:22Z

Resolution and Re-Testing:

← Older revision		Revision as of 04:14, 7 January 2024
Line 129:		Line 129:
	In this step, we propose various methods to eliminate the identified vulnerability. When focusing on our specific example, it is important to consider two key configurations that need to be addressed:		In this step, we propose various methods to eliminate the identified vulnerability. When focusing on our specific example, it is important to consider two key configurations that need to be addressed:

	*'''Encrypted Connection (HTTPS):''' To set up an encrypted connection, it is necessary		*'''Encrypted Connection (HTTPS):''' To set up an encrypted connection, it is necessary to create an SSL/TLS certificate with a FQDN (Fully Qualified Domain Name) for the web application. This ensures that data transmission is secure and the server only responds to encrypted requests directed to this specific domain name.
	to create an SSL/TLS certificate with a FQDN (Fully Qualified Domain Name)
	for the web application. This ensures that data transmission is secure and the server
	only responds to encrypted requests directed to this specific domain name.

	[[File:Resolution_and_re-testing_-_HTTPS_A.jpg\|600px]]		[[File:Resolution_and_re-testing_-_HTTPS_A.jpg\|600px]]
Line 138:		Line 135:
	Figure 8: Automated scan with encrypted connection		Figure 8: Automated scan with encrypted connection

	*'''Web Application IP:''' It is also important to ensure that the web application does		*'''Web Application IP:''' It is also important to ensure that the web application does not respond to HTTP requests directed specifically to its IP address. This serves as an additional security measure by preventing the application from being accessible via unencrypted HTTP connections.
	not respond to HTTP requests directed specifically to its IP address. This serves as
	an additional security measure by preventing the application from being accessible via		[[File:Resolution_and_re-testing_-_Web_Applucation_IP_A.jpg\|400px]]
	unencrypted HTTP connections.
			Figure 9: Modify a Linux File to Prevent HTTP Responses to a Specific IP Address

	[[File:Resolution_and_re-testing_-_Web_Applucation_IP_C.jpg\|800px]]		[[File:Resolution_and_re-testing_-_Web_Applucation_IP_C.jpg\|800px]]

	Figure 9: Results of Automated Scan After Encrypted Connection		Figure 10: Results of Automated Scan After Encrypted Connection

	==Conclusion==		==Conclusion==

HVergara: /* Execution */

2024-01-07T04:12:11Z

Execution

← Older revision		Revision as of 04:12, 7 January 2024
Line 137:		Line 137:

	Figure 8: Automated scan with encrypted connection		Figure 8: Automated scan with encrypted connection

			*'''Web Application IP:''' It is also important to ensure that the web application does
			not respond to HTTP requests directed specifically to its IP address. This serves as
			an additional security measure by preventing the application from being accessible via
			unencrypted HTTP connections.

	[[File:Resolution_and_re-testing_-_Web_Applucation_IP_C.jpg\|800px]]		[[File:Resolution_and_re-testing_-_Web_Applucation_IP_C.jpg\|800px]]

HVergara: /* Execution */

2024-01-07T04:10:57Z

Execution

← Older revision		Revision as of 04:10, 7 January 2024
Line 129:		Line 129:
	In this step, we propose various methods to eliminate the identified vulnerability. When focusing on our specific example, it is important to consider two key configurations that need to be addressed:		In this step, we propose various methods to eliminate the identified vulnerability. When focusing on our specific example, it is important to consider two key configurations that need to be addressed:

	'''Encrypted Connection (HTTPS):''' To set up an encrypted connection, it is necessary		*'''Encrypted Connection (HTTPS):''' To set up an encrypted connection, it is necessary
	to create an SSL/TLS certificate with a FQDN (Fully Qualified Domain Name)		to create an SSL/TLS certificate with a FQDN (Fully Qualified Domain Name)
	for the web application. This ensures that data transmission is secure and the server		for the web application. This ensures that data transmission is secure and the server

HVergara: /* Execution */

2024-01-07T04:09:59Z

Execution

← Older revision		Revision as of 04:09, 7 January 2024
Line 128:		Line 128:
	===Resolution and Re-Testing:===		===Resolution and Re-Testing:===
	In this step, we propose various methods to eliminate the identified vulnerability. When focusing on our specific example, it is important to consider two key configurations that need to be addressed:		In this step, we propose various methods to eliminate the identified vulnerability. When focusing on our specific example, it is important to consider two key configurations that need to be addressed:

			'''Encrypted Connection (HTTPS):''' To set up an encrypted connection, it is necessary
			to create an SSL/TLS certificate with a FQDN (Fully Qualified Domain Name)
			for the web application. This ensures that data transmission is secure and the server
			only responds to encrypted requests directed to this specific domain name.

	[[File:Resolution_and_re-testing_-_HTTPS_A.jpg\|600px]]		[[File:Resolution_and_re-testing_-_HTTPS_A.jpg\|600px]]

HVergara: /* Execution */

2024-01-07T04:06:26Z

Execution

← Older revision		Revision as of 04:06, 7 January 2024
Line 110:		Line 110:
	In this step, we investigate what information can be accessed after an attack, especially when unencrypted packets have been transmitted.		In this step, we investigate what information can be accessed after an attack, especially when unencrypted packets have been transmitted.

	[[File:Post_Explotation_-_A.jpg\|~~400px~~]]		[[File:Post_Explotation_-_A.jpg\|600px]]

	Figure 5: Wireshark Packet Analysis for Login Password		Figure 5: Wireshark Packet Analysis for Login Password

Line 121:		Line 122:
	Figure 6: Vulnerability Report in OWASP ZAP		Figure 6: Vulnerability Report in OWASP ZAP

	[[File:Reporting_-_C.jpg\|~~400px~~]]		[[File:Reporting_-_C.jpg\|600px]]

	Figure 7: OWASP ZAP Report		Figure 7: OWASP ZAP Report
Line 128:		Line 129:
	In this step, we propose various methods to eliminate the identified vulnerability. When focusing on our specific example, it is important to consider two key configurations that need to be addressed:		In this step, we propose various methods to eliminate the identified vulnerability. When focusing on our specific example, it is important to consider two key configurations that need to be addressed:

	[[File:Resolution_and_re-testing_-_HTTPS_A.jpg\|~~400px~~]]		[[File:Resolution_and_re-testing_-_HTTPS_A.jpg\|600px]]

	Figure 8: Automated scan with encrypted connection		Figure 8: Automated scan with encrypted connection

	[[File:Resolution_and_re-testing_-_Web_Applucation_IP_C.jpg\|~~400px~~]]		[[File:Resolution_and_re-testing_-_Web_Applucation_IP_C.jpg\|800px]]

	Figure 9: Results of Automated Scan After Encrypted Connection		Figure 9: Results of Automated Scan After Encrypted Connection

HVergara at 04:04, 7 January 2024

2024-01-07T04:04:15Z

← Older revision		Revision as of 04:04, 7 January 2024
Line 2:		Line 2:

	OWASP Zed Attack Proxy (ZAP)<ref name="getting-started"/> is a comprehensive, open-source penetration		OWASP Zed Attack Proxy (ZAP)<ref name="getting-started"/> is a comprehensive, open-source penetration
	testing tool developed by The Software Security Project (SSP)~~[3]~~ under		testing tool developed by The Software Security Project (SSP)<ref name="Software Security"/> under
	OWASP. Specifically designed for assessing web application security, it functions as		OWASP. Specifically designed for assessing web application security, it functions as
	a “Manipulator-in-the-middle proxy~~[4]~~, intercepting and modifying messages		a “Manipulator-in-the-middle proxy<ref name="Manipulator-in-the-middle proxy"/>, intercepting and modifying messages
	between the tester’s browser and the application.		between the tester’s browser and the application.
	ZAP is versatile and user-friendly, catering to both security novices and specialists.		ZAP is versatile and user-friendly, catering to both security novices and specialists.
Line 29:		Line 29:
	Security Scanner for Web Applications:		Security Scanner for Web Applications:
	OWASP ZAP is utilized as a security scanner specifically designed for web applications.		OWASP ZAP is utilized as a security scanner specifically designed for web applications.
	Various Modules:~~[5]~~		Various Modules:<ref name="ZAPPROXY. Features."/>

	It is equipped with various modules including:		It is equipped with various modules including:
Line 39:		Line 39:

	Vulnerability Detection:		Vulnerability Detection:
	OWASP ZAP is capable of detecting medium and low-level risks and vulnerabilities such as~~[6]~~:		OWASP ZAP is capable of detecting medium and low-level risks and vulnerabilities such as<ref name="OWASP. Attacks."/>:
	* '''URL rewriting'''		* '''URL rewriting'''
	* '''Application error disclosure'''		* '''Application error disclosure'''
Line 59:		Line 59:

	==Methodology==		==Methodology==
	There are various ways to analyze risks in OWASP. This is based on standard methods and is tailored to personalized security applications~~[7]~~.		There are various ways to analyze risks in OWASP. This is based on standard methods and is tailored to personalized security applications<ref name="Penetration testing methodologies"/>.
	* '''Step 1: Pre-engagement Interactions:''' This phase involves establishing clear goals, scope, and legal boundaries for the security assessment or penetration test, often through contractual agreements.		* '''Step 1: Pre-engagement Interactions:''' This phase involves establishing clear goals, scope, and legal boundaries for the security assessment or penetration test, often through contractual agreements.
	* '''Step 2: Intelligence Gathering:''' The focus here is on collecting as much information as possible about the target system or organization, which could include public data or internal details.		* '''Step 2: Intelligence Gathering:''' The focus here is on collecting as much information as possible about the target system or organization, which could include public data or internal details.

HVergara at 04:02, 7 January 2024

2024-01-07T04:02:58Z

← Older revision		Revision as of 04:02, 7 January 2024
Line 1:		Line 1:
	[[File:OWASP ZAP.png\|thumb\| OWASP ZAP https://www.zaproxy.org/ <ref name="OWASP ZAP"/>]]		[[File:OWASP ZAP.png\|thumb\| OWASP ZAP https://www.zaproxy.org/ <ref name="OWASP ZAP"/>]]

	OWASP Zed Attack Proxy (ZAP)[[<ref name="getting-started"/>]] is a comprehensive, open-source penetration		OWASP Zed Attack Proxy (ZAP)<ref name="getting-started"/> is a comprehensive, open-source penetration
	testing tool developed by The Software Security Project (SSP)[3] under		testing tool developed by The Software Security Project (SSP)[3] under
	OWASP. Specifically designed for assessing web application security, it functions as		OWASP. Specifically designed for assessing web application security, it functions as

HVergara at 04:02, 7 January 2024

2024-01-07T04:02:48Z

← Older revision		Revision as of 04:02, 7 January 2024
Line 1:		Line 1:
	[[File:OWASP ZAP.png\|thumb\| OWASP ZAP https://www.zaproxy.org/ <ref name="OWASP ZAP"/>]]		[[File:OWASP ZAP.png\|thumb\| OWASP ZAP https://www.zaproxy.org/ <ref name="OWASP ZAP"/>]]

	OWASP Zed Attack Proxy (ZAP)[2] is a comprehensive, open-source penetration		OWASP Zed Attack Proxy (ZAP)[[<ref name="getting-started"/>]] is a comprehensive, open-source penetration
	testing tool developed by The Software Security Project (SSP)[3] under		testing tool developed by The Software Security Project (SSP)[3] under
	OWASP. Specifically designed for assessing web application security, it functions as		OWASP. Specifically designed for assessing web application security, it functions as

HVergara: /* References */

2024-01-07T04:02:29Z

References

← Older revision		Revision as of 04:02, 7 January 2024
Line 142:		Line 142:
	<references>		<references>
	<ref name="OWASP ZAP">https://www.zaproxy.org/</ref>		<ref name="OWASP ZAP">https://www.zaproxy.org/</ref>
	<ref name="~~OWASP ZAP~~">OWASP. https://www.zaproxy.org/getting-started/, 2023. access 09.12.2023.</ref>		<ref name="getting-started">OWASP. https://www.zaproxy.org/getting-started/, 2023. access 09.12.2023.</ref>
	<ref name="~~OWASP ZAP~~">Software Security Project. Welcoming zap to the software security project. https://softwaresecurityproject.org/blog/welcoming-zap-to-the-software-security-project/, 2023. access 09.12.2023.</ref>		<ref name="Software Security">Software Security Project. Welcoming zap to the software security project. https://softwaresecurityproject.org/blog/welcoming-zap-to-the-software-security-project/, 2023. access 09.12.2023.</ref>
	<ref name="~~OWASP ZAP~~">OWASP. Manipulator-in-the-middle proxy. https://www.zaproxy.org/docs/desktop/start/features/intercept/, 2023. access 09.12.2023.</ref>		<ref name="Manipulator-in-the-middle proxy">OWASP. Manipulator-in-the-middle proxy. https://www.zaproxy.org/docs/desktop/start/features/intercept/, 2023. access 09.12.2023.</ref>
	<ref name="~~OWASP ZAP~~">ZAPPROXY. Features. https://www.zaproxy.org/docs/desktop/start/features/, ZAPPROXY. access 09.12.2023.</ref>		<ref name="ZAPPROXY. Features.">ZAPPROXY. Features. https://www.zaproxy.org/docs/desktop/start/features/, ZAPPROXY. access 09.12.2023.</ref>
	<ref name="OWASP ~~ZAP~~">OWASP. Attacks. https://owasp.org/www-community/attacks/, 2023. access 09.12.2023.</ref>		<ref name="OWASP. Attacks.">OWASP. Attacks. https://owasp.org/www-community/attacks/, 2023. access 09.12.2023.</ref>
	<ref name="~~OWASP ZAP~~">OWASP. Penetration testing methodologies. https://owasp.org/www-project-web-security-testing-guide/latest/3-The_OWASP_Testing_Framework/1-Penetration_Testing_Methodologies#penetration-testing-execution-standard, 2023. access 09.12.2023.</ref>		<ref name="Penetration testing methodologies">OWASP. Penetration testing methodologies. https://owasp.org/www-project-web-security-testing-guide/latest/3-The_OWASP_Testing_Framework/1-Penetration_Testing_Methodologies#penetration-testing-execution-standard, 2023. access 09.12.2023.</ref>

	</references>		</references>

	[[Category:Pentesting]]		[[Category:Pentesting]]