<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by whit3h473r on Medium]]></title>
        <description><![CDATA[Stories by whit3h473r on Medium]]></description>
        <link>https://medium.com/@srisabeshan271?source=rss-82d7a2cef9ad------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*eK5fQ2eZcNCDPt5B</url>
            <title>Stories by whit3h473r on Medium</title>
            <link>https://medium.com/@srisabeshan271?source=rss-82d7a2cef9ad------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:25:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@srisabeshan271/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How a small software company can make an ISMS useful]]></title>
            <link>https://medium.com/@srisabeshan271/how-a-small-software-company-can-make-an-isms-useful-0db839d62f59?source=rss-82d7a2cef9ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/0db839d62f59</guid>
            <dc:creator><![CDATA[whit3h473r]]></dc:creator>
            <pubDate>Tue, 29 Sep 2026 06:21:38 GMT</pubDate>
            <atom:updated>2026-09-29T06:21:38.575Z</atom:updated>
            <content:encoded><![CDATA[<p>By Srisabeshan Asokan<br>IE3102 Assignment 02 companion article<br>Fictional case study. Prepared for publication; not yet published.</p><p>A software company can collect security policies without changing the way it handles customer information. The useful question is whether those policies lead to clear decisions, reliable routines and evidence that someone checks.</p><p>This article uses NilaSoft, a fictional Sri Lankan company with 45 employees and a hosted business application, to explore that question. Its proposed toolkit uses ISO/IEC 27001:2022 as the requirements reference. ISO/IEC 27002 supplies companion control guidance. The company and all figures below are educational assumptions, not observations about a real client. [1, 2]</p><h3>Begin with a service and its owners</h3><p>NilaSoft starts by defining the service it wants to protect. The scope includes software development, cloud configuration, customer support, office activity and remote working. It names the information involved and the people who can make decisions about it.</p><p>This is more useful than a vague promise to protect everything. When a support employee requests access to customer data, the scope and role record identify the owner who can approve the request. When a supplier changes its service, the company knows which dependency to reassess.</p><h3>Connect a risk to a testable action</h3><p>Consider account compromise. In the case study, its current likelihood is rated four and impact five, giving a qualitative score of twenty. NilaSoft proposes MFA, separate administrator identities and access reviews. The proposed target score is ten because the potential impact remains severe even when likelihood falls.</p><p>The target is deliberately still High. It keeps a management decision visible instead of suggesting that purchasing an authentication tool has solved the problem. The risk owner needs evidence of operation and either more treatment or an authorized exception.</p><p>NIST SP 800–30 supports structured risk assessment. The particular five by five scale is a local choice. Its scores prioritize discussion; they are not probabilities or monetary loss estimates. [3]</p><h3>Make control decisions explainable</h3><p>The Statement of Applicability links control decisions to business reasons. NilaSoft proposes office access controls because it has a physical office, even though a provider hosts production infrastructure. It proposes excluding outsourced development because all development is internal. That decision must be reviewed before any external development arrangement begins.</p><p>The toolkit also adds a company specific control requiring two reviewers for customer tenant setup. A useful control decision should explain the risk addressed, the responsible owner and the evidence expected. The ISO auditing practices paper discusses this approach, but its educational status means it does not replace the standard. [4]</p><h3>Test outcomes rather than paperwork</h3><p>A backup success notification cannot establish that the company can recover its service. A restore exercise should measure elapsed time, the age of recovered data and information integrity. Likewise, an access policy does not establish that a departing employee lost all access. The reviewer needs the actual closure record across relevant services.</p><p>An empty results table should remain empty or say “No data.” Turning the absence of tests into a green status creates false confidence. In the NilaSoft workbook, an objective with no assessable population does not show 100 percent achievement.</p><h3>Give management an honest financial case</h3><p>The fictional financial model estimates first year economic costs of LKR 2.75 million and annual gross benefits of LKR 2.2 million. That produces a negative first year ROI of 20 percent. The base simple payback is about 1.46 years, assuming benefits begin immediately and remain constant.</p><p>These estimates are uncertain. At a lower assumed treatment effectiveness, payback stretches to 8.75 years. Management therefore needs to validate effort, quotations and loss estimates. It must also avoid counting the same benefit as both avoided loss and increased productivity.</p><p>The decision may still support implementation because of customer obligations and unacceptable risks. However, those reasons should be stated directly instead of hiding an unfavorable financial result.</p><h3>Keep improvement connected to work</h3><p>The most useful toolkit links ordinary work to review. An incident produces lessons. A failed release creates corrective action. A supplier change prompts a risk review. Management then decides whether responsibilities, resources or controls need to change.</p><p>For NilaSoft, success would mean that people can explain these decisions and produce evidence that the processes operate. The proposed documents are a starting point for that work. They do not establish that implementation or certification has occurred.</p><h3>References</h3><p>1. ISO and IEC. ISO/IEC 27001:2022. <a href="https://www.iso.org/standard/27001">https://www.iso.org/standard/27001</a><br>2. ISO and IEC. ISO/IEC 27002:2022. <a href="https://www.iso.org/standard/75652.html">https://www.iso.org/standard/75652.html</a><br>3. NIST. SP 800–30 Revision 1. <a href="https://csrc.nist.gov/pubs/sp/800/30/r1/final">https://csrc.nist.gov/pubs/sp/800/30/r1/final</a><br>4. ISO IEC 27001 Auditing Practices Group. Statement of Applicability and conformity discussion. Educational note with nonendorsement disclaimer. <a href="https://committee.iso.org/files/live/sites/jtc1sc27/files/resources/ISO-IECJTC1-SC27-WG1_N3298_Auditing%20Practices%20Note%20-%20SoA.pdf">https://committee.iso.org/files/live/sites/jtc1sc27/files/resources/ISO-IECJTC1-SC27-WG1_N3298_Auditing%20Practices%20Note%20-%20SoA.pdf</a></p><p>AI assisted with the scenario and draft. The student should review, adapt and disclose that assistance before publication or submission. No publication or practical client consultation is claimed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0db839d62f59" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding and prevention mechanism of the of the sever side attacks]]></title>
            <link>https://medium.com/@srisabeshan271/understanding-and-prevention-mechanism-of-the-of-the-sever-side-attacks-67d61d5c3956?source=rss-82d7a2cef9ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/67d61d5c3956</guid>
            <dc:creator><![CDATA[whit3h473r]]></dc:creator>
            <pubDate>Thu, 12 Dec 2024 08:26:34 GMT</pubDate>
            <atom:updated>2024-12-12T08:26:34.601Z</atom:updated>
            <content:encoded><![CDATA[<h3>Understanding and prevention mechanism of the sever side attacks</h3><p>The attacks that target servers tend to seek out vulnerabilities in their infrastructure, applications, or configurations. These could compromise sensitive data, disrupt services, or give an attacker unauthorized control over server resources. The following are the common server-side attacks and their mechanisms in detail: 1. Injection Attacks</p><p>Description: This is where an attacker injects malicious input into a server application to manipulate or execute unintended commands.</p><p>Types:<br>SQL Injection: It takes advantage of the vulnerabilities in the SQL queries by injecting malicious SQL code to view or alter the database.<br> Example: ‘ OR ‘1’=’1 in a login form bypassing authentication.<br> Command Injection: It is a technique of injecting operating system commands through the inputs of a web application.<br>Example: Appending; rm -rf / to a command parameter for deleting the files on the server.</p><p>Prevention<br> Prepared statements or parameterized queries.<br> Sanitization and validation of user inputs.<br> Input length and type restriction must be strictly implemented.</p><p>2. Cross-Site Scripting (XSS)</p><p>Description: While this is often considered a client-side vulnerability, XSS attacks can be caused by vulnerable server-side applications that fail to sanitize user inputs properly.</p><p>Mechanism: Malicious scripts are injected into a web page displayed to other users, leading to data theft or session hijacking.</p><p>Prevention:<br> Encode outputs to prevent the execution of scripts.<br>Use Content Security Policy (CSP) to limit the resources allowed.<br> Always sanitize user inputs rigorously.</p><p>3. File Inclusion Vulnerabilities</p><p>Description: An attack occurs when an attacker exploits applications that dynamically include files based on user input.</p><p>Types:<br> Local File Inclusion (LFI): Read access of files on the server’s file system.<br>Example: /././etc/passwd to read sensitive server files.<br> Remote File Inclusion (RFI): Include external files hosted on an attacker-controlled server.</p><p>Prevention:<br> Restrict file paths and validate inputs.<br> Disable remote file inclusion in server settings.<br>Follow secure coding practices.</p><p>4. Distributed Denial of Service (DDoS)</p><p>Description: Attackers overwhelm the server with an overwhelming amount of traffic, which cannot respond to legitimate requests.</p><p>Mechanism: A network of compromised devices (botnets) sends continuous requests, exhausting server resources.</p><p>Prevention:<br> Rate-limiting and filtering of traffic.<br>Employ Cloudflare and AWS Shield DDoS protection services. Employ scalable infrastructure to handle very high spikes in traffic.</p><p>5. Privilege Escalation</p><p>Description: Attackers use weaknesses to gain privileges in the system that are above that level, such as administrative ones.</p><p>Mechanism: Applications’ logic, misconfigured resources, and flaws within their access control allow vulnerabilities.</p><p>Prevention:<br> Run regular audits of permissions and access.<br> Practice the rule of least privilege.<br> Keep all software components up-to-date.</p><p>6. Exploiting Outdated Software</p><p>Description: Exploit unpatched servers or applications that have known vulnerabilities to gain control.</p><p>Mechanism: Exploits from public vulnerability databases, such as the CVE database, are used to target outdated systems.</p><p>Prevention:<br> Periodically update and patch servers and applications.<br> Keep up with the disclosure of vulnerabilities affecting your software stack.</p><p>7. Poor Authentication Mechanisms</p><p>Description: Attackers bypass authentication through weak passwords, predictable tokens, or insecure authentication mechanisms.</p><p>Mechanism:<br> Credential stuffing: Using previously stolen credentials from past breaches,<br> Brute force: Guessing the credentials one after another.</p><p>Prevention:<br> Strong password policies and multi-factor authentication (MFA) need to be enforced.<br>Lock accounts after a certain number of failed attempts.<br> Utilize CAPTCHA to prevent automated attacks.</p><p>8. Malware Deployment</p><p>Description: An attacker injects malicious software or scripts into the server to perform unauthorized actions such as data exfiltration or system sabotage.</p><p>Mechanism:<br>Uploading backdoors or trojans via file upload vulnerabilities.<br> Planting ransomware to encrypt server data.</p><p>Prevention:<br> Scan uploaded files for malware.<br> Use secure upload mechanisms (e.g., limiting file types and size).<br>Deploy endpoint detection and response solutions.</p><p>9. Directory Traversal</p><p>Description: This attack leverages the vulnerabilities that would let the attacker access unauthorized directories or files on the server.</p><p>Mechanism: It works by manipulating the file path to gain access to a critical system file.<br> Example:././etc/passwd for accessing the password file in Linux servers.</p><p>Prevention:<br>Validate and sanitize file paths.<br> Configure the server to disallow access outside allowed directories.<br> Use chroot or containerization to isolate application environments.</p><p>Additional Security Best Practices:</p><p>Secure Configurations:<br> Disable unnecessary services and ports.<br>Use strong encryption for data in transit and at rest, such as HTTPS and TLS.</p><p>Access Control:<br> Implement robust role-based access control.<br> Avoid hardcoding sensitive credentials in code or configuration files.</p><p>Monitoring and Auditing:<br>Log all server activities and regularly review them.<br> Use intrusion detection and prevention systems (IDPS).</p><p>Web Application Firewalls (WAF):<br> Filter and monitor HTTP requests to block malicious traffic.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67d61d5c3956" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Basic understanding of the file based attacks, How to protect from it.]]></title>
            <link>https://medium.com/@srisabeshan271/basic-understanding-of-the-file-based-attacks-how-to-protect-from-it-6dbfb12d30c2?source=rss-82d7a2cef9ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/6dbfb12d30c2</guid>
            <dc:creator><![CDATA[whit3h473r]]></dc:creator>
            <pubDate>Mon, 09 Dec 2024 11:51:05 GMT</pubDate>
            <atom:updated>2024-12-09T11:51:05.774Z</atom:updated>
            <content:encoded><![CDATA[<p>An upload of files attack is a situation when an attacker takes advantage of some weak points of website or application file upload, which allows him to upload several malicious files. The attacker might store harmful code or scripts within uploaded files, which help execute unauthorized actions, compromise a server, or seize system control.<br>Common Objectives of Attackers in File Uploads:<br>1. Remote Code Execution (RCE): Uploading of scripts such as .php, .jsp to execute commands on the server.<br>2. Data Exfiltration: Embedding malware to steal sensitive data.<br>3. System Exploitation:*Uploading files that exploit vulnerabilities in the server.<br>4. Defacement: Uploading modified or malicious content to deface the website.<br>5. Phishing and Malware Distribution: Hosting malicious files on the server to deceive users.</p><p>How it Happens:<br>- No File Validation: The system does not check the file types, which enables executable files.<br>- Improper File Storage: The uploaded files are stored in URL accessible directories.<br>- Weak Authentication: Attackers bypass authentication or authorization and upload files.</p><p>Prevention Measures:<br>1. File Type Restrictions: Allow only specific, safe file types such as images like .jpg.<br>2. Content Scanning: Perform antivirus or malware scanning on uploaded files using appropriate tools.<br>3. Renaming Files:Change file names and extensions upon upload to prevent execution.<br>4. Directory Restrictions: Store files in non-executable directories.<br>5. Input Validation:Sanitize filenames and metadata to prevent injection attacks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6dbfb12d30c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Basics of blind SQLi]]></title>
            <link>https://medium.com/@srisabeshan271/basics-of-blind-sqli-547bed5d571e?source=rss-82d7a2cef9ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/547bed5d571e</guid>
            <dc:creator><![CDATA[whit3h473r]]></dc:creator>
            <pubDate>Sun, 08 Dec 2024 07:17:41 GMT</pubDate>
            <atom:updated>2024-12-08T07:17:41.039Z</atom:updated>
            <content:encoded><![CDATA[<p>Blind SQL Injection (Blind SQLi) is a type of SQL injection attack where an attacker cannot view the results of their injected queries directly. Instead, they infer information about the database based on indirect responses, such as error messages, page content changes, or response times.</p><p>There are two major types of blind SQLi:</p><p><strong>1. Boolean-Based Blind SQLi</strong></p><p>The attacker injects SQL payloads that return different results depending on a true or false condition.</p><p>· ‘ OR 1=1 — (True condition)</p><p>· ‘ OR 1=0 — (False condition)</p><p>If the page behavior changes, such as showing different content for true versus false, then it confirms the vulnerability.</p><p><strong>2. Time-Based Blind SQLi</strong></p><p>The attacker utilizes SQL queries that introduce time delays to infer database responses.</p><p>· ‘ OR IF(1=1, SLEEP(5), 0) —</p><p>This is done by noting that if the response time increases, it means the condition (1=1) was true.</p><p>Exploitation Goals:</p><p>Database details such as table names, column names, data.</p><p>Further attacks such as privilege escalation or sensitive data extraction.</p><p>Preventive Measures:</p><p>1. Parameterized queries — Utilize prepared statements.</p><p>2. Input validation and sanitization.</p><p>3. Web application firewalls (WAFs): to detect and block malicious payloads.</p><p>4. Security testing: perform regularly to identify and patch vulnerabilities.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=547bed5d571e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>