Skip to content

Commit 92eb3f1

Browse files
rolling-coderolling-code
authored
Add index.html for Security Awareness Training
1 parent 46b2bb3 commit 92eb3f1

File tree

1 file changed

+102
-0
lines changed

1 file changed

+102
-0
lines changed

‎docs/index.html‎

Lines changed: 102 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,102 @@
1+
2+
<!DOCTYPE html>
3+
<html lang="en">
4+
<head>
5+
<meta charset="UTF-8">
6+
<title>Security Awareness Training – OAuth Simulation</title>
7+
<meta name="viewport" content="width=device-width, initial-scale=1">
8+
<style>
9+
body {
10+
font-family: "Segoe UI", Roboto, Arial, sans-serif;
11+
background: #0F172A;
12+
color: #F9FAFB;
13+
margin: 0;
14+
padding: 0;
15+
}
16+
header {
17+
background: #1E293B;
18+
padding: 20px;
19+
text-align: center;
20+
font-size: 24px;
21+
font-weight: bold;
22+
color: #38BDF8;
23+
}
24+
.container {
25+
max-width: 800px;
26+
margin: 40px auto;
27+
background: #1E293B;
28+
padding: 30px;
29+
border-radius: 12px;
30+
box-shadow: 0 8px 24px rgba(0,0,0,0.4);
31+
}
32+
h1 {
33+
color: #38BDF8;
34+
margin-bottom: 10px;
35+
}
36+
p {
37+
line-height: 1.6;
38+
font-size: 18px;
39+
}
40+
.alert {
41+
background: #F87171;
42+
color: #0F172A;
43+
padding: 12px;
44+
border-radius: 8px;
45+
font-weight: bold;
46+
margin: 20px 0;
47+
}
48+
ul {
49+
margin-top: 10px;
50+
padding-left: 20px;
51+
}
52+
li {
53+
margin-bottom: 8px;
54+
}
55+
footer {
56+
text-align: center;
57+
font-size: 14px;
58+
color: #94A3B8;
59+
margin-top: 40px;
60+
}
61+
.btn {
62+
display: inline-block;
63+
padding: 12px 20px;
64+
background: #38BDF8;
65+
color: #0F172A;
66+
font-weight: bold;
67+
text-decoration: none;
68+
border-radius: 8px;
69+
margin-top: 20px;
70+
}
71+
.btn:hover {
72+
background: #0EA5E9;
73+
}
74+
</style>
75+
</head>
76+
<body>
77+
<header>Security Awareness Training</header>
78+
<div class="container">
79+
<h1>OAuth Consent Simulation Complete</h1>
80+
<div class="alert">⚠️ This was a phishing simulation – no credentials were captured.</div>
81+
<p>
82+
You clicked a link and signed in because the consent screen looked familiar. This exercise demonstrates how attackers exploit <strong>trusted app names</strong> to trick users.
83+
</p>
84+
<h2>What happened?</h2>
85+
<ul>
86+
<li>The sign-in page looked legitimate because it was Microsoft’s real login page.</li>
87+
<li>The app name shown was a well-known service (e.g., Microsoft Teams).</li>
88+
<li>You trusted the app name without checking the <strong>redirect URL</strong> or <strong>permissions requested</strong>.</li>
89+
</ul>
90+
<h2>How to protect yourself:</h2>
91+
<ul>
92+
<li>Always verify the <strong>redirect URI</strong> before granting consent.</li>
93+
<li>Check the <strong>permissions requested</strong> – attackers often ask for more than they need.</li>
94+
<li>If something feels off, stop and report it to IT Security.</li>
95+
</ul>
96+
<a hrefMore About Phishing Risks</a>
97+
</div>
98+
<footer>
99+
© 2025 Security Awareness Program | This was a controlled simulation for training purposes.
100+
</footer>
101+
</body>
102+
</html>

0 commit comments

Comments
 (0)