Forem: Saranyo Deyasi

The “Silicon Shield”: Analyzing India’s Unified Cyber Command (IUCC)

Saranyo Deyasi — Wed, 01 Apr 2026 17:31:34 +0000

In modern warfare, the first shot isn’t fired from a rifle; it’s a line of code hitting a power grid.

A city goes dark. Communication collapses. Defense systems freeze.

No explosions. No warning.

Just silence.

The real question is — is India ready for a “Blackout” scenario?

The Rise of Cyber Warfare
Traditional warfare is evolving. Tanks and missiles still matter, but today, wars can begin in server rooms instead of battlefields.

Countries are investing heavily in cyber capabilities because:

Attacks are cheap but devastating
Attribution is difficult (you can hide who attacked)
Critical infrastructure is increasingly digital
India is no exception.

India’s Cyber Backbone: The Defence Cyber Agency
India took a major step by establishing the Defence Cyber Agency (DCyA).

But here’s the key shift:

[i] India is moving from a reactive defense mindset
[ii] to a proactive deterrence strategy

This means:

Not just defending against attacks
But also developing the capability to respond or retaliate
Towards a Unified Cyber Command (IUCC)
Currently, cyber operations are spread across:

Army cyber units
Navy cyber divisions
Air Force cyber intelligence
The vision? A Unified Cyber Command (IUCC) that integrates all three.

Why this matters:

Faster response during attacks
Centralized intelligence
Coordinated offensive + defensive operations
Think of it as: A single brain controlling all cyber defense and offense instead of three separate ones.

The Technical Battlefield: Air-Gapped Systems
India’s most critical infrastructure — especially:

Nuclear facilities
Power grids
Strategic defense systems
often rely on Air-Gapped Systems.

What does that mean?
👉 These systems are completely isolated from the internet.
No WiFi. No external connections.

Sounds safe, right?

The Reality: Air-Gap ≠ Invincible
Even air-gapped systems can be compromised.

The most famous example is Stuxnet — a highly sophisticated cyber weapon.

What made it dangerous:

It spread via USB drives
It targeted industrial control systems
It caused physical damage without direct internet access
This changes everything.

The Real Threat: “Stuxnet-Style” Attacks
For India, the biggest cyber threat isn’t just hacking websites.

It’s: Silent, targeted attacks on critical infrastructure.

Imagine:

A power grid failure across multiple cities
Disruption in military communication systems
Interference with nuclear monitoring systems
All triggered remotely.

This is what a modern cyber war looks like.

🚀 From Defense to Deterrence
India’s evolving strategy is clear:

Build strong defenses
Detect threats early
Develop offensive cyber capabilities
Because in cyber warfare:
The best defense is often the ability to strike back.

🧩 Final Thoughts
The battlefield has changed.
The next war may not begin with a missile launch —
but with a malicious script executed silently in the background.
India’s push toward a Unified Cyber Command is not just necessary —
it’s inevitable.
The only question is:
Will the Silicon Shield be ready before the next blackout?

Inside a Cyber Attack: How Hackers Think, Operate, and Exploit Systems

Saranyo Deyasi — Fri, 27 Mar 2026 06:49:34 +0000

Introduction
When a cyber attack makes headlines, the story is often simplified: a system was hacked, data was stolen, and damage was done.
But behind every successful attack lies a carefully planned sequence of actions, driven not just by tools—but by strategy, patience, and psychology.
Understanding how attackers think is one of the most important steps toward building effective defenses.

The Mindset of an Attacker
A cyber attacker does not randomly target systems. Instead, they think like a strategist:

Where is the weakest point?
What can be exploited with minimum effort?
How can I remain undetected?

In many cases, the weakest link is not technology—but human behavior.

Stage 1: Reconnaissance (Information Gathering)
Every attack begins with observation.
Attackers collect as much information as possible about their target:

Public websites
Employee details (LinkedIn, social media)
Email formats
Technology stack being used This phase is silent but critical. The more information gathered, the higher the chances of a successful attack. Defensive Insight: Organizations must limit unnecessary public exposure and train employees to be cautious about the information they share online.

Stage 2: Initial Access (Finding the Entry Point)
Once enough data is collected, attackers look for a way in. Common entry methods include:

Phishing emails
Weak or reused passwords
Unpatched software vulnerabilities Often, a single mistake—like clicking a malicious link—can open the door. Defensive Insight: Strong password policies, regular updates, and user awareness training can prevent most entry-level attacks.

Stage 3: Exploitation and Privilege Escalation
After gaining access, the attacker’s goal is to expand control.
They may:

Move across systems (lateral movement)
Gain higher-level permissions (admin access)
Install hidden backdoors At this stage, the attack becomes more dangerous, as the attacker is no longer an outsider—they are inside the system. Defensive Insight: Monitoring unusual activity and restricting user permissions are key to stopping attackers early.

Stage 4: Action on Objectives
Now the attacker executes their main goal. This could include:

Data theft (sensitive information, credentials)
System disruption (DDoS, ransomware)
Surveillance or espionage At this point, the impact becomes visible—and often costly. Defensive Insight: Data encryption, backups, and incident response planning can reduce damage significantly.

Stage 5: Covering Tracks
A skilled attacker does not simply leave—they erase evidence.
Logs may be deleted
Activities hidden
Backdoors left for future access
This makes detection and investigation much harder.
Defensive Insight:
Advanced logging systems and continuous monitoring are essential for identifying hidden threats.

Why This Matters Today
In a rapidly digitizing country like India, cyber threats are increasing alongside technological growth.
Organizations, governments, and individuals must understand that:
Cybersecurity is not just about tools—it is about understanding the attacker’s mindset.
Even popular media like Special Ops reflects this growing importance of combining intelligence with technology, though real-world scenarios are far more complex and less visible.

Conclusion
A cyber attack is not a single event—it is a process.
Each stage presents an opportunity to detect, prevent, or mitigate damage. The key is awareness, preparation, and continuous learning.
The future of cybersecurity will not be defined by those who react to attacks, but by those who can anticipate and understand them before they happen.

The Silent Battlefield: How Cyber Warfare is Redefining Power in the 21st Century

Saranyo Deyasi — Tue, 24 Mar 2026 18:34:12 +0000

Introduction
In the 21st century, wars are no longer fought only with bullets, tanks, or missiles. A new battlefield has emerged—silent, invisible, and far more unpredictable: cyberspace. Cyber warfare is about disruption, control, and influence, and it has the power to impact nations without a single soldier crossing a border.

Why Cyber Warfare Matters?

Cyber attacks can:
Paralyze banking systems
Shut down power grids
Disrupt communication networks
Influence national decisions

These attacks demonstrate that cybersecurity is no longer just a technical requirement—it is a national security priority.

Countries like China, United States, and Russia are investing heavily in both offensive and defensive cyber operations. For a rapidly digitizing nation like India, protecting critical infrastructure is increasingly challenging and essential.

Challenges for India
Growing attack surfaces due to increased internet penetration
Need for skilled cybersecurity professionals
Public and organizational awareness of cyber threats still limited
Without strong talent and research, even advanced systems can become vulnerable.

Lessons from Media
Shows like Special Ops dramatize intelligence operations alongside technology experts. While fictional, these portrayals highlight a truth: the future of national security depends on integrating cyber intelligence with human strategy.

The Modern Cyber Expert
Today, a cybersecurity professional must be more than a defender of systems. They must:

Understand attacker psychology
Anticipate threats before they occur
Build resilient systems
Operate strategically, sometimes in secrecy This evolution demands a new generation of thinkers: individuals who are technically skilled and strategically aware.

“Meta-Security: Rethinking Trust, Incentives, and the Insider Threat”

Saranyo Deyasi — Tue, 03 Mar 2026 07:54:21 +0000

📝 Meta-Security: Rethinking Trust, Incentives, and the Insider Threat

Most security discussions focus on vulnerabilities, patches, and exploits.

But the real weaknesses are often hidden deeper — in assumptions, incentives, and trust models.

Before solving security problems, we need to question the thinking that built the system.

This is meta-security.

What Is Truly “Unsolvable”?

The insider threat is often described as unsolvable.

If a trusted administrator decides to leak data or destroy systems, the system is technically behaving correctly. It is obeying an authorized user.

You cannot patch human intent.

But “unsolvable” does not mean “undefendable.”

It means the solution cannot rely purely on technical barriers.

What Problems Are Social, Not Technical?

Phishing and pretexting show a critical reality:

Encryption doesn’t matter if a human voluntarily hands over credentials.

Security fails faster through trust exploitation than cryptographic weakness.

This reveals something deeper:

Security is as much psychology as it is engineering.

What Problems Are Actually Economic?

Zero-day markets exist because incentives are misaligned.

A vulnerability may be worth:

$20,000 to a company

$2,000,000 to a government buyer

When offensive discovery pays more than defensive reporting, vulnerabilities flow toward profit.

Security is governed by incentives, not morality.

What Solutions Create New Risks?

Single Sign-On centralizes authentication.

It reduces password chaos — but increases blast radius.

Convenience often trades distributed weakness for centralized risk.

Security is rarely about eliminating danger.
It’s about choosing where danger lives.

What Defense Helps Attackers?

Verbose system feedback.

Every detailed error message becomes an oracle.

Attackers learn through feedback loops.
Security must limit deterministic feedback.

What Is Security Theater?

Password rotation policies that create predictable mutations.

Controls designed to satisfy auditors rather than stop modern threats.

Security theater looks protective.
But protection without effectiveness is ritual, not defense.

What Is Security Based on Faith?

The supply chain.

Every library, package, and dependency is an act of probabilistic trust.

We do not verify every line of code.

Modern systems are built on layered trust we cannot fully inspect.

The Real Insight

Security is not just a technical discipline.

It is:

An incentive structure

A trust model

A governance design

A psychological system

And nowhere is this clearer than the insider threat.

Engineering Against the “Unsolvable” Insider

If betrayal cannot be eliminated, it must be engineered against.

My strategy: Trust, but Verify.

Pillar 1: Principle of Least Privilege + Just-In-Time Access

No permanent admin rights.

Access is:

Requested

Time-bound

Automatically revoked

Goal: Minimize blast radius.

If someone goes rogue, they can damage a room — not the building.

Pillar 2: The Two-Person Rule (M-of-N Control)

No catastrophic action should be executable by a single individual.

Critical actions require dual authorization.

Goal: Increase conspiracy cost and psychological friction.

Betrayal now requires recruitment — not impulse.

Pillar 3: Behavioral Detection (UEBA)

Intent leaves patterns.

If a user suddenly:

Accesses unusual systems

Downloads abnormal data volumes

Operates outside normal hours

The system escalates scrutiny.

Not punishment.
Not paranoia.

Friction.

The goal is early anomaly detection before irreversible damage occurs.

The Philosophy

You cannot remove free will.

So security must:

Reduce standing power

Increase visibility

Add delay to destructive actions

Increase collaboration cost

Detect anomalies early

Limit blast radius

The insider threat is not unsolvable.

It is irreducible.

And irreducible risks must be managed structurally, not emotionally.

Final Thought

Security is not about distrusting people.

It is about designing systems that remain stable even when trust fails.

Trust should enable productivity.

Verification should protect reality.

That balance is the future of security design.

Security Fails Because Incentives Fail

Saranyo Deyasi — Tue, 03 Mar 2026 07:43:25 +0000

Security Fails Because Incentives Fail
When we talk about cybersecurity, we usually focus on vulnerabilities, exploits, and patches.

But after thinking deeply about security economics, I realized something uncomfortable:

Security doesn’t fail because engineers are incompetent.

It fails because incentives are misaligned.

Who Benefits When Security Is Weak?

Obviously, threat actors benefit.

But they aren’t the only ones.

Product managers benefit from high velocity.
Fewer security controls mean:
Faster release cycles
Less friction
Lower development costs
In the short term, shareholders benefit too.
Money not spent on “invisible” protection increases margins.
Security success looks like nothing happened.
Velocity shows up on dashboards.
Incentives follow metrics.

Who Pays When Security Fails?

The first to pay are usually end users.

They lose:

Identity

Financial data

Time

Trust

Sometimes CISOs and security engineers pay with their jobs.

Companies pay reputation damage.

But here’s the deeper problem:

The people harmed are often not the same people making security budget decisions.

When cost and decision-making are separated, security weakens structurally.

Who Decides Security Budgets?

Typically the CFO and the Board.

Security is often treated as a cost center.

Budgets are frequently driven by compliance:

“What is the minimum required to stay legal?”

The issue isn’t ignorance.

It’s that security risk is probabilistic.
Feature revenue is measurable.

You can measure revenue from a new product feature.

You cannot precisely measure revenue saved from preventing a hypothetical breach.

And in business, measurable value usually wins.

What Gets Removed for Convenience?

Session timeouts are a classic example.

Users hate being logged out frequently.
So sessions are extended.

This increases the window for session hijacking.

Convenience expands attack surface.

Security friction competes directly with user retention.

What Risks Are Ignored Because They’re “Unlikely”?

Physical data center breaches.
Black swan infrastructure failures.
Extreme disaster scenarios.

Companies calculate expected loss:

Probability × Impact

If probability feels extremely low, mitigation feels wasteful.

The problem?

Probability estimates are often wrong.

What Vulnerabilities Exist Because Fixing Them Is Boring?

Dependency management and patching.

Updating libraries is tedious.
It doesn’t create flashy features.

So technical debt accumulates.

Security debt compounds silently.

When something like Log4j happens, the cost of boring neglect becomes visible overnight.

What Would Be Secure But Terrible for User Experience?

Air-gapped authentication.

It would be extremely secure.

It would also be impractical for most users.

If security is too inconvenient, users leave.

Security is not about maximum protection.

It’s about optimal friction.

The Real Pattern

Security is governed by incentives, not ignorance.

Speed is rewarded.

Profit is rewarded.

Usability is rewarded.

Compliance is enforceable.

Hypothetical risk is abstract.

Security is reactive because growth is proactive.

Until the cost of insecurity directly reaches decision-makers, security will always be slightly late.

Final Thought

Security is not just a technical discipline.

It is economics.
It is psychology.
It is governance.
It is design.

And most importantly:

It is an incentive problem.

Why Security is Always Late: Economics, Zero-Days, and Attacker Math

Saranyo Deyasi — Mon, 02 Mar 2026 18:14:37 +0000

We’ve all seen the headlines. Another day, another massive data breach, another critical system compromised, another "we take security seriously" statement.

It raises a cynical, yet crucial question: Why is security always the last thing to arrive?

We pour billions into cybersecurity, yet we are always reacting. We buy the locks after the house has been robbed.

This isn't just a failure of imagination or technology. It is a failure dictated by the harsh economics of software development, the immutable laws of complexity, and the fundamental asymmetric math of attack and defense.

Security is not late because engineers are careless. It’s late because reality moves faster than assumptions.

Security Doesn’t Ship Products We have to start with the uncomfortable reality of business economics. Every software project exists under the intense pressure of "time to market."

When a company builds a product, they are focused on Value Delivery. They need a feature that solves a problem, generates revenue, or attracts users. If they don't deliver that value quickly, a competitor will.

In this high-stakes race, security is often viewed not as a feature, but as friction.

Security doesn't demo well: No investor has ever been thrilled by a product whose main feature is "it didn't get hacked today."

Security increases complexity: Strong authentication, encryption, and input validation all add friction to the development cycle and the user experience.

The Cost-Benefit Fallacy: Spending $50,000 on security auditing feels like a loss, while spending $50,000 on marketing feels like an investment.

The market rewards the first to ship, not the safest to ship.

Speed Creates Unknown Vulnerabilities When speed is the metric, shortcuts are inevitable. This is the concept of Technical Debt applied to security.

The fastest way to build a feature is rarely the most secure way.

The Problem of Dependencies: To move quickly, developers rely heavily on third-party libraries and open-source packages (like npm or pip). This is essential for modern development, but it means your application is only as secure as the weakest link in a chain of code you didn't write. Remember Log4j?

Configuration Drift: In the rush to get a service live, "good enough" configurations become permanent. Default settings—which are designed for ease of use, not security—remain in production, creating open doors.

The Complexity Paradox: The faster you build, the more complex the system becomes. As the number of components and interactions grows, the possible attack paths expand exponentially. Complexity is the enemy of security.

Every line of code written in haste is a potential invitation to an attacker.

Defenders vs. Attackers is Not a Fair Game The core problem of cybersecurity is that it is a fundamentally asymmetric game. The math does not favor the defender.

The Defender's Dilemma
A defender must protect every single point of entry, every line of code, every configuration setting, every open port, and every employee from a phishing email. They have to get it right 100% of the time, 24 hours a day.

The Attacker's Advantage
An attacker only needs to find one single weakness. They only need to get it right once.

Furthermore, attackers have their own favorable economics. A team of highly paid, professional penetration testers costs hundreds of thousands of dollars to defend a system. A lone attacker using automated tools to scan the entire internet for known vulnerabilities costs almost nothing.

Security is always late because the defenders are trying to build a perfect wall, while the attackers only need a ladder.

Why "Secure by Design" is Hard in Reality The industry consensus is that we must shift security "left," integrating it into the design phase of the development lifecycle (SDLC). While theoretically sound, implementing "Secure by Design" is exceptionally difficult.

It requires a fundamental shift in mindset:

From Features to Threat Models: It demands that architects anticipate not just what a user will do, but what an attacker might do.

From Speed to Scrutiny: It requires slow-downs, such as code reviews and architecture analysis, when the entire ecosystem is screaming for speed.

The Knowledge Gap: It assumes that every developer is a security expert. The reality is that secure coding is a specialized skill that is often not taught in computer science degree programs or bootcamps.

We want "Secure by Design," but the market rewards "Fast to Deliver."

Why Security Always Follows Failure This all culminates in the reactive nature of the industry. The vast majority of security spending is triggered by a failure event.

A "Zero-Day" vulnerability—a flaw known to attackers but unknown to the defenders—exists by definition before the patch. We can only create a vaccine once we have identified the virus.

This creates a necessary and tragic loop:

A new technology is built (IoT, Cloud, AI).

It is shipped as quickly as possible, ignoring security for features.

The technology gains widespread adoption.

A significant attack succeeds, exposing the critical flaw.

Only then does security receive the funding, attention, and mandates required to "fix" the problem.

This pattern is not a failure of individual engineers; it is the systemic consequence of prioritizing immediate value over long-term stability.

Final Thought
We will never "solve" security. As long as we build software, we will create vulnerabilities. We must accept that security will always be a step behind.

"Security is not late because engineers are careless — it’s late because reality moves faster than assumptions."

Why sudo exists: Linux’s solution to shared power and shared blame

Saranyo Deyasi — Mon, 02 Mar 2026 17:45:40 +0000

The Problem: The All-Powerful Root
In Linux, the root account is the "God mode" of the system. It has the power to read any file, delete the entire operating system, or change hardware settings.

Before sudo became the standard, there were two bad options for managing a system:

Sharing the Root Password: You give the administrative password to everyone who needs to install a printer.

The Risk: If one person makes a mistake or gets hacked, the entire system is toast. You also have no idea who ran which command.

Logging in as Root: Staying logged in as the superuser for your daily tasks.

The Risk: A simple typo like rm -rf / (delete everything) happens instantly without a "Are you sure?" prompt.

The Solution: sudo
sudo acts as a controlled gatekeeper. It solves three specific technical problems:

The Principle of Least Privilege
Instead of being "all-powerful" all the time, you operate as a normal, restricted user. You only "elevate" your privileges for the five seconds it takes to run a specific command. This prevents accidental system-wide damage from daily browsing or scripts.
Fine-Grained Access Control
Through a file called /etc/sudoers, a System Administrator can give specific users permission to run only specific commands.

Example: You can let the "Junior Admin" restart the web server, but forbid them from touching the database or deleting users.

Accountability (The Audit Trail) When you use sudo, the system logs the event. It records who ran the command, when they ran it, and exactly what they did. If the system crashes, you can look at the logs to see the specific command that caused the failure.

How it Works Technically
When you type sudo [command]:

Authentication: sudo asks for your password, not the root password. This proves you are who you say you are.

Authorization: It checks the sudoers file to see if you have permission to run that specific command.

SetUID Bit: Technically, the sudo binary has a special "SetUID" permission bit. This allows the program to temporarily assume root's identity to carry out the task you requested.

From Curiosity to Code: My Technical Journey and Future Predictions

Saranyo Deyasi — Mon, 23 Feb 2026 17:50:04 +0000

When I first started exploring technology, I didn’t know where it would lead me. I was just a curious kid tinkering with computers, trying to understand how things worked. Fast forward a few years, and technology has become not just a passion but a pathway to learning, experimenting, and creating.

My Technical Journey

Over the years, I’ve dived into multiple areas of tech:

Programming & Web Development: I’ve built mini web projects, chat platforms, and interactive websites. Each project taught me something new—from managing backend logic to designing a user-friendly interface.

Artificial Intelligence & Data Analysis: Exploring AI has been a fascinating journey. I’ve worked with data analysis using Excel and implemented AI-based tools for practical use cases like automated content generation and predictive modeling.

Cybersecurity: Understanding the world of cyber threats and defense mechanisms has been eye-opening. I’ve created tools for penetration testing, phishing detection, and vulnerability scanning, which gave me hands-on experience in securing digital environments.

Project Management & Product Thinking: Beyond coding, I’ve learned how to structure projects, plan features, and iterate based on feedback—skills that are essential for turning ideas into real products.

Through all these experiences, the most important lesson has been that technology is not just about writing code—it’s about problem-solving, creativity, and resilience.

Key Lessons Learned

Consistency beats intensity: Small, regular efforts compound over time.

Curiosity drives growth: Never hesitate to explore unfamiliar domains; that’s where breakthroughs happen.

Failure is feedback: Every bug, every failed experiment, is a chance to learn and improve.

Collaboration is key: Working with others, even virtually, teaches you perspectives you can’t get alone.

Looking Ahead: Future Predictions in Tech

From my observations and experiences, here’s what I think the future holds:

AI will be ubiquitous: From automating routine tasks to creating complex solutions, AI will continue to reshape industries.

Cybersecurity will be more critical than ever: As technology advances, so will threats. Skills in security, ethical hacking, and threat intelligence will be in high demand.

IoT and Smart Systems will expand: Connected devices will dominate homes, cities, and industries, requiring developers to think about scalability, security, and efficiency.

Learning agility matters: The pace of tech evolution will make adaptability and continuous learning the most valuable skills.

Personally, I plan to keep exploring AI, cybersecurity, and emerging technologies, turning small experiments into impactful projects.

Advice to Fellow Learners

If you’re starting your tech journey, my advice is simple: explore boldly, fail quickly, and keep learning every day. Your unique experiences will shape the solutions you create, and the challenges you overcome will define your growth.

“No flower grows without rain, and no person becomes great without facing challenges.”

This philosophy guides me as I navigate my own path in technology, and I hope it inspires others to embrace the journey, no matter how uncertain it may seem.

I Realized Coding Is More About Thinking Than Typing

Saranyo Deyasi — Mon, 29 Dec 2025 11:59:48 +0000

When I first imagined a “good programmer,” I thought of someone typing insanely fast, switching between terminals, and writing thousands of lines of code without stopping.
Reality hit me hard when I started building real projects.
I realized something unexpected:
Most of my time coding is spent not typing at all.
Instead, I’m thinking.
Thinking about:
Why the code is failing even though it “looks right”
How data moves from one part of the program to another
What happens if the user enters the wrong input
Why fixing one bug creates two new ones

At first, this frustrated me.
I thought I was slow. I thought I wasn’t good enough.

But then I understood something important.

💡 Coding Is Structured Thinking
Typing code is the easy part.
The hard part is breaking a problem into steps that a machine can understand.
When code breaks, it’s rarely because of syntax.
It’s because of logic.
This changed how I approach programming. I stopped rushing and started thinking.

🌍 Real-World Connection
In the real tech industry, developers aren’t paid for how fast they type.
They’re paid for how clearly they think.
That’s why:
Senior developers write less code
Debugging is considered a skill
Problem-solving matters more than languages

🏁 Final Thought
Coding didn’t just teach me programming.
It trained my brain to think clearly, logically, and patiently — skills that apply far beyond computers.
Typing makes code. Thinking makes software.
I’m a young developer learning in public — feedback is welcome.

🌐 Building SafeNet Jr. — A Student-Friendly Browser with Parental Controls

Saranyo Deyasi — Thu, 28 Aug 2025 16:26:55 +0000

Intro:
One day, I asked myself: Why do browsers like Chrome or Brave get all the fun? Can I build my own? That’s when I started SafeNet Jr., a mini-browser with parental controls.

Features I added:

🚫 Blocked websites that distract students.

🎯 Focus Mode — auto-blocks YouTube, Netflix, and other entertainment sites.

🔐 Simple Parental Settings screen for adding/removing blocked sites.

Why this matters:
Students (like me!) get distracted a lot. Having a browser that encourages focus is a game-changer.

What I learned:

Web browsers are complicated, but even a demo version can teach you tons about HTML, CSS, and JavaScript.

UI design is just as important as coding.

Future idea:
Maybe one day, SafeNet Jr. could become a real student browser that schools use.

🤖 How I Built an AR Solar System Project with Python

Saranyo Deyasi — Wed, 27 Aug 2025 18:01:40 +0000

Making the Solar System Come Alive with Augmented Reality (School Project)

In school, we were learning about planets, and I thought: What if I could see them floating in my room? That’s when I decided to build a mini Augmented Reality Solar System using Python.

How I did it:
🌍 Used Blender models for planets.
📱 Connected it with an AR library in Python.
🛰️ Added simple interactions like rotating planets with a click.

Challenges I faced:
Getting planet textures right 🌌.
Making the models small enough to run on my laptop.

Why this project is cool:
Because it made science fun. Instead of just reading about Saturn’s rings, I could actually see them in 3D space.

Tip for students:
You don’t need high-end devices. Start with basic 3D models and small AR libraries. The fun part is experimenting.

🔒 My First Cybersecurity Toolbox (Zerocool Edition)

Saranyo Deyasi — Wed, 27 Aug 2025 18:00:04 +0000

Title: Building My Own Cybersecurity Toolbox as a 12-Year-Old Developer

Cybersecurity always felt like something only professionals could do. But recently, I started building my own cybersecurity toolbox called Zerocool Toolbox. It’s not advanced yet, but it’s a cool way for me to explore ethical hacking and security.

What’s inside my toolbox?
🔍 Port Scanner – to check open ports on a system.
🛡️ Password Strength Checker – to test how secure a password is.
📡 Basic Network Sniffer – captures packets (for learning purposes).
🚫 Website Blocker – to block distracting or unsafe sites.

Why I built it?
To learn how hackers think (so I can defend better)
To practice Python networking libraries.
To have my own set of tools as a beginner.

Takeaway:
If you’re starting out in cybersecurity, don’t wait until you’re an expert. Start small, build tools, and share your progress. Even a simple password checker is a great step!