Shadowing Practice: Zero Trust Explained in 5 Minutes - Learn English Speaking with Video
בחר מצב תרגול
כל מצב פותח חדר תרגול במסך מלא.
102 משפטים
אם המשפטים קצרים או ארוכים מדי, לחץ על ערוך כדי להתאים אותם.
1
Think about what happens when you connect to your company's network, at the office, or over the VPN.
2
Suddenly, everything just.. opens.
3
The internal wiki loads, the file share mounts, the internal tools answer.
4
Nobody asks who you are again.
5
You're inside, so you're trusted.
6
Here's the problem.
7
Attackers are counting on exactly that.
8
One phished laptop, one leaked password.
9
And they're inside too, inheriting all of that automatic trust.
10
That's how most of the breaches in the news actually spread.
11
Nothing gets hacked.
12
Somebody gets trusted.
13
Today, we're building the architecture that ends that deal.
14
A zero-trust internal API on AWS.
15
The rule is simple and brutal.
16
Nobody is trusted to be inside the network.
17
Not our servers, not our own machines.
18
Every request has to cryptographically prove who sent it, or it hits a locked door.
19
By the end, we'll fire two requests from the same machine, on the same network, at the same URL.
20
One walks away with the secret data, the other gets stopped cold.
21
And the only difference between them is proof of identity.
22
And every piece comes with a free, hands-on lab, so you can build the whole thing yourself.
23
Let's get into it.
24
There are two sides to this build.
25
Something worth protecting, and something that has to prove itself to reach it.
26
Protected side first, starting with the thing an attacker would actually want.
27
That's a DynamoDB table holding our internal inventory.
28
Inside it, we'll plant one item.
29
A gadget whose status says exactly what's at stake.
30
Top secret.
31
DynamoDB encrypts this at rest, so even if someone got hold of the physical storage underneath, the bytes are useless to them.
32
First Zero Trust principle.
33
Before we've built any API at all, protect the data itself, not just the road to it.
34
Now, something has to read that table.
35
We'll add a Lambda function.
36
And here's where Zero Trust gets concrete.
37
The IAM role we give this function is read only on DynamoDB.
38
It can fetch inventory.
39
It is physically incapable of changing or deleting it.
40
If an attacker ever hijacked this code, the blast radius is already capped.
41
That's least privilege.
42
Every piece gets the minimum it needs, nothing more.
43
The Lambda needs a front door, so we put API Gateway in front of it, a REST API with one route, a GET for the inventory.
44
And then we flip the most important switch in this entire build.
45
On that method, authorization changes from none to AWS IAM.
46
From this moment, every request must arrive carrying a cryptographic signature generated from real AWS credentials.
47
No signature?
48
The gateway answers with with a 403, and our Lambda never even wakes up.
49
Anonymous traffic doesn't get to talk to our code at all.
50
That's the protected side.
51
Now, the other half of the handshake, the side that has to prove itself.
52
Our internal client needs somewhere to live, so we create a network for it.
53
A VPC with a public subnet, an internet gateway, and a route out.
54
And here's the twist.
55
In the old model, this network would be the security.
56
Anything inside it, trusted.
57
In ours, the VPC gives us isolation and control over traffic.
58
And that's all.
59
Being inside it earns a machine exactly nothing.
60
Into that subnet we launch the client.
61
A small EC2 instance.
62
Notice what we don't give it.
63
No SSH key pair at all.
64
When we need a shell, we'll connect through Instance Connect.
65
No keys to leak, no passwords to steal.
66
What it does get is the only thing that matters here.
67
An identity.
68
We attach an IAM role with exactly one permission.
69
Invoke API Gateway.
70
This machine can't read the table directly, can't touch the lambda.
71
All it can do is knock on the front door and prove who it is.
72
And now, the two requests we promised at the start.
73
We open a session on the client and run a short Python script.
74
It picks up the role's temporary credentials, issued to the instance automatically, nothing hard-coded, and signs the request with Signature version 4, AWS's signing protocol.
75
The signed GET goes to the inventory endpoint.
76
The gateway checks the signature, confirms this identity is allowed in, and lets it through.
77
Back comes a 200, zero trust verified, one item found, our top secret gadget.
78
Now send the same request without the signature, and it dies at the gateway with a 403.
79
same machine, same network, same URL.
80
The only difference is proof of who's asking.
81
That's zero trust, working.
82
So that's the build.
83
An inventory table holding the secrets, encrypted at rest.
84
A back-end Lambda reading them through a role that can look but never touch.
85
API Gateway demanding a signed identity on every call.
86
A VPC that provides isolation but hands out zero trust.
87
And a client that reaches the data not because of where it sits, but because of who it can prove it is.
88
Two roles, two halves, one handshake, and nobody got trusted for free.
89
Reading about zero trust is one thing.
90
Watching your own 403 turn into a 200 just because you attached the right identity is the moment it actually clicks.
91
We've broken this into six short, free, hands-on labs.
92
One each for VPC, DynamoDB, IAM, Lambda, API Gateway, and EC2.
93
Then the capstone walks you through the full build.
94
Stand up the network, plant the secret, lock the gateway, launch the client, sign the request, and watch Zero Trust Verified come back in your own terminal.
95
Links are in the description.
96
You just watched a request get through a locked down API with no password and no API key.
97
Nothing but a proven identity.
98
That's the architecture real companies are moving to right now, and it's what we build on this channel.
99
Real AWS systems, piece by piece, each with free labs to try yourself.
100
If that's the engineering you want more of, subscribe.
101
And if there's an architecture you'd like us to break down next, tell us in the comments.
102
See you in the lab.
הורד אפליקציה
כל מה שאתה צריך כדי לדבר בשטף
הגיית AIציון לכל משפט
תרגול IPAשלוט בכל צליל
אוצר מיליםבנה את מאגר המילים שלך
משחק אוצר מיליםלמד תוך כדי משחק
אותו ערוץ
FOR YOU
המלץ על סרטון
C11
40 משפטים
Zero Trust Explained in 4 mins
Business EnglishUniversity StudentsWorking Adults
C19
47 משפטים
The most interesting "hack" in history...
American AccentBusiness EnglishUniversity StudentsWorking Adults
C16
58 משפטים
You Hired Them for a Reason. So, Earn Their Trust.
Business EnglishUniversity StudentsWorking Adults
C130
26 משפטים
Docker in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
C13
29 משפטים
How Bitcoin Works in 5 Minutes (Technical)
Business EnglishUniversity StudentsWorking Adults
C12
59 משפטים
Course Preview | AZ-104 | Azure Administrator Associate
Business EnglishUniversity StudentsWorking Adults
B23
314 משפטים
Zero to One - Book Summary
Business EnglishUniversity StudentsWorking Adults
C11
143 משפטים
MCP vs API: The protocol every developer needs to know
Business EnglishUniversity StudentsWorking Adults
B21
190 משפטים
This 25-Year-Old Built a 2-Year Moat Nobody Can Bet Against | Corgi, Nico Laqua & Emily Yuan
Business EnglishUniversity StudentsWorking Adults
C12
130 משפטים
Password Storage Tier List: encryption, hashing, salting, bcrypt, and beyond
Business EnglishUniversity StudentsWorking Adults
C12
187 משפטים
Watch this before you boot up another device
Business EnglishUniversity StudentsWorking Adults
Vocabulary and speaking notes for this lesson
This video has 102 sentences and 1010 words to shadow. The speech runs for 5:55. The speaker talks at a natural 171 words per minute, close to everyday conversation. Only 80% of the words are among the 3,000 most common in English, so the vocabulary is demanding.
Key vocabulary in this video
15 less common words from the video, with pronunciation and meaning:
- gateway /ˈɡeɪtˌweɪ/ (noun) — A passage that can be closed by use of a gate.
- signature /ˈsɪɡ.nə.t͡ʃə/ (noun) — A person's name, written by that person, used as identification or to signify approval of accompanying material, such as a legal contract.
- inventory /ˈɪn.vən.tɹi/ (noun) — The stock of an item on hand at a particular location or business.
- architecture /ˈɑː.kɪˌtɛk.t͡ʃə/ (noun) — The art and science of designing and managing the construction of buildings and other structures, particularly if they are well proportioned and decorated.
- connect /kəˈnɛkt/ (verb) — To join (to another object): to attach, or to be intended to attach or capable of attaching, to another object.
- password /ˈpæs.wɜɹd/ (noun) — A word relayed to a person to gain admittance to a place or to gain access to information.
- attacker /əˈtækɚ/ (noun) — Someone who attacks.
- lab /læːb/ (noun) — A Labrador retriever.
- leak /liːk/ (noun) — A crack, crevice, fissure, or hole which admits water or other fluid, or lets it escape.
- isolation /ˌaɪsəˈleɪʃən/ (noun) — The state of being isolated, detached, or separated; the state of being away from other people.
- verify /ˈvɛɹɪfaɪ/ (verb) — To substantiate or prove the truth of something.
- attach /əˈtæt͡ʃ/ (verb) — To fasten, to join to (literally and figuratively).
- earn /ɝn/ (verb) — To gain (success, reward, recognition) through applied effort or work.
- temporary /ˈtɛmp(əˌɹ)ɛɹi/ (adjective) — Not permanent; existing only for a period or periods of time.
- mount /maʊnt/ (verb) — To get upon; to ascend; to climb.
Phrasal verbs you will hear
- break down (verb) — To stop functioning.
- build on /bɪldɑn/ (verb) — To add additional elements or components to (a framework, a concept, a device, etc.) in order to extend it.
- come with (verb) — To join and come along.
- count on /kaʊnʌn/ (verb) — To rely on, trust, or expect.
- get into (verb) — To move into (an object), such that one ends up inside it.
- get through /ɡɛt ˈθɹu/ (verb) — To overcome; to endure.
- hand out (verb) — To distribute; to give out, either by hand or as if so (figuratively).
- knock on (verb) — To commit a foul by knocking the ball forward.
Pronunciation to watch
The speaker uses 15 contractions and reduced forms, such as we'll, can't, we've. Say them the short way, as you hear them.
- The “th” sounds: underneath /ˌʌndɚˈniθ/, authorization /ˌɔːθəɹaɪˈzeɪʃən/
- The “sh” and “zh” sounds: isolation /ˌaɪsəˈleɪʃən/, shell /ʃɛl/, authorization /ˌɔːθəɹaɪˈzeɪʃən/, credential /kɹɪˈdɛnʃəl/, handshake /ˈhæn(d)ˌʃeɪk/
- Long words — get the stress right: architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, isolation /ˌaɪsəˈleɪʃən/, temporary /ˈtɛmp(əˌɹ)ɛɹi/, automatic /ˌɔː.təˈmæt.ɪk/, anonymous /əˈnɒn.ə.məs/
How to practise with this video
- Listen to the whole video once without speaking and note the words you do not know.
- Start at 0.75× speed, shadow it sentence by sentence, then go back to normal speed once it feels easy.
- Record yourself and compare with the original, paying attention to words like gateway, signature, inventory.
דקדוק בסרטון הזה
המבנים שהדובר משתמש בהם הכי הרבה, עם המילים המדויקות מהסרטון:
| מבנה | בסרטון |
|---|---|
| סביל (Passive voice) be + past participle — הדגש הוא על מה שקורה, לא על מי שעושה את הפעולה | is trusted · is read · is already capped |
| הווה מושלם (Present perfect) have/has + past participle — פעולה שקרתה בעבר ועדיין יש לה חשיבות או השפעה עכשיו | we've built · We've broken |
מהי טכניקת השאדואינג?
שאדואינג היא טכניקת למידת שפה מבוססת מדע שפותחה במקור להכשרת מתורגמנים מקצועיים ופופולרית על ידי הפוליגלוט ד"ר אלכסנדר ארגואלס. השיטה פשוטה אך עוצמתית: אתה מקשיב לאודיו באנגלית ילידית וחוזר עליו בקול רם מיד — כמו צל העוקב אחרי הדובר עם עיכוב של 1–2 שניות בלבד. בניגוד להאזנה פסיבית או תרגילי דקדוק, שאדואינג מכריח את המוח והשרירים בפה לעבד ולשחזר דפוסי דיבור אמיתיים בו זמנית. מחקרים מראים שזה משפר משמעותית את דיוק ההגייה, האינטונציה, הקצב, הדיבור המחובר, הבנת השמיעה ושטף הדיבור — מה שהופך אותו לאחת השיטות היעילות ביותר להכנה לIELTS Speaking ולתקשורת באנגלית בעולם האמיתי.