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

47. Interview Questions Asked in MNC Interviews

47.9 Source Appendix (URLs actually read)

By Last updated:

He appendix – transparency. Candidate-reported. Themes change. Verify links; pages may move.

Ref Company / scope What we used URL
S1 Wipro (candidate-reported via TechGig article) CIA, encryption, firewall, DDoS, least privilege, zero-day, social engineering, audits/pentest, NIST CSF, honeypot, encryption at rest, IR plan https://content.techgig.com/career-advice/explore-top-12-latest-wipro-interviews-questions-based-on-cybersecurity/articleshow/103643624.cms
S2 Accenture SOC Analyst (candidate-reported; Vinod Kumar LinkedIn post; question list confirmed via search-index excerpt when direct fetch was login-walled) SIEM, TCP/UDP, DoS/DDoS, Kill Chain, OSI/FTP, Event ID 4624, malware, Kerberos/NTLM/Golden/Silver, phishing, SPF/DKIM/DMARC, PTH, ping.exe, external IP, brute force, MITRE, persistence, lateral movement, suspicious command, phishing URL click https://www.linkedin.com/posts/vinod-kumar-183143136_cybersecuritycommunity-soc-accenture-activity-7393987410042417153-YWyT
S3 TCS Smart Hiring (candidate-reported; GeeksforGeeks) Firewalls, networking protocols, social engineering, pentest phases, threat vs vulnerability vs risk; HR hire/location/other-role https://www.geeksforgeeks.org/interview-experiences/tcs-interview-experience-58/
S4 TCS HackQuest Season 9 (candidate-reported; GeeksforGeeks) OWASP Top 10, offensive+defensive scenarios, Burp Suite, Wireshark; managerial/HR mix https://www.geeksforgeeks.org/interview-experiences/tcs-hackquest-season-9-interview-experience/
S5 General (TechGig common questions – no single MNC) SSL, cryptography, firewall, traceroute, VPN, cybersecurity elements https://content.techgig.com/career-advice/common-questions-asked-in-cybersecurity-interviews/articleshow/89977074.cms
S6 General SOC interview guide (SOCSimulator – no single MNC) CIA, ports, SIEM triage, 4625/4624 logic, phishing triage, lateral movement, alert fatigue, prioritisation https://www.socsimulator.com/blog/soc-analyst-interview-questions
S7 Deloitte Cyber Security Analyst (candidate-reported; AmbitionBox – themes from search snippet; full page fetch timed out) SPF/DKIM, ports + UDP example, Active Directory attack awareness, SOC-related themes https://www.ambitionbox.com/interviews/deloitte-interview-questions/cyber-security-analyst

Source honesty

Infosys / Glassdoor pages were not solidly fetched in this research pass – so this chapter does not attribute themes to Infosys. If you find a public experience post, add it to your notebook with the URL before you name the company in an interview story.

Red team (attacker) does Blue team (defender) detects / stops
Spreads fake "official MNC question papers" Uses public candidate reports + concept mastery; no leaked private banks

Ravindra Bagale's Tip

Don't copy-paste appendix URLs in the interview. Understand the concepts. If the interviewer quizzes you on sources: "public candidate report, themes change, I prepare principles." Honest. Remember this.

Lab

Open each URL in the table on your home browser (when online). Tick themes you can explain without notes. Cross out any page that 404s and replace with a new public source in your personal notebook.

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.