Skip to content

Commit bbe21b4

Browse files
authored
Merge pull request #233062 from TerryLanfear/sec-pen
update
2 parents bd6c0d9 + 4b0e9f7 commit bbe21b4

File tree

1 file changed

+8
-10
lines changed

1 file changed

+8
-10
lines changed

articles/security/fundamentals/pen-testing.md

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -11,40 +11,38 @@ ms.subservice: security-fundamentals
1111
ms.topic: article
1212
ms.tgt_pltfrm: na
1313
ms.workload: na
14-
ms.date: 04/21/2022
14+
ms.date: 03/23/2023
1515
ms.author: terrylan
1616
---
1717

1818
# Penetration testing
1919

20-
One of the benefits of using Azure for application testing and deployment is that you can quickly get environments created. You dont have to worry about requisitioning, acquiring, and racking and stacking your own on-premises hardware.
20+
One of the benefits of using Azure for application testing and deployment is that you can quickly get environments created. You don't have to worry about requisitioning, acquiring, and "racking and stacking" your own on-premises hardware.
2121

22-
Quickly creating environments is great – but you still need to make sure you perform your normal security due diligence. One of the things you likely want to do is penetration test the applications you deploy in Azure.
23-
24-
We don’t perform penetration testing of your application for you, but we do understand that you want and need to perform testing on your own applications. That’s a good thing, because when you enhance the security of your applications you help make the entire Azure ecosystem more secure.
22+
Quickly creating environments is great but you still need to make sure you perform your normal security due diligence. One of the things you likely want to do is penetration test the applications you deploy in Azure.
23+
We don't perform penetration testing of your application for you, but we do understand that you want and need to perform testing on your own applications. That's a good thing, because when you enhance the security of your applications you help make the entire Azure ecosystem more secure.
2524

2625
As of June 15, 2017, Microsoft no longer requires pre-approval to conduct a penetration test against Azure resources. This process is only related to Microsoft Azure, and not applicable to any other Microsoft Cloud Service.
2726

28-
2927
> [!IMPORTANT]
3028
> While notifying Microsoft of pen testing activities is no longer required customers must still comply with the [Microsoft Cloud Unified Penetration Testing Rules of Engagement](https://www.microsoft.com/msrc/pentest-rules-of-engagement).
3129
3230
Standard tests you can perform include:
3331

3432
* Tests on your endpoints to uncover the [Open Web Application Security Project (OWASP) top 10 vulnerabilities](https://owasp.org/www-project-top-ten/)
35-
* [Fuzz testing](https://www.microsoft.com/security/blog/2007/09/20/fuzz-testing-at-microsoft-and-the-triage-process/) of your endpoints
33+
* [Fuzz testing](https://www.microsoft.com/research/blog/a-brief-introduction-to-fuzzing-and-why-its-an-important-tool-for-developers/) of your endpoints
3634
* [Port scanning](https://en.wikipedia.org/wiki/Port_scanner) of your endpoints
3735

38-
One type of pen test that you cant perform is any kind of [Denial of Service (DoS)](https://en.wikipedia.org/wiki/Denial-of-service_attack) attack. This test includes initiating a DoS attack itself, or performing related tests that might determine, demonstrate, or simulate any type of DoS attack.
36+
One type of pen test that you can't perform is any kind of [Denial of Service (DoS)](https://en.wikipedia.org/wiki/Denial-of-service_attack) attack. This test includes initiating a DoS attack itself, or performing related tests that might determine, demonstrate, or simulate any type of DoS attack.
3937

4038
> [!Note]
4139
> You may only simulate attacks using Microsoft approved testing partners:
4240
> - [BreakingPoint Cloud](https://www.ixiacom.com/products/breakingpoint-cloud): A self-service traffic generator where your customers can generate traffic against DDoS Protection-enabled public endpoints for simulations.
4341
> - [Red Button](https://www.red-button.net/): Work with a dedicated team of experts to simulate real-world DDoS attack scenarios in a controlled environment.
44-
>
42+
> - [RedWolf](https://www.redwolfsecurity.com/services/#cloud-ddos) a self-service or guided DDoS testing provider with real-time control.
43+
>
4544
> To learn more about these simulation partners, see [testing with simulation partners](../../ddos-protection/test-through-simulations.md).
4645
47-
4846
## Next steps
4947

5048
* Learn more about the [Penetration Testing Rules of Engagement](https://www.microsoft.com/msrc/pentest-rules-of-engagement?rtc=2).

0 commit comments

Comments
 (0)