🔐 LESSON 19 — Security Testing Basics

 

🔐 LESSON 19 — Security Testing Basics

Topic: Security Testing

Grammar: Future Forms – Will & Be Going To

🎯 Lesson Objectives

By the end of the lesson, you will be able to:

  • talk about basic security testing;

  • discuss software vulnerabilities and user access;

  • describe security issues in English;

  • use will and be going to correctly;

  • explain your testing plans and predictions.

💬 1. Warm-up

Look at the pictures.

Image

Image

Image

Image

Discuss

  1. Why is security important in software development?

  2. Have you ever forgotten a password?

  3. Which applications need the highest level of security?

  4. What happens if users can access information they shouldn't see?

  5. Which is worse:

    • a broken button,

    • a slow website,

    • or a security vulnerability?

  6. Have you ever found a serious bug?

📚 2. Vocabulary




✏️ Vocabulary Practice


Complete the sentences.

💬 3. Speaking

Answer the questions.

  1. What security features do you test most often?

  2. Why is authentication important?

  3. What is the difference between authentication and authorization?

  4. Have you ever tested password recovery?

  5. Which security bug is the most dangerous?

  6. What happens if sensitive data becomes public?

  7. Do you enjoy security testing? Why or why not?

📖 4. Reading

A Small Bug with Big Consequences

On Monday morning, Alex, a QA engineer, started testing the login page of a new banking application.

His task was simple: check whether users could only see their own accounts.

Alex logged in as a regular customer. Everything looked normal.

Then he copied the URL and changed one number.

To his surprise, another customer's profile appeared.

The page displayed the customer's name, email address, account number, and transaction history.

Alex immediately understood that this was a serious security vulnerability.

He repeated the test three more times.

The result was always the same.

He created a detailed bug report and called the development team.


The developers quickly started investigating the problem.

They discovered that the application checked authentication correctly, but it didn't verify user permissions.

Because of this mistake, users could open other customers' accounts simply by changing the URL.

The team fixed the bug on the same day.

The next morning, Alex tested the application again.

This time, everything worked correctly.

Only authorised users had access to their own data.

Alex smiled.

"Sometimes one small bug can create a huge security problem."


📖 Reading Comprehension

Answer the questions.

  1. What was Alex testing?

  2. What did he change?

  3. What information did he see?

  4. Why was the bug dangerous?

  5. What mistake did the developers find?

  6. How was the bug discovered?

  7. When was it fixed?

  8. What lesson did Alex learn?

💭 Discussion

  1. How serious is this bug?

  2. What severity would you give it?

  3. Could this bug appear in a real banking application?

  4. What test cases would you create for this feature?

  5. Who is responsible for preventing security vulnerabilities?

📚 5. Grammar

Future Forms: Will & Be Going To


We use be going to for:

✅ Plans

You have already decided.

Examples:

  • I'm going to test the login page tomorrow.

  • We're going to check user permissions.

  • The developers are going to fix the bug this afternoon.

  • I'm going to create a bug report after the meeting.

✅ Predictions with evidence

Examples:

  • The server is overloaded. It's going to crash.

  • The password is too simple. Someone is going to guess it.

  • The session is almost over. It's going to expire.

We use will for:

✅ Decisions made now

Examples:

Developer:
"I can't reproduce the bug."

QA:
"I'll show you."

Manager:
"We need another test."

QA:
"I'll do it."

✅ Predictions (opinions)

Examples:

  • I think the update will improve security.

  • I don't think users will notice this bug.

  • The new firewall will protect the system better.

✅ Promises / Offers

  • I'll send the report today.

  • I'll help you.

  • We'll investigate the issue.

✏️ Grammar Practice


✍️ Writing

Bug Report (100–120 words)

Write a short report.

Include:

  • Summary

  • Steps to Reproduce

  • Actual Result

  • Expected Result

  • Severity

Use at least:

  • 6 vocabulary words

  • 3 sentences with "going to"

  • 3 sentences with "will"

💡 Useful QA Sentences

EnglishUkrainian
Users don't have permission to edit this page.Користувачі не мають прав редагувати цю сторінку.
The login page doesn't validate the password correctly.Сторінка входу неправильно перевіряє пароль.
Sensitive data is visible to other users.Конфіденційні дані видно іншим користувачам.
I'm going to reproduce this issue again.Я збираюся знову відтворити цю проблему.
I'll create a bug report after the meeting.Я створю звіт про баг після зустрічі.
I think the developers will fix it today.Думаю, розробники виправлять це сьогодні.
We're going to test user permissions next.Далі ми збираємося протестувати права доступу користувачів.
This vulnerability may affect all users.Ця вразливість може вплинути на всіх користувачів.

🏠 Homework

 Future Plans

Write 10 sentences:

  • 5 with going to

  • 5 with will

Use today's vocabulary.

Example:

  • I'm going to test the firewall tomorrow.

  • I think the new authentication system will be more secure.



Коментарі

Дописати коментар

Популярні дописи з цього блогу