47. Interview Questions Asked in MNC Interviews
47.10 Red vs Blue, Project and Real Incidents
Shevtat purple loop + real incidents – MNC interview prep target OWN lab. Chala finish kara!
MNC interview project = weak app tumhi build karta, attack path English madhe explain karta (lab only), mag fix + re-verify. Real incidents = known facts, "reported", no invented numbers.
| Red team (attacker) does | Blue team (defender) detects / stops |
|---|---|
| Explains SQLi/auth path only on OWN interview-prep VM | Prepared statements; SG; HTTPS cookies; SIEM-style log proof; re-verify |
| Name-drops MNC breaches with fake statistics | Uses well-known public facts; says "reported"; focuses on controls |
Ravindra Bagale's Tip
In an MNC interview project, don't dump "50 tools + 3 company names". Three screenshots: weak → proof → fixed. Ethics line first. Source discipline = name a company only if you have evidence. This wins. Remember this.
Ravindra Bagale's Tip – मराठी
MNC interview project मध्ये "50 tools + 3 company names" dump नको. तीन screenshots: weak → proof → fixed. Ethics line आधी. Source discipline = company नाव फक्त evidence असेल तर. हे जिंकते. लक्षात ठेवा.
Ravindra Bagale's Tip – हिंदी
MNC interview project में "50 tools + 3 company names" dump नहीं. तीन screenshots: weak → proof → fixed. Ethics line पहले. Source discipline = company का नाम सिर्फ़ evidence हो तो. यही जिताता है. याद रखो.
Lab
Complete the Project box below end-to-end on host-only. Then write a 12-line clean-English "tell me about a security project" script that never invents an MNC client name. Practise twice aloud.
Project: Build it, hack it, fix it
Build: For fictional Raja-Rani Traders (Kolhapur) on YOUR host-only Amazon Linux / Ubuntu VM 192.168.56.50, deploy a tiny PHP+MySQL (or SQLite) staff login + order lookup that deliberately (1) uses string-concat SQL, (2) sets session cookie without HttpOnly/Secure on HTTP, (3) leaves lab firewall open to Kali for 80/22, (4) writes auth failures only to a local file you will later "triage" like a mini-SIEM. Theme commands: sudo yum install httpd php mysql (or mariadb-server) then sudo service httpd start / sudo service mysqld start (Ubuntu: apt + sudo service apache2 start). Snapshot pre-mnc-weak. Hack (lab only / interview English): From Kali 192.168.56.10, nmap -sS -T2 -p 22,80,443,3306 192.168.56.50; explain how a quoted OR payload on the order field changes the WHERE clause; show cookie readable on clear HTTP; show failed-login lines in your log file. Never sqlmap the internet; never demo Kerberos forge steps. Fix: PDO/mysqli prepared statements; HTTPS (lab cert OK); cookie HttpOnly/Secure; sudo nginx -t / apachectl configtest before reload; sudo service httpd restart; firewall allow 80/443/22 only from 192.168.56.10; MySQL bind localhost; optional fail2ban for SSH. Re-verify: old SQLi fails; DB port closed from Kali; cookie flags present; failed-login pattern documented as a triage note (4625-style thinking even on Linux logs). Interview closer: "This was my OWN lab for Raja-Rani fiction – I do not attack systems without written permission. In MNC rounds I discuss themes as candidate-reported, not as secret company papers."
Real incident: Capital One (2019)
Public reporting described a breach involving a misconfigured web application firewall / SSRF-style path that allowed access to data in Amazon S3, as widely reported at the time, with a large number of individuals’ data affected (say reported – no invented counts here). Weakness themes: cloud misconfiguration + over-broad data access. Defence mindset for MNC interviews: least privilege, SSRF allow-lists, S3 Block Public Access / tight policies, and continuous cloud config monitoring. Source: US court documents and major contemporaneous press / company disclosures (verify; say "reported").
Real incident: SolarWinds / SUNBURST (2020)
Public reporting described a supply-chain compromise of SolarWinds Orion software updates that led to follow-on intrusions at multiple organisations, as reported by US agencies and major press. Weakness themes: trusted update channel abuse + detection lag for subtle C2. Defence mindset: software supply-chain risk awareness, egress monitoring, privileged-access hygiene, and layered detection – not only perimeter firewalls. Source: CISA / major vendor advisories and investigative reporting (verify; say "reported").
Q69. How do you cite an MNC-related theme without inventing facts?
I name the theme, say candidate-reported, and if a public source backs a company name I mention that source class (TechGig article, GeeksforGeeks experience, LinkedIn candidate post). If not, I say frequently asked across MNC interviews. I do not invent ticket numbers or salary claims.
Q70. How do you cite a real breach without inventing numbers?
I name the incident, the well-known timeframe in parentheses, the weakness theme, and the control lesson. I say "as reported" for scale. Example themes: cloud misconfig (Capital One (2019)), supply chain (SolarWinds (2020)).
Q71. What NIST CSF functions should you remember for Wipro-style rounds?
(Theme: TechGig / Wipro — candidate-reported.) Identify, Protect, Detect, Respond, Recover. I map a SOC day: asset inventory (Identify), hardening (Protect), SIEM (Detect), IR playbooks (Respond), backups/lessons (Recover).
Q72. Closing line if asked "Will you hack our client in week one?"
No. I will follow written scope, laws, and employer process. I practise offence only in labs I own so I can defend clients better – least privilege, patching, monitoring, and honest escalation.
Thodkyaat sangaycha tar
- MNC interview prep = candidate-reported sources + ethics + STAR + OWN-lab proof.
- Company named only with a public page actually read (Wipro, Accenture, TCS, Deloitte themes in appendix); else frequently asked across MNCs.
- Themes covered: networking/CIA/DDoS, Linux + Event IDs, SIEM/MITRE/Kill Chain, identity awareness (no exploit steps), AWS misconfigs, OWASP + SPF/DKIM/DMARC, HR mix.
- Project Build-Hack-Fix for Raja-Rani = weak PHP → explain → fix → triage note.
- Real incidents (Capital One (2019), SolarWinds (2020)) = cloud misconfig + supply-chain lessons — known facts only.
- Next: CEH exam-module map with practice questions (still ethics first).
Samjla ka? MNC interview Q and A complete – sources honest, English answers, OWN lab stories. Pudhe **CEH exam-module map** with practice questions. Chala practice kara, mitrano!