Skip to content

Commit 5fbe82b

Browse files
committed
small fixes
1 parent 816da7a commit 5fbe82b

File tree

3 files changed

+13
-9
lines changed

3 files changed

+13
-9
lines changed

src/pentesting-cloud/azure-security/README.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The first step is of course to enumerate information about the tenant you are at
2222

2323
Based on the domain name it's possible to know **if the company if using Azure**, get the **tenant ID**, get other **valid domains** in the same tenant (if more) and get **relevant information** like if SSO is enabled, mail configurations, valid user emails...
2424

25-
Check the folloeing page to learn how to perform the **external enumeration**:
25+
Check the following page to learn how to perform the **external enumeration**:
2626

2727
{{#ref}}
2828
az-unauthenticated-enum-and-initial-entry/
@@ -72,7 +72,7 @@ The following tools will be super useful to enumerate both Entra ID tenants and
7272
az-enumeration-tools.md
7373
{{#endref}}
7474

75-
### Bypass Login Conditions
75+
### Bypass Access Policies
7676

7777
<figure><img src="../../images/image (268).png" alt=""><figcaption></figcaption></figure>
7878

@@ -85,7 +85,11 @@ In cases where you have some valid credentials but you cannot login, these are s
8585

8686
After bypassing it, you might be able to get back to your initial setup and you will still have access.
8787

88+
Check:
8889

90+
{{#ref}}
91+
az-privilege-escalation/az-entraid-privesc/az-conditional-access-policies-mfa-bypass.md
92+
{{#endref}}
8993

9094
### Whoami
9195

@@ -145,7 +149,7 @@ Get-AzureADTenantDetail
145149
{{#endtabs }}
146150

147151

148-
### Entra ID Enumeration & Privilege Escalation
152+
### Entra ID Enumeration & Privesc
149153

150154
By default, any user should have **enough permissions to enumerate** things such as users, groups, roles, service principals... (check [default AzureAD permissions](az-basic-information/index.html#default-user-permissions)).\
151155
You can find here a guide:
@@ -161,7 +165,7 @@ az-enumeration-tools.md#automated-post-exploitation-tools
161165
{{#endref}}
162166

163167

164-
### Enumerate Azure Services
168+
### Azure Enumeration
165169

166170
Once you know who you are, you can start enumerating the **Azure services you have access to**.
167171

@@ -196,7 +200,7 @@ In the following section you can find **information about the most common Azure
196200
az-services/
197201
{{#endref}}
198202

199-
### Privilege Escalation, Post-Exploitation & Persistence in Azure Services
203+
### Privilege Escalation, Post-Exploitation & Persistence
200204

201205
Once you know how is the Azure environment structured and what services are being used, you can start looking for ways to **escalate privileges, move laterally, perform other post-exploitation attacks and maintain persistence**.
202206

src/pentesting-cloud/azure-security/az-persistence/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,9 @@
22

33
{{#include ../../../banners/hacktricks-training.md}}
44

5-
### Illicit Consent Grant
5+
### OAuth Application
66

7-
By default, any user can register an application in Azure AD. So you can register an application (only for the target tenant) that needs high impact permissions with admin consent (an approve it if you are the admin) - like sending mail on a user's behalf, role management etc.T his will allow us to **execute phishing attacks** that would be very **fruitful** in case of success.
7+
By default, any user can register an application in Entra ID. So you can register an application (only for the target tenant) that needs high impact permissions with admin consent (an approve it if you are the admin) - like sending mail on a user's behalf, role management etc.T his will allow us to **execute phishing attacks** that would be very **fruitful** in case of success.
88

99
Moreover, you could also accept that application with your user as a way to maintain access over it.
1010

src/pentesting-cloud/azure-security/az-services/az-azuread.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1001,15 +1001,15 @@ When PIM is enabled it's possible to configure each role with certain requiremen
10011001
- Max time to expire the elegible assignments
10021002
- A lot more configuration on when and who to send notifications when certain actions happen with that role
10031003
1004-
### Conditional Access Policies <a href="#title-text" id="title-text"></a>
1004+
### Conditional Access Policies
10051005
10061006
Check:
10071007
10081008
{{#ref}}
10091009
../az-privilege-escalation/az-entraid-privesc/az-conditional-access-policies-mfa-bypass.md
10101010
{{#endref}}
10111011
1012-
### Entra Identity Protection <a href="#title-text" id="title-text"></a>
1012+
### Entra Identity Protection
10131013
10141014
Entra Identity Protection is a security service that allows to **detect when a user or a sign-in is too risky** to be accepted, allowing to **block** the user or the sig-in attempt.
10151015

0 commit comments

Comments
 (0)