Abida Chowdhury | Cybersecurity Insights

Send Email LinkedIn logo
Portraot of Abida Chowdhury

Hi, I’m Abida.

Technical insight. Business perspective. Security in practice.

With more than 20 years across IT, banking, and finance, I bring a business-focused perspective to cybersecurity. I understand why protecting information, maintaining trust, and managing risk matter to organizations.

This blog connects that experience with hands-on work in Azure, Linux, cloud security, and web application protection. Through practical projects and clear analysis, I explore how security controls work, where their limitations lie, and how thoughtful configuration strengthens protection.

My focus is clear: turn technical knowledge into informed decisions and practical security improvements.

Blog Posts

Image 1

HTTPS and Digital Trust: Securing the Connection

Azure · HTTPS · TLS · Certificates · Cloud Security

A professional website needs more than a polished appearance: it needs a secure connection that visitors can trust. HTTPS uses Transport Layer Security, or TLS, to protect data exchanged between a browser and a server. Encryption helps prevent someone monitoring network traffic from reading information in transit. A digital certificate also helps the browser verify the identity of the server.

Trusted certificates establish that identity through a chain leading to a certificate authority recognized by the browser. A self-signed certificate can support encryption, but browsers generally warn visitors unless they explicitly trust it. This distinction matters because an encrypted connection does not automatically establish a trustworthy identity. For a custom domain, the certificate must cover the hostname visitors use and be correctly configured for the application.

Azure Key Vault provides controlled storage and management for certificates, keys, and secrets. Checking certificate expiration, hostname coverage, and the trust chain helps identify common connection problems. HTTPS protects communication in transit, but it does not replace secure application code, access controls, or updates. Strong website security combines a trusted connection with careful configuration and ongoing maintenance.

Image-2

Web Application Defense: Turning Security Rules into Protection

WAF · Web Security · Managed Rules · Access Control

Every public website can receive malicious requests alongside legitimate visits. A web application firewall, or WAF, inspects web requests using configured security rules. Managed rule sets help detect common attack patterns, including SQL injection and cross-site scripting. These controls add protection, but they do not eliminate the need to fix vulnerabilities in the application.

Custom rules allow administrators to apply additional controls based on an application's requirements. Geographic filtering, for example, can restrict requests according to the country associated with a source IP address. This project's activity guide uses the United States, Canada, and Australia as approved locations for its exercise. Such filtering has limitations because attackers can route requests through infrastructure located in an allowed country.

A WAF policy must be associated with a supported service handling the website's traffic before it can inspect requests. Testing and reviewing logs help identify rules that unintentionally block legitimate visitors. Microsoft Defender for Cloud complements this work by identifying security recommendations for cloud resources. Effective web application defense combines request filtering, secure configuration, and regular monitoring.