Registration, task submissions and review are free. An optional ₹99 verified certificate requires all assigned approvals and the selected program's date conditions.
Practise defensive utilities inside an authorized scope
Choose this track for password checks, port status, email-risk indicators, file protection, login controls, encryption and lab packet statistics. Check your scripting and networking foundations first, and use only your own disposable files and explicitly authorized systems. A task assignment is not permission to scan a public target or capture unrelated traffic.
State the test scope and inputs in your submission. Explain why a heuristic flagged an email, how an encryption round trip was checked, or what a failed-login limit actually did. Remove keys and private payloads from public proof. Compare Ethical Hacking for a lab-assessment/reporting path. The project evidence workflow helps make a defensive result inspectable without exposing secrets.
Seven defensive programming tasks
The standard program includes the following tasks plus LinkedIn offer-letter onboarding. The starter includes onboarding and the first two tasks.
1. Password Strength Checker
Evaluate demonstration passwords using entropy calculations and security-policy criteria. Explain what your score measures and what it cannot establish about real-world account security.
Submit: Code repository and command-line output screenshots. Never collect or display real passwords.
2. Port Status Checker
Build a Python or C++ socket utility that reports open ports and service responsiveness. Run it against your own lab host or an explicitly authorised target.
Submit: Source script and execution logs with the test scope stated.
3. Email Risk Analyzer
Inspect headers and body text for phishing or spoofing indicators. Explain why each flag appeared and avoid treating a single heuristic as proof of malicious intent.
Submit: Python source and analysis PDF. Download safe email examples.
4. File Protection Utility
Implement local-file encryption and decryption using the brief's AES-256 requirement. Test only disposable demonstration files and verify a successful round trip.
Submit: Python encryption script and verification screenshots. Keep keys out of public source.
5. Login Attempt Control System
Demonstrate account lockout after repeated failed attempts in an application you control. Explain the threshold and recovery behaviour.
Submit: Source and tests showing lockout enforcement. Download fictional login events.
6. Cryptographic Encryption Vault
Build a directory-encryption demonstration. Use a copied test directory and explain key handling, error recovery and the difference between your learning tool and a production security product.
Submit: Vault code and execution screenshots.
7. Network Packet Sniffer
Inspect protocol statistics from an authorised lab network. Avoid collecting unrelated users' traffic, private payloads or credentials.
Submit: Python source and a safe sample network log.
Permission is part of the project
State the lab environment and authorised scope in your README. Use synthetic identities, example domains and disposable files. Do not scan public systems or publish captured credentials. Remove sensitive packet contents before sharing proof.
Explain normal, failure and empty-input behaviour. A reviewer should be able to inspect your code and reproduce the demonstration without gaining access to a real system. For a report-focused lab roadmap, compare Ethical Hacking.
Dates, participation and certificate
Standard durations are 30, 45 or 60 days with eight total tasks. The 7 Days Starter Instant Internship has three tasks and no submission deadline while unpaid. Verified optional payment after starter approvals becomes its end date. Standard certificate access follows the dashboard's date rules.
This is a private educational program without a job, stipend, placement or college-credit guarantee. Read the complete conditions.