<?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 Siddhi Tandalekar on Medium]]></title>
        <description><![CDATA[Stories by Siddhi Tandalekar on Medium]]></description>
        <link>https://medium.com/@Siddhi.?source=rss-5eb97dcb3a5a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AnrLAdAOOf6dzYaAEmNCqA.png</url>
            <title>Stories by Siddhi Tandalekar on Medium</title>
            <link>https://medium.com/@Siddhi.?source=rss-5eb97dcb3a5a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:42:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Siddhi./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[Broken Access Control]]></title>
            <link>https://medium.com/@Siddhi./broken-access-control-993804d7df43?source=rss-5eb97dcb3a5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/993804d7df43</guid>
            <dc:creator><![CDATA[Siddhi Tandalekar]]></dc:creator>
            <pubDate>Wed, 06 Sep 2023 13:17:45 GMT</pubDate>
            <atom:updated>2023-09-06T13:17:45.690Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>Broken Access Control</em></strong> is when an attacker can gain unauthorized access to restricted information or systems. It has been <strong>#1</strong> in the <strong>OWASP</strong> List. Once this flaw is discovered, the consequences of a flawed access control scheme can be devastating. In addition to viewing unauthorized content, an attacker might be able to change or delete content, perform unauthorized functions, or even take over site administration.</p><p>Example of a broken access control vulnerability would be an application that doesn’t properly restrict access to certain functions based on a user’s role. For instance, an administrator account might have permission to add new users to the system, but a regular user account shouldn’t. However, if the application doesn’t restrict access to the function, a regular user could add new users to the system, potentially giving them administrator privileges.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/0*zYf8v0g0uI-2XIgu.png" /></figure><p><strong>Some BROKEN ACCESS CONTROL ATTACK METHODS</strong></p><ol><li><strong>Injection attacks in web application:</strong> By injecting malicious code into an application, attackers can bypass access controls and access sensitive information, perform unauthorized actions, and compromise the security and confidentiality of an organization’s data and systems.</li><li><strong>Cross-site scripting (XSS): </strong>XSS flaws occur when untrusted input is included in web page output. Attackers can exploit this to execute malicious scripts in the user’s browser, resulting in session hijacking, cookie theft or other malicious activity.</li><li><strong>Broken authentication and Session Management : </strong>Broken authentication and session management allows a cybercriminal to steal a user’s login data, or forge session data, such as cookies, to gain access to websites.</li><li><strong>Session Hijacking :</strong> If hackers steal your session ID, they can sign in by impersonating your identity. This is known as session hijacking. In a session hijacking attack, a hacker takes control of a user’s browsing session to gain access to their personal information and passwords.</li><li><strong>Brute Force Attacks :</strong>This type of attack involves repeatedly trying to guess a user’s password or other authentication credentials in order to gain access to their account.</li><li><strong>Forced Browsing :</strong> Forced browsing attacks include accessing unpublished web pages, confidential documents, or private user data through URL manipulation or Google dorking.</li><li><strong>API Exploitation :</strong> Exploiting vulnerabilities in API endpoints to gain unauthorized access, compromise data, disrupt services, or perform other malicious activities.</li></ol><p>The root cause of Broken Access Control is weak authentication and authorization mechanisms, allowing attackers to gain illegitimate privileges.</p><p><strong><em>PREVENTIONS FOR BROKEN ACCESS CONTROL ATTACK</em></strong></p><p>1.<strong> Continuous Inspection and Testing Access Control:</strong></p><p>Efficient continuous testing and inspecting the access control mechanism is an effective way to detect the newer vulnerabilities and correct them as soon as possible.</p><p>2.<strong> Deny Access By Default:</strong></p><p>Design <a href="https://www.geeksforgeeks.org/access-control-in-computer-network/">access control</a> in such a way that not everyone can get access to the resources and functionalities unless it is intended to be publicly accessible. You can apply <strong>JIT (Just-in-Time)</strong> access, which helps to remove the risks associated with standing privileges.</p><p>3.<strong> Enable Role-based Access Control:</strong></p><p>This is a widely used access control mechanism. According to this, users are given permissions based on their roles. Instead of identifying each user individually, users are assigned to a group of roles, this way the struggle of IT support and administration can be reduced, and operational efficiency will be maximized.</p><p>4. <strong>Enable Permission-Based Access Control:</strong></p><p>This is an access control method, where the authorization layer checks if the user has permission to access particular data or to perform a particular action, typically by checking if the user’s roles have this permission or not.</p><p>5. <strong>Enable Mandatory access control:</strong></p><p>It is a security method, that restricts the ability to access resources based on the sensitivity of the information, that the resource contains. This security policy can only be controlled by the administrator, regular users don’t have the ability to change that policy. Because of this centralized administration, it is considered to be very secure.</p><p>The <strong>conclusion</strong> is that broken access control is a <strong>critical issue</strong> that can <strong>compromise web application security</strong>. It occurs when web applications do not properly implement access control mechanisms and allow users to access resources they should not have access to.</p><p>THANK YOU !! I hope this is useful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=993804d7df43" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SQL Injection Attack]]></title>
            <link>https://medium.com/@Siddhi./sql-injection-attack-94f6893eef36?source=rss-5eb97dcb3a5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/94f6893eef36</guid>
            <dc:creator><![CDATA[Siddhi Tandalekar]]></dc:creator>
            <pubDate>Sun, 27 Aug 2023 15:02:57 GMT</pubDate>
            <atom:updated>2023-08-27T15:02:57.022Z</atom:updated>
            <content:encoded><![CDATA[<p>SQL Injection attack is a code injection technique which is used by an attacker to manipulate a web application’s database queries.</p><p>It’s done by injecting a SQL code or query(malicious) into input fields. Attackers can execute an unauthorized command and potentially gain access to the sensitive data: customer information, personal data, trade secrets, intellectual property, and many more.</p><p>SQL injection attacks primarily target web applications that use SEQUEL (Structured English QUERY Language) databases such as MySQL, Oracle, SQL Server, etc.</p><p><strong>HOW SQL Injection Attack WORKS ?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*7cdTAyZGaF7zNNOk.png" /></figure><p>SQL queries are used to retrieve or update data into a database. An attacker exploits vulnerable input fields by injecting malicious SQL code which alters the intended behavior of the query. An attacker first study the target database to understand its structure and behavior then they craft a SQL query the server interprets as a legitimate command [for example : OR 1=1(This condition is always True)] this is a query’s input field wherein an attacker bypasses authentication and gain unauthorized access.</p><p>SQL Injection Attack can also be used to delete data, manipulate records, or retrieve information from multiple database tables using techniques like Error-based Injection, Union-based Injection or Inferential SQL Injection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/583/1*8XDN8eEW2WhlRbPhsPDamA.png" /></figure><p><strong>How to PREVENT SQL Injection Attack ?</strong></p><p>When designing database operations, the use of prepared statements with parameterized queries and stored procedures will help to prevent SQLi attacks.</p><p><strong><em>Few Key Methods to prevent SQL Injection Attack</em></strong></p><ol><li><strong>Filter database inputs</strong> : Detect and filter out malicious code from user inputs.</li><li><strong>Restrict database code </strong>: Prevent unintended database queries and exploration by limiting database procedures and code.</li><li><strong>Restrict database access</strong> : Prevent unauthorized data access, exfiltration, or deletion through access control restrictions.</li><li><strong>Maintain application and database</strong> : Keep databases fully patched and updated. Upgrade when possible.</li><li><strong>Monitor application and database inputs and communications</strong> : Monitor communication to detect and block malicious SQLi attempts.</li></ol><p>THANK YOY !!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94f6893eef36" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>