Tags: Cybersecurity, Privacy, Data Breach

A company gets hacked. The headline says the company suffered a breach. The press release calls it a security incident. The response is usually familiar: systems were secured, passwords were reset, law enforcement was notified, and users are advised to stay alert.

But sometimes, calling it an incident is too generous. If a company stores user data without basic security controls, a breach is not a surprise. It is a matter of time. Some breaches are not accidents. They are the outcome of neglect.

## The Breach Does Not End When Service Is Restored

For a company, a breach has a timeline. Detect the incident. Contain it. Investigate. Notify users. Patch systems. Publish a statement. Move on.

For users, the timeline is different. A leaked email address can invite phishing attempts for years. A leaked phone number can become a SIM-swap risk. A leaked password can be tested across dozens of other platforms. A leaked ID document can be reused in fraud attempts long after the original incident disappears from the news.

## Users Did Not Choose the Security Controls

Most users never chose the company's cloud provider, database design, encryption model, access control policy, logging system, vendor contracts, or incident response process. But when those controls fail, users inherit the consequences.

## A Password Reset Is Not Accountability

After many breaches, the advice given to users is simple: change your password, enable MFA, watch for suspicious emails, and monitor your accounts. This advice is useful, but it is also incomplete. It shifts the burden onto the user after the damage has already happened.

## The Real Attack Starts After the Breach

A data breach is often not the final attack. It is the beginning of many smaller attacks. Leaked emails become phishing lists. Leaked phone numbers become smishing targets. Leaked passwords become credential stuffing attempts. Leaked personal details make scams more believable.

## Accountability Should Follow the Risk

Companies ask users to trust them with personal data. That trust should come with responsibility. Security is not only about protecting servers. It is about protecting people from the consequences of system failure.

This article was originally published on Rihad Roshan.

About the author: Rihad Roshan is a cybersecurity researcher and blogger focusing on security automation, threat detection, and digital well-being.

Tags: OWASP, Security, Supply Chain

The 8th edition of the OWASP Top 10 2025 brings a refined focus on modern application risks. It aligns more closely with today's development practices, such as microservices, cloud-native architecture, and DevSecOps pipelines.

## What's New in OWASP Top 10 2025

The update highlights not just the presence of vulnerabilities, but the systemic flaws that lead to them. This blog explores what's new, what's changed, and why these updates matter for researchers, developers, and defenders working on secure software systems.

## Key Changes and Updates

The 2025 edition introduces a sharper perspective on application security risks — reflecting both the evolution of attacker techniques and the complexity of modern ecosystems.

### Supply Chain Security

Supply chain attacks have become increasingly prominent, targeting the software development lifecycle itself. The updated framework addresses these modern threat vectors.

### Cloud-Native Architecture Risks

With the widespread adoption of microservices and containerization, new attack surfaces have emerged that require specialized attention.

## Implementation Guidelines

Practical steps teams can take to improve their security posture and align with the updated OWASP recommendations.

### Development Team Actions

Specific recommendations for development teams to integrate security into their workflows.

### Security Team Considerations

Guidance for security professionals on implementing these recommendations across their organizations.

This article was originally published on Rihad Roshan.

About the author: Rihad Roshan is a cybersecurity researcher and blogger focusing on security automation, threat detection, and digital well-being.

Tags: Technology, Digital Minimalism

We talk a lot about digital security — passwords, firewalls, and two-factor authentication. But what about the most valuable asset we're losing in the digital age? Our time. Our attention. Our peace.

## The Silent Prison We Built

We're not talking about the scams that try to steal your money; we're talking about the silent prison we voluntarily walked into. This new prison has no walls, no guards, and no bars. Its architecture is built from screens, notifications, and the endless scroll.

## The Illusion of Connection

We call it connection, but for many of us, it's closer to constant surveillance by our own devices. Every tap, swipe, and scroll is monitored, analyzed, and optimized to keep us engaged.

### Attention as Currency

Our attention has become the most valuable commodity in the digital economy. Companies compete fiercely for every second of our focus.

### The Dopamine Economy

Social media platforms and apps are designed to trigger dopamine releases, creating addiction-like behaviors that keep us coming back.

## Breaking Free from Digital Arrest

Reclaiming our attention and finding pauses in a noisy world requires intentional effort and strategic choices.

### Digital Minimalism Strategies

Practical approaches to reducing digital overwhelm and creating space for meaningful activities.

### Mindful Technology Use

Developing awareness around our device usage and creating healthy boundaries with technology.

This article was originally published on Rihad Roshan.

About the author: Rihad Roshan is a cybersecurity researcher and blogger focusing on security automation, threat detection, and digital well-being.

Tags: Cybersecurity, Automation, SOAR, EDR

Cybersecurity incidents don't wait. Every second counts — and in those moments, automation can make the difference between a quick recovery and a full-blown breach.

## The Need for Automation

That's what inspired me to build my own automated threat detection and response workflow, combining LimaCharlie, Tines, Slack, and Email. This project demonstrates how modern tools can work together to detect threats, alert teams in real time, and even isolate compromised systems.

## Architecture Overview

The automation workflow integrates several key components to create a comprehensive security response system.

### LimaCharlie EDR Integration

LimaCharlie serves as the primary endpoint detection and response platform, providing real-time monitoring and threat detection capabilities.

### Tines Workflow Orchestration

Tines acts as the central orchestration engine, managing the flow between different security tools and automating response actions.

### Communication Channels

Integration with Slack and email ensures that security teams are immediately notified of threats and can coordinate response efforts.

## Implementation Details

Step-by-step breakdown of how to build your own automated security response system.

### Setting Up Detection Rules

Configuration of detection rules in LimaCharlie to identify various threat patterns and malicious activities.

### Workflow Automation

Creating automated workflows in Tines to handle different types of security incidents.

### Response Actions

Automated response capabilities including system isolation, evidence collection, and team notification.

## Keeping Analysts in Control

While automation handles routine tasks, critical decisions remain with human analysts to ensure appropriate response to complex threats.

This article was originally published on Rihad Roshan.

About the author: Rihad Roshan is a cybersecurity researcher and blogger focusing on security automation, threat detection, and digital well-being.