Ravindra BagaleCourses & study guides मराठी Track your progress

47. Interview Questions Asked in MNC Interviews

By Last updated:

Chala mitrano, Part 13 continue – aata MNC-style interview Q and A for cyber / SOC / cloud security roles. He questions candidate-reported public experiences varun aahet (TechGig, GeeksforGeeks, LinkedIn posts, AmbitionBox snippets). Company naav fakt tevha – jevha aapan public page kharokhar vachli. Nasel tar: Frequently asked across MNC interviews (candidate-reported). Model answers clean professional English. Ti rat naka – OWN lab (Sahyadri / Raja-Rani / host-only 192.168.56.x) che examples swatahchya shabdat sanga. Ethics pehle. Ghabru naka – section ni section practice kara. He khup important aahe!

What you will practise in this chapter

  • How to use candidate-reported MNC sources without inventing company names
  • Networking and protocol themes seen in Wipro / TCS / Accenture-style rounds
  • Linux logs plus Windows Event IDs (4624 / 4625 and friends) for SOC talk
  • SIEM architecture, triage, Cyber Kill Chain, MITRE ATT&CK talking points
  • Identity-attack awareness (Kerberos / PTH) – defensive only, no exploit steps
  • Cloud / AWS security themes MNCs probe
  • OWASP, web tools, SPF / DKIM / DMARC email auth
  • Scenario + HR–technical mix answers
  • Source appendix with URLs actually read
  • Project Build-Hack-Fix for MNC interview stories + real incidents

Lab scope

Interview stories about scanning, SQLi, Kerberos demos, or Kali tools must refer only to systems you own: host-only lab (Kali 192.168.56.10, Metasploitable 192.168.56.20, DVWA/Juice 192.168.56.30–.50), your Free Tier EC2, or your emulator. Never claim you tested a client, cafe, or classmate device. Identity topics (Golden Ticket, Pass-the-Hash) stay defensive talking points – no step-by-step attack recipes. IT Act sections such as 43 and 66 apply without authority (verify current text). Lab = learn. Production = defend.

Concepts in this chapter

  1. 47.1How to Use This Chapter – Sources and Ethics
  2. 47.2Networking and Protocols (MNC rounds)
  3. 47.3Linux, Logs and Windows Event IDs
  4. 47.4SOC Analyst Round – SIEM, Triage, MITRE
  5. 47.5Identity Attacks Awareness (Kerberos / PTH – defensive talking points only)
  6. 47.6Cloud and AWS Security MNC Themes
  7. 47.7OWASP / Web / Email Auth (SPF DKIM DMARC)
  8. 47.8Scenario and HR + Technical Mix
  9. 47.9Source Appendix (URLs actually read)
  10. 47.10Red vs Blue, Project and Real Incidents

The chapter recap is at the end of the last concept page.

Chapter 47: MNC interview questions — practice tasks

Open chapter lessons · Full guided lab: mock interview 10 security basics record (not repeated here)

47.1 STAR story for an incident

MediumIT

Why: MNCs love STAR.

What: Write Situation, Task, Action, Result for a lab or real study incident.

How:

  1. Keep Result measurable (e.g. reduced failed logins).
  2. Max half a page.

Expected output: STAR with numbers.

Hint

Use a lab if you lack work experience.

Answer / how to check
  1. Each letter has one sentence.

47.2 Explain HTTPS to a manager

EasyRetail

Why: Non-technical answers matter.

What: Write a 90-second script with no jargon, or define every term.

How:

  1. Cover padlock, encryption, certificate, why login needs it.

Expected output: Manager-friendly script.

Hint

Avoid asymmetric unless explained.

Answer / how to check
  1. A non-IT friend understands it.

47.3 Live command: show listening ports

EasyBanking

Why: They may hand you a terminal.

What: On your VM, demonstrate and narrate.

How:

  1. ss -tulpn
  2. Point to sshd and any web server.
  3. Say which are expected.

Expected output: Narrated demo under 2 minutes.

Hint

Practise out loud.

Answer / how to check
  1. You named each process.

Extended teaching notes

Why this lesson matters

Use this lesson to strengthen systems you own: understand the risk, practise safely in a lab, then write and apply the fix.

Apply the fix across stacks

Same class of bug, same idea in every language.

Java / Spring Boot

Parameterise queries, encode output, CSRF tokens, limited Actuator, dependency scanning.

ASP.NET Core

EF Core / parameterised SQL, Razor encoding, HTTPS, Data Protection.

Node.js / Express

helmet, parameterised SQL, npm audit, avoid eval and shell concat.

Python / Django / Flask / FastAPI

ORM, autoescape, pip-audit, Bandit; never shell=True with user input.

PHP / Laravel

PDO/Eloquent, Blade escaping, composer audit.

Go / Ruby

database/sql placeholders / ActiveRecord; html/template / ERB escaping; govulncheck / Brakeman.

nginx / Apache / Tomcat

Hide versions, TLS, security headers, least-open ports.

MySQL / PostgreSQL / MongoDB / Redis

Private networks, auth on, least-privilege users, no 0.0.0.0/0.

AWS / Azure / GCP

Roles not long-lived keys, private data stores, cloud audit logs on.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.