<?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 Ravitej Bandlekar on Medium]]></title>
        <description><![CDATA[Stories by Ravitej Bandlekar on Medium]]></description>
        <link>https://medium.com/@ravitejbandlekar?source=rss-3d7b75a5b260------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*p1H8ltfZ39N8A9ExhDtqDQ.jpeg</url>
            <title>Stories by Ravitej Bandlekar on Medium</title>
            <link>https://medium.com/@ravitejbandlekar?source=rss-3d7b75a5b260------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:25:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ravitejbandlekar/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[Deconstructing Phishing Attacks and Email Analysis”]]></title>
            <link>https://ravitejbandlekar.medium.com/deconstructing-phishing-attacks-and-email-analysis-efcb54e8b707?source=rss-3d7b75a5b260------2</link>
            <guid isPermaLink="false">https://medium.com/p/efcb54e8b707</guid>
            <category><![CDATA[phishing]]></category>
            <category><![CDATA[email]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[network-security]]></category>
            <dc:creator><![CDATA[Ravitej Bandlekar]]></dc:creator>
            <pubDate>Tue, 07 Nov 2023 11:05:23 GMT</pubDate>
            <atom:updated>2023-11-07T11:05:23.698Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hEPspBgALhgcTbJ0.jpeg" /><figcaption>Source: vipre.com</figcaption></figure><p>Spam and phishing are prevalent forms of social engineering attacks, with a specific focus on email as a common attack vector. Spam emails, despite their origins dating back to 1978, continue to inundate our inboxes, often bypassing filters and security measures. On the other hand, phishing is a grave concern that organizations must defend against. Even with robust security strategies in place, the actions of a single unwitting user can provide attackers with a foothold in the corporate network, typically through clicking on malicious links or downloading harmful attachments.</p><p>While numerous security products aim to combat spam and phishing, the reality is that some of these malicious emails can still slip through the cracks. As a Security Analyst, it becomes crucial to analyze these emails when they do breach the defenses to determine their nature, whether they are malicious or benign. This analysis is not only for immediate mitigation but also to gather essential information about the email, which can be used to enhance security products and prevent similar malicious emails from reaching users’ inboxes in the future. In the constant battle against cyber threats, the ability to scrutinize and understand these email attacks is a vital component of maintaining a secure corporate environment.</p><p>Email phishing stands as a primary catalyst for various cyber-attacks. In this deceptive tactic, unsuspecting users are lured into opening and interacting with seemingly authentic files and links sent via email. Consequently, cyber adversaries gain access to their victims’ systems, introducing malware, exfiltrating sensitive credentials and personal information, and engaging in activities like financial fraud and launching ransomware attacks.</p><p>Malicious emails can be classified into several categories:</p><ol><li><strong>Spam</strong>: These are unsolicited and widespread junk emails sent to a large number of recipients. A more malicious form of spam is known as “MalSpam.”</li><li><strong>Phishing</strong>: Phishing emails impersonate trusted entities to trick individuals into revealing sensitive information.</li><li><strong>Spear Phishing</strong>: Going a step further, spear phishing targets specific individuals or organizations, aiming to acquire sensitive data.</li><li><strong>Whaling</strong>: Whaling is a variation of spear phishing, focusing on high-level C-suite individuals (such as CEOs and CFOs) with the same objective.</li><li><strong>Smishing</strong>: Smishing adapts phishing for mobile devices, using tailored text messages to target mobile users.</li><li><strong>Vishing</strong>: Vishing is similar to smishing but relies on voice calls, rather than text messages, for social engineering attacks.</li></ol><p>These diverse forms of malicious email attacks vary in their level of specificity, all with the common goal of deceiving recipients and extracting sensitive information.</p><p>Phishing emails commonly share the following characteristics:</p><ul><li><strong>Email Spoofing:</strong> They often disguise the sender’s email name/address to mimic a trusted source.</li><li><strong>Urgent Language:</strong> These emails employ a sense of urgency or keywords like “Invoice” or “Suspended” in the subject line or body.</li><li><strong>Mimicked Design:</strong> The HTML email body is crafted to resemble a reputable entity, such as Amazon.</li><li><strong>Poor Formatting:</strong> Contrary to the previous point, some phishing emails exhibit poorly formatted or poorly written content.</li><li><strong>Generic Content:</strong> They use generic salutations like “Dear Sir/Madam.”</li><li><strong>Hidden Hyperlinks: </strong>Phishing emails frequently contain hyperlinks, sometimes using URL shortening services to obscure their true origin and URL shortening services.</li><li><strong>Malicious Attachments:</strong> They may include harmful attachments posing as legitimate documents.</li></ul><h4>Email Security:</h4><p>Email authentication and security techniques such as SPF, DKIM, and DMARC are used to combat email spoofing, phishing, and other email-related risks. These techniques operate together to ensure the authenticity and dependability of email messages.</p><p><strong>SPF (Sender Policy Framework)</strong></p><ul><li>SPF is an email authentication standard developed to combat email spoofing by allowing domain owners to indicate which mail servers are authorized to send emails on their behalf.</li><li>It works by establishing a DNS record (TXT record) for the sender’s domain that lists the IP addresses or hostnames of authorized email servers.</li><li>When an email is received, the recipient’s email server verifies the SPF record of the sender’s domain to ensure that the sending server is authorized to send emails on behalf of that domain. If the verification fails, the email may be marked as suspicious or rejected.</li></ul><p><strong>DKIM (DomainKeys Identified Mail)</strong></p><ul><li>DKIM is another email authentication mechanism that employs cryptographic signatures to validate the integrity and authenticity of email communications.</li><li>When an email is sent, the sender mail server signs it with a private key and adds a DKIM signature to the message header. The sender’s DNS records contain the public key necessary for signature verification.</li><li>The sender’s public key can be used by the recipient’s email server to validate the DKIM signature and ensure that the email was not tampered with during transit.</li></ul><p><strong>DMARC (Domain-based Message Authentication, Reporting, and Conformance)</strong></p><ul><li>DMARC is a policy framework that extends SPF and DKIM to provide further protection against email spoofing and phishing.</li><li>A domain owner can use DMARC to define which email authentication procedures (SPF and/or DKIM) must be fulfilled for emails coming from their domain, as well as the actions to be performed if these checks fail (e.g., rejecting or quarantining the email).</li><li>DMARC also includes reporting capabilities that offer feedback on the status of emails sent from the domain, allowing domain owners to monitor and fine-tune their email authentication rules.</li></ul><h4>Primary analysis:</h4><p>Prior to delving into the subject, it’s essential to grasp that an email comprises two distinct components:</p><ul><li>The email header, which contains information about the email, including details about the email servers through which it passed.</li></ul><p>An email header, also known as an internet header, is a set of metadata that comes with every email. It contains various details such as the sender’s and receiver’s information, the path the email took, timestamps, and more. Email service providers and mailbox systems use these headers to verify the legitimacy of email senders and correctly place emails in the recipient’s inbox.</p><p>The content of email metadata is automatically generated, and while there are established standards for what it should include, there are no restrictions on what additional information a mail server can include in it.</p><p>Here is an extra source from Media Temple that provides guidance on how to examine email headers:</p><p>You can access this resource at the following link: <a href="https://mediatemple.net/community/products/all/204643950/understanding-an-email-header">https://mediatemple.net/community/products/all/204643950/understanding-an-email-header</a></p><ul><li>The email body, which encompasses the text and potentially HTML-formatted content of the message.</li></ul><h4>What specific signs or elements do we seek when evaluating a potentially harmful email?</h4><p>A. Which social media platform or well-known website is the attacker attempting to impersonate in the email?</p><p>B. What is the subject of the email, and do you find it to be suspicious?</p><p>C. What is the email address of the sender?</p><p>D. What is the email address of the recipient?</p><p>E. What is the return-path email from the header?</p><p>F. What is the IP address of origin?</p><ul><li>What is the domain listed for the IP address, and can you provide the customer name associated with it?</li><li>Reverse lookup of the sender IP address.</li><li>Utilize online tools like Cisco Talos, VirusTotal, IBM X-Force, and IPvoid to obtain the information mentioned above.</li></ul><p><a href="https://talosintelligence.com/reputation_center">https://talosintelligence.com/reputation_center</a><br><a href="https://exchange.xforce.ibmcloud.com/">https://exchange.xforce.ibmcloud.com/</a></p><p><a href="https://www.virustotal.com/gui/home/upload">https://www.virustotal.com/gui/home/upload</a></p><p>G. Are there any files attached to the email?</p><ul><li>What is the name of the attachment?</li><li>What is the file extension of the attachment?</li></ul><p>H. Do you see any embedded hyperlinks, such as those containing the text “Click here,” in the email?</p><ul><li>What is the URI for the blocked image or embedded hyperlink, as found in the email header?</li><li>Once you’ve located it, you can utilize online threat intelligence tools to uncover reputation details, determine the domain it redirects to, and identify the IP address associated with the hyperlink.</li><li>What is the root domain of the URL?</li></ul><p>I. What technique was used to persuade the victim to not ignore the email and act swiftly?</p><p>J. What is the SPF record for the domain?</p><p>F. What is the DMARC record for the domain?</p><h4>Tools Used for Analysis:</h4><p>Header analysis:</p><ol><li><strong>Messageheader from google</strong></li></ol><p><a href="https://toolbox.googleapps.com/apps/messageheader/analyzeheader">https://toolbox.googleapps.com/apps/messageheader/analyzeheader</a></p><p><a href="https://mha.azurewebsites.net/">2. Message Header Analyzer (mha.azurewebsites.net)</a></p><p>3. <a href="https://mailheader.org/">https://mailheader.org/</a></p><p>IP Reputation and information:</p><ol><li><a href="https://ipinfo.io/">https://ipinfo.io/</a></li><li><a href="https://talosintelligence.com/reputation">https://talosintelligence.com/reputation</a></li><li><a href="https://exchange.xforce.ibmcloud.com/">https://exchange.xforce.ibmcloud.com/</a></li><li><a href="https://www.virustotal.com/gui/">https://www.virustotal.com/gui/</a></li><li><a href="https://www.ipvoid.com/">https://www.ipvoid.com/</a></li></ol><p>URL analysis:</p><ol><li><a href="https://urlscan.io/">https://urlscan.io/</a></li><li><a href="https://www.wannabrowser.net/">https://www.wannabrowser.net/</a></li><li><a href="https://www.url2png.com/">https://www.url2png.com/</a></li></ol><p>URL extractor:</p><ol><li><a href="https://www.convertcsv.com/url-extractor.htm">https://www.convertcsv.com/url-extractor.htm</a></li><li><a href="https://gchq.github.io/CyberChef/">https://gchq.github.io/CyberChef/</a></li></ol><p>File Reputation:</p><ol><li><a href="https://talosintelligence.com/talos_file_reputation">https://talosintelligence.com/talos_file_reputation</a></li><li><a href="https://www.virustotal.com/gui/">https://www.virustotal.com/gui/</a></li><li><a href="https://www.reversinglabs.com/">https://www.reversinglabs.com/</a></li></ol><p>Malware Sandbox:</p><ol><li><a href="https://app.any.run/">https://app.any.run/</a></li><li><a href="https://www.hybrid-analysis.com/">https://www.hybrid-analysis.com/</a></li><li><a href="https://www.joesecurity.org/">https://www.joesecurity.org/</a></li></ol><p>Phishing analysis:</p><p>A tool that will help with automated phishing analysis is <a href="https://www.phishtool.com/">PhishTool</a>.<br>https://www.phishtool.com/</p><p>Additional tools:</p><ul><li><a href="https://mxtoolbox.com/">https://mxtoolbox.com/</a></li><li><a href="https://phishtank.com/?">https://phishtank.com/?</a></li><li><a href="https://www.spamhaus.org/">https://www.spamhaus.org/</a></li></ul><p>To gain a more practical understanding of analyzing phishing emails, you can explore the rooms available on TryHackMe that cover this topic. These rooms will provide hands-on experience and guidance for dissecting and assessing phishing emails.</p><ul><li><a href="https://tryhackme.com/room/threatinteltools">Threat Intelligence Tools</a></li><li><a href="https://tryhackme.com/room/phishingemails1tryoe">Phishing Analysis Fundamentals</a></li><li><a href="https://tryhackme.com/room/phishingemails2rytmuv">Phishing Emails in Action</a></li></ul><p>Let’s connect?</p><p>LinkedIn: <a href="http://www.linkedin.com/in/ravitejmbandlekar">www.linkedin.com/in/ravitejmbandlekar</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efcb54e8b707" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decoding The Web Application Protection: Understanding Attacker Handling]]></title>
            <link>https://ravitejbandlekar.medium.com/decoding-the-web-application-protection-understanding-attacker-handling-120be2de16b5?source=rss-3d7b75a5b260------2</link>
            <guid isPermaLink="false">https://medium.com/p/120be2de16b5</guid>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Ravitej Bandlekar]]></dc:creator>
            <pubDate>Wed, 18 Oct 2023 13:46:21 GMT</pubDate>
            <atom:updated>2023-10-18T13:46:21.633Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/780/0*W_MtgfJHkuLiLIwZ.png" /><figcaption>Source: <a href="http://www.safeaeon.com/">www.safeaeon.com</a></figcaption></figure><p>When creating an application, especially when security is a significant concern, it’s vital to acknowledge the likelihood of it becoming a prime target for determined and highly skilled attackers. This highlights the necessity of making security an inherent part of the development process and adopting a proactive approach in uncovering and addressing vulnerabilities. It’s a reminder that security should be integrated from the outset and that ongoing monitoring and updates are essential to safeguard against evolving threats from cybercriminals who possess both the dedication and expertise to exploit any potential weaknesses in the application.</p><p>One of the primary roles of an application’s security mechanisms is to effectively manage and respond to attacks in a controlled manner. These security measures typically involve a combination of defensive and offensive strategies aimed at minimizing the attacker’s success and providing the application’s administrators with the necessary alerts and evidence regarding the attack. Strategies employed to handle attackers commonly encompass the following:</p><h4>Handling Errors</h4><p>While developers strive to thoroughly validate user input, they can’t predict all potential errors, and some unexpected issues are nearly inevitable. Errors stemming from typical user actions are typically discovered and addressed during testing before the application goes live. However, it’s challenging to anticipate all the ways malicious users may exploit the application, so errors are to be expected during attacks. A vital defense is the application’s ability to gracefully handle unforeseen errors, either by recovering from them or presenting appropriate error messages. In a production environment, it’s crucial not to divulge system-generated messages or debug information, as detailed error messages can aid malicious users and faulty error handling might expose sensitive data, creating a vulnerability for data theft. Most web development languages offer robust error-handling capabilities, such as try-catch blocks and checked exceptions. Application code should make extensive use of these constructs to effectively catch and manage errors. Furthermore, application servers can be configured to handle unanticipated errors in customized ways. Effective error handling often integrates with the application’s logging system to record valuable debug information about unforeseen errors, which can be used to enhance the application’s defenses.</p><h4>Maintaining Audit Logs</h4><p>Audit logs play a critical role in investigating intrusion attempts within security-sensitive applications, shedding light on incident details, exploited vulnerabilities, unauthorized access, and potentially the identity of the intruder. Security-focused applications routinely log specific key events, including activities related to authentication, significant transactions like payments, blocked access attempts, and requests containing known attack patterns. In some highly secure applications such as online banking systems, every client request is extensively logged for forensic analysis.</p><p>Effective audit logs should contain event timestamps, the source IP address, and user account details if authenticated. Protecting these logs from unauthorized access is of utmost importance. A recommended practice is to store them on a separate system that only accepts updates from the main application. In some situations, logs may be written to write-once media to ensure their integrity, even in the event of a security breach.</p><p>It’s essential to be aware that poorly protected audit logs can become a valuable resource for attackers, potentially exposing sensitive information like session tokens and request parameters.</p><h4>Alerting Administrators</h4><p>Audit logs serve the purpose of looking back and investigating intrusion attempts, potentially leading to legal action against the culprits. However, when dealing with security, immediate actions in response to ongoing attacks are often essential. Taking swift defensive measures can minimize the practical impact of a successful intrusion.</p><p>In the realm of real-time security, alert systems must find a balance between reporting genuine attacks effectively and not overwhelming administrators with excessive alerts. Well-designed alert systems rely on various factors to identify determined attacks and consolidate related events into a single alert whenever feasible. The kinds of unusual events that alert systems monitor include anomalies in usage, like a high volume of requests from a single source, unusual business activities such as atypical fund transfers, requests containing known attack patterns, and unauthorized modifications to concealed data.</p><p>Commercial off-the-shelf application firewalls and intrusion detection products offer some of these functionalities. They employ a mix of signature- and anomaly-based rules to detect and block malicious application usage while alerting administrators. Nevertheless, these products have their limitations due to the unique nature of each web application. While they excel at spotting obvious attacks, they may struggle with more subtle, application-specific threats.</p><p>In the case of security-critical applications, the most effective real-time alerting seamlessly integrates with the application’s input validation and control mechanisms. This approach empowers the application to identify and respond to malicious activity by closely aligning with the specific logic and user behavior expectations of that application. This approach substantially reduces the risk of false positives compared to generic off-the-shelf solutions.</p><h4>Reacting to Attacks</h4><p>Security-critical applications often incorporate built-in mechanisms to proactively defend against potentially malicious users. Since each application has its unique characteristics, real-world attacks frequently involve systematic probing for vulnerabilities, where attackers submit multiple requests with crafted input to exploit common vulnerabilities. Effective input validation can identify and block many of these malicious requests, but it’s prudent to assume that some bypasses may exist, and undiscovered vulnerabilities remain.</p><p>Hence, some applications automatically take defensive actions to disrupt the activities of systematic attackers. For instance, they might respond slowly to an attacker’s requests or terminate the attacker’s session, forcing them to log in or perform additional steps before continuing the attack. While these measures may not deter the most patient and determined attackers, they effectively discourage casual attackers and provide administrators with extra time to monitor the situation and take more substantial action if necessary.</p><p>In the domain of application security, it is essential to be proactive and ready for the constant threat posed by skilled attackers. Prioritizing strong security measures in the initial application design is paramount, along with the capability to respond effectively to security breaches. Audit logs serve a crucial role in post-incident investigations, shedding light on intrusion attempts and possible legal actions. Immediate responses, like blocking attackers and potentially taking the application offline, are vital. To strike a balance between alerting and avoiding information overload, alert mechanisms need to discern genuine threats from background noise and detect patterns indicative of malicious behavior. Moreover, automated defenses can disrupt systematic attackers, while tailoring real-time alerting to the application’s unique logic and user behavior expectations forms a robust security strategy. In summary, security must be an inherent component of the application development process, involving a combination of proactive, reactive, and customized security measures.</p><p><strong>Reference:</strong></p><p>The web application hacker’s handbook- Finding and exploiting security flaws.</p><blockquote><em>Let’s connect?</em></blockquote><blockquote><em>LinkedIn: </em><a href="http://www.linkedin.com/in/ravitejmbandlekar"><em>www.linkedin.com/in/ravitejmbandlekar</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=120be2de16b5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decoding The Web Application Protection: Understanding Input Handling]]></title>
            <link>https://ravitejbandlekar.medium.com/decoding-the-web-application-protection-understanding-input-handling-7a2db2fd7d56?source=rss-3d7b75a5b260------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a2db2fd7d56</guid>
            <category><![CDATA[web-app-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[network-security]]></category>
            <dc:creator><![CDATA[Ravitej Bandlekar]]></dc:creator>
            <pubDate>Sat, 16 Sep 2023 09:28:50 GMT</pubDate>
            <atom:updated>2023-09-16T09:28:50.290Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5WQ-61WxEzNtoO9e.png" /><figcaption>Source: <a href="https://www.thinklogic.com/">https://www.thinklogic.com/</a></figcaption></figure><p>Numerous attacks targeting web applications revolve around the submission of unconventional input, meticulously designed to trigger unintended behaviors within the application. Consequently, a fundamental necessity for bolstering an application’s security lies in its ability to process user input safely and securely.</p><p>Vulnerabilities stemming from input can emerge in various parts of an application’s features, spanning across a wide range of commonly used technologies. “Input validation” is frequently touted as the essential safeguard against such attacks. Nevertheless, it’s important to recognize that there isn’t a one-size-fits-all protective measure that can be universally applied, and defending against malicious input is often more complex than it may initially appear.</p><p>Let us consider an application’s input validation checks with different use cases.</p><blockquote><strong>Use Case 1:</strong></blockquote><p>Gather the user’s postal address for various reasons, such as sending items or confirming their whereabouts.</p><p><strong>Checks:</strong></p><p><strong>Required Field-</strong>Ensure that the “Address” field is mandatory, meaning users must provide their address during registration.</p><p><strong>Maximum Length- </strong>Establish a character limit cap (e.g., 100 characters) for the address input to avoid excessively lengthy entries that could potentially disrupt the structure of the database or user interface.</p><p><strong>Valid Characters- </strong>Permit only legitimate characters in the address field, typically including alphanumeric characters, spaces, commas, and specific special characters such as hyphens and periods.</p><p><strong>Address Format-</strong> Make certain that the address adheres to a standardized format appropriate for your target region or country. This could involve mandating that addresses incorporate expected elements such as street numbers, street names, city names, and postal/ZIP codes in the prescribed format.</p><p><strong>Avoid HTML/Script Tags- </strong>Incorporate input sanitization measures to safeguard against the inclusion of HTML or script tags within the address field, as these elements may pose a risk for potential cross-site scripting (XSS) attacks.</p><blockquote><strong>Use Case 2:</strong></blockquote><p>Ensure that the user provides a valid email address during registration.</p><p><strong>Check:</strong></p><p>Verify that the input contains the “@” symbol and a valid domain name.</p><p>The various approaches:</p><h4><strong>1. Reject known bad:</strong></h4><p>This approach involves maintaining a blacklist or deny list containing known strings, characters, or patterns commonly used in various types of attacks. These entries are typically gathered from threat intelligence sources as Indicators of Compromise (IOCs). The technique operates by prohibiting any input or entities that match the items in the blacklist while permitting everything else to proceed without restriction.</p><p>In General this is termed as the least effective approach for validating input which has two reasons to support.</p><ul><li>Vulnerabilities within an application can be exploited through numerous avenues, employing a diverse range of input methods, which may include encoding or diverse representations. Consequently, a blacklist may inadvertently exclude certain input patterns that can be leveraged to compromise the application’s security.</li><li>Exploitation tactics, techniques, and procedures are rapidly evolving. As a result, it’s improbable that existing blocklists can effectively prevent the exploitation of known vulnerability categories through new and innovative methods.</li></ul><p>Examples:</p><ul><li>SQL Injection Attempt:</li></ul><p>Input: &#39;; DROP TABLE Users--</p><ul><li>Explanation: This input attempts to execute a malicious SQL injection attack by adding a semicolon followed by a SQL command to delete the “Users” table.</li><li>Cross-Site Scripting (XSS) Payload:</li></ul><p>Input: &lt;script&gt;alert(&#39;XSS Attack&#39;);&lt;/script&gt;</p><ul><li>Explanation: This input contains a JavaScript script tag, which can be used to execute malicious scripts on the user’s browser.</li><li>Path Traversal Attempt:</li></ul><p>Input: ../../../../../etc/passwd</p><ul><li>Explanation: This input tries to perform a directory traversal attack by attempting to access sensitive files on the server, such as the password file.</li><li>Command Injection Attempt:</li></ul><p>Input: ; ls -la</p><ul><li>Explanation: This input aims to execute arbitrary commands on the server by appending a semicolon followed by a system command (ls -la in this case).</li></ul><h4><strong>2. Accept known Good:</strong></h4><p>This method entails using a whitelist, which consists of specific literal strings, patterns, or criteria that are recognized as only matching benign inputs. The validation process permits data that aligns with the whitelist while rejecting any other inputs.</p><p>For an instance: Prior to querying the database for a requested product code, the application may perform validation to confirm that the code comprises precisely six characters and contains only alphanumeric characters. Considering the subsequent processing of the product code, developers are confident that input meeting these criteria will not pose any potential issues.</p><p>Another example: Before processing a user’s payment information, the application may validate that the credit card number provided is 16 digits long and contains only numerical digits (0–9). Given the subsequent payment processing steps, developers are assured that input adhering to these criteria will not lead to any issues or errors.</p><p>While a whitelist approach is highly effective in handling potentially malicious input, it’s not a universal solution. When meticulously constructed, a whitelist prevents attackers from using crafted input to disrupt an application’s behavior. However, in many cases, applications must accept data that doesn’t conform to predefined criteria. For example, names with apostrophes or hyphens can be legitimate but also pose database security risks. There are situations where the application needs to accommodate such data, making the whitelist approach not suitable for all scenarios.</p><h4>Sanitization</h4><p>This approach involves recognizing that there are situations where it’s necessary to accept data that may not be inherently safe and then taking steps to make it safe. This is achieved through sanitization techniques, which can involve removing potentially harmful characters, retaining only known safe elements, or appropriately encoding and escaping the data before proceeding with further processing.</p><p>This method is widely effective in numerous scenarios and can be considered a comprehensive solution to the issue of handling malicious input. For instance, a common defense against cross-site scripting involves the HTML encoding of potentially harmful characters before they are incorporated into the application’s web pages.</p><h4>Safe Data Handling</h4><p>Vulnerabilities in web applications often stem from insecure handling of user-supplied data. To address these vulnerabilities, it’s essential not just to validate user input but also to guarantee that subsequent data processing follows secure protocols. In specific instances, secure programming methods can supplant conventional practices to thwart attacks. For instance, utilizing parameterized queries when communicating with databases can protect against SQL injection attacks. Similarly, in different scenarios, application functionality can be structured to sidestep inherently risky practices, such as passing user input directly to an operating system command interpreter.</p><h4>Semantic Checks</h4><p>In certain cases, malicious input submitted by threat actors can appear identical to input from non-malicious users, making it challenging to discern the difference based solely on syntax or structure. The distinguishing factor lies in the context in which the input is provided. For instance, an attacker might attempt to access someone else’s bank account by altering an account number sent through a hidden form field. Conventional syntactic validation alone cannot distinguish between the legitimate user’s data and the attacker’s input. To thwart unauthorized access, the application must validate that the submitted account number actually belongs to the user who is making the submission.</p><p>Let’s consider an online voting system as another example within the same context. A threat actor might submit a vote that syntactically matches a legitimate user’s vote, making it difficult to distinguish between the two based on syntax alone. However, the malicious aspect lies in the intent — the attacker may want to manipulate the election results by casting multiple votes.</p><p>To prevent this type of fraudulent activity, the application must validate not just the syntax of the vote but also the context in which it is submitted. This could involve tracking unique identifiers for each voter, checking for patterns of repeated votes, and employing additional security measures like CAPTCHA tests or voter authentication to ensure that each vote is cast by an eligible and legitimate user.</p><p><strong>Reference:</strong></p><p>The web application hacker’s handbook- Finding and exploiting security flaws.</p><blockquote><em>Let’s connect?</em></blockquote><blockquote><em>LinkedIn: </em><a href="http://www.linkedin.com/in/ravitejmbandlekar"><em>www.linkedin.com/in/ravitejmbandlekar</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a2db2fd7d56" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decoding The Web Application Protection: Understanding Authentication, Session Management, and…]]></title>
            <link>https://ravitejbandlekar.medium.com/decoding-the-web-application-protection-understanding-authentication-session-management-and-23b02ddf1835?source=rss-3d7b75a5b260------2</link>
            <guid isPermaLink="false">https://medium.com/p/23b02ddf1835</guid>
            <category><![CDATA[web-app-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[network-security]]></category>
            <dc:creator><![CDATA[Ravitej Bandlekar]]></dc:creator>
            <pubDate>Sat, 26 Aug 2023 21:09:15 GMT</pubDate>
            <atom:updated>2023-08-26T21:09:15.077Z</atom:updated>
            <content:encoded><![CDATA[<h3>Decoding The Web Application Protection: Understanding Authentication, Session Management, and Access Control</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CTd1CAZ5mFna_Se4.jpg" /><figcaption>Source: <a href="https://www.strongdm.com/">https://www.strongdm.com/</a></figcaption></figure><p>In our previous blog post, we laid the foundation by exploring the basics of essential web application defensive mechanisms. Now, it’s time to take the next step. In this article, we’re diving deeper into the core defensive mechanisms that form the backbone of robust web security.</p><p><a href="https://ravitejbandlekar.medium.com/decoding-web-application-protection-essential-defense-mechanisms-3580f40e6d29">Decoding Web Application Protection: Essential Defense Mechanisms</a></p><p>We can categorize the fundamental defensive mechanisms into three distinct parts.</p><p>A. Handling User Access</p><p>B. Handling User Input</p><p>C. Handling Attacker</p><h3>Handling User Access</h3><p>The primary objective of any virtual application should be the ability to effectively manage user access to its data and functionality. These user categories encompass anonymous users, regular authenticated users, and administrative users. It’s evident that various user types hold distinct permissions to access the web application’s data.</p><p>For instance, let’s consider the scenario of a collaborative document editing platform. Different users, such as authors and reviewers, require varying levels of access. An author can edit and revise a document, while a reviewer might have the privilege to suggest changes. This stratification of user roles ensures a controlled and secure environment, enhancing the overall user experience.</p><p>Most of the web application handle access using a trio of interrelated security mechanisms:</p><ul><li>Authentication</li><li>Session Management</li><li>Access Control</li></ul><p>Each of these mechanisms represents a significant segment of an application’s potential points of vulnerability. They are interconnected and collectively contribute to robust security, but paradoxically, they could also be perceived as the most fragile element in the chain. A flaw in any individual component could potentially grant malicious actors the means to circumvent defenses and gain unauthorized access to the application, thereby compromising both its functionality and data.</p><h4>Authentication</h4><p>Authentication is a fundamental method for managing user access. It ensures that a user is truly who they claim to be. Without authentication, applications would treat all users as anonymous, implying a minimal level of trust.</p><p>Most commonly used applications utilize authentication processes where a provided username and password combination is checked to grant users access to the application’s features and data. For applications focused on security, extra layers of protection like Multi-Factor Authentication (MFA) and smartcards are implemented. Furthermore, these authentication methods often come with additional functions like self-registration, account recovery, and the ability to change passwords.</p><p>While the concept of authentication, which is simply verifying the identity of a user, might appear simple on the surface, the actual mechanisms and systems put in place to achieve this are often quite complex. These mechanisms are designed to ensure that users are who they claim to be before granting them access to a system, application, or data. However, despite their apparent simplicity, these authentication mechanisms can suffer from a variety of issues that arise from both their design and how they are implemented.</p><ul><li>Design Flaws: The process of designing and constructing authentication systems can lead to inherent vulnerabilities. Design flaws may arise from not anticipating specific types of attacks or failing to account for all possible scenarios. Malicious actors frequently take advantage of these weak points in the design to illicitly access systems.</li><li>Implementation Errors: Even when an authentication method is meticulously planned, mistakes can emerge during the actual implementation. Errors in coding, configurations, or the integration of different systems can inadvertently introduce vulnerabilities.</li><li>Inadequate Security Measures: At times, authentication systems may not encompass essential security measures to defend against contemporary threats. For example, depending solely on passwords without incorporating supplementary security layers like Multi-Factor Authentication (MFA) can render systems more prone to breaches.</li><li>Evolving Threat Landscape: The techniques employed by malicious individuals to circumvent authentication are continually changing. What might have provided security a few years back could now be susceptible due to the emergence of new attack methods.</li><li>Human Factors: Users might not follow best practices when it comes to choosing strong passwords, keeping them safe, or practicing caution while sharing personal information. This human aspect can undermine even the strongest authentication systems.</li><li>Insufficient Updates and Maintenance: Security weaknesses could be identified after an authentication system is put into operation. If the system doesn’t undergo consistent updates and maintenance, these vulnerabilities might linger without being resolved, exposing the system to potential attacks.</li><li>Social Engineering: Adversaries frequently leverage human psychology to manipulate people into divulging their authentication credentials. This manipulation can take various forms, such as phishing emails or impersonation tactics.</li><li>Complexity of Integration: Large systems often have various components and services that need to work together seamlessly. This complexity can introduce points of failure or vulnerabilities if not managed properly.</li></ul><p>The interplay of these elements contributes to the diverse array of weaknesses that can be present in authentication mechanisms. To counter these challenges, security experts remain engaged in a continuous effort to pinpoint and resolve vulnerabilities, enhance authentication protocols, and educate users on the optimal strategies for protecting their credentials.</p><p>Please review this article, which provides additional insights into the concept of authentication.</p><p><a href="https://ravitejbandlekar.medium.com/beyond-the-lock-and-key-insights-into-cryptology-34767aa07a61">Beyond the Lock and Key: Insights into Cryptology</a></p><h4>Session Management</h4><p>After successfully authenticating a user to a web application, the subsequent task in managing user access involves session management. This concept comes into play when an authenticated user interacts with resources they are authorized to access. This interaction generates a substantial amount of traffic between the web application server and the user’s browser simultaneously. The web server might be handling numerous requests and responses concurrently, catering to both authenticated and non-authenticated users.</p><p>To ensure efficient access control, the application requires a method to distinguish and handle the sequence of requests originating from individual users. Virtually all applications address this necessity by establishing a session for each user and providing a token that serves as the identifier for that session. The session consists of a collection of data structures stored on the server, which monitor the user’s ongoing interaction with the application. The token, a distinct string, is used by the application to correlate with the specific session.</p><p>Ordinarily, HTTP cookies are the conventional means of transmitting these session tokens, although some applications employ hidden form fields or include the token in the URL query string. Ideally, if a user remains inactive for a specific duration, the session expires automatically.</p><p>The process described above, involving session management and the issuance of session tokens, can inadvertently become an attack surface if not properly implemented and secured. Attackers might exploit vulnerabilities in this system to gain unauthorized access or manipulate user sessions. Here’s how:</p><ul><li><strong>Session Hijacking/Session Fixation: </strong>Insufficiently safeguarded session tokens can be intercepted by attackers, enabling them to impersonate authenticated users. This could even lead to attackers compelling users to adopt a particular session (session fixation) and subsequently exploiting the associated privileges.</li><li><strong>Session Prediction:</strong> Should session tokens be generated predictably, malicious actors can deduce or anticipate valid tokens, thereby obtaining unauthorized entry to user accounts.</li><li><strong>Session Sniffing:</strong> In the event that session tokens are transmitted without encryption, attackers have the opportunity to intercept network traffic and abscond with these tokens. This can result in them obtaining unauthorized access to user accounts.</li><li><strong>Cross-Site Scripting (XSS):</strong> If an application is vulnerable to XSS attacks, attackers can inject malicious scripts that steal session tokens from users’ browsers, leading to unauthorized access.</li><li><strong>Cross-Site Request Forgery (CSRF):</strong> Attackers can trick authenticated users into unknowingly making unwanted requests, potentially leading to unintended actions being performed within their active session.</li><li><strong>Session Timeout/Browser Closure Issues:</strong> When a user’s session doesn’t terminate after a period of inactivity or persists even after the browser is closed, there’s a potential for attackers to exploit unattended active sessions and gain unauthorized access.</li><li><strong>Weak Session Token Generation: </strong>When session tokens lack randomness or possess inadequate length, attackers can readily guess or employ brute-force techniques to determine valid tokens. This can lead to unauthorized access.</li><li><strong>Token Leakage through URLs or Referer Headers:</strong> If session tokens are included in URLs or sent through HTTP headers, they can be exposed in browser history or referer logs, increasing the risk of unauthorized access.</li><li><strong>Insecure Token Storage:</strong> When session tokens are stored in cookies without the necessary security configurations, attackers can potentially gain access to or manipulate these tokens.</li><li><strong>Insecure Token Transmission:</strong> In the absence of transmission over secure channels (HTTPS), session tokens are vulnerable to interception during their transfer.</li></ul><p>To counter these risks, it’s essential to establish robust security protocols while managing sessions. This entails adopting practices such as generating session tokens with a strong element of randomness, strictly employing HTTPS for token transmission, setting up appropriate session expiration rules, fortifying defenses against cross-site scripting (XSS) and cross-site request forgery (CSRF) attacks, and ensuring the secure storage of session data. Consistent security audits and comprehensive testing play a pivotal role in detecting and rectifying vulnerabilities preemptively, thwarting potential exploitation by malicious entities.</p><h4>Access Control</h4><p>The final phase of managing user access involves making and enforcing accurate decisions regarding whether each individual request should be granted or denied. If the mechanisms described above are operating effectively, the application can identify the user sending each request. Based on this, it must determine if the user has the authorization to perform the requested action or access the desired data.</p><p>This process of access control typically requires nuanced handling, with distinct considerations being relevant to different sections of the application and various functionalities. Many applications support multiple user roles, each associated with specific privileges. Individual users may have permission to access only a subset of the overall application data. Certain functions might impose transaction limits and other validation checks, all of which must be correctly enforced according to the user’s identity.</p><p>When it comes to making and enforcing access decisions, the process itself can inadvertently become a vulnerable area if not managed securely. In such cases, attackers could potentially capitalize on weaknesses within the access control mechanisms to attain unauthorized entry or even tamper with their own permissions. Here’s a breakdown of how this process could evolve into an attack surface:</p><ul><li><strong>Insufficient Authorization Checks:</strong> If the application doesn’t rigorously check a user’s authorization before granting access, attackers could potentially access functionalities or data they shouldn’t be able to.</li><li><strong>Privilege Escalation: </strong>Attackers might find ways to escalate their privileges beyond what they are supposed to have, gaining access to sensitive features or data.</li><li><strong>Inadequate Role-Based Access Control (RBAC): </strong>Poorly implemented RBAC might allow users to assume roles with higher privileges than intended, providing access to unauthorized resources.</li><li><strong>Broken Access Control:</strong> Misconfigurations or coding errors could lead to access control bypass, enabling attackers to reach restricted areas.</li><li><strong>Horizontal Privilege Escalation:</strong> Attackers could try to access another user’s resources by exploiting insufficient checks between users.</li><li><strong>Vertical Privilege Escalation:</strong> If proper validation is not in place, attackers might try to gain higher privileges within the same user account.</li><li><strong>Insecure Defaults:</strong> If default access settings are too permissive, attackers could exploit them to gain access to sensitive areas.</li><li><strong>Insecure Direct Object References (IDOR): </strong>Poorly protected references to internal resources could allow attackers to directly access unauthorized resources.</li><li><strong>Parameter Manipulation:</strong> Attackers might manipulate input parameters to access unauthorized data or functionalities.</li><li><strong>Brute Force Attacks:</strong> Attackers might attempt to guess resource identifiers or use iterative methods to access resources they shouldn’t have access to.</li></ul><p>To address these potential risks, it’s crucial to establish access control mechanisms with a strong foundation. This involves implementing stringent authorization checks, conducting comprehensive vulnerability testing, ensuring the continuous application of Role-Based Access Control (RBAC), handling errors effectively, and adhering to the principle of granting minimal privilege. Consistent security audits and vigilant monitoring play a vital role in pinpointing and rectifying potential vulnerabilities proactively, before attackers can take advantage of them.</p><p>I will be discussing the remaining two fundamental defensive mechanisms in the upcoming articles.</p><p><strong>Reference:</strong></p><p>The web application hacker’s handbook- Finding and exploiting security flaws.</p><blockquote><em>Let’s connect?</em></blockquote><blockquote><em>LinkedIn: </em><a href="http://www.linkedin.com/in/ravitejmbandlekar"><em>www.linkedin.com/in/ravitejmbandlekar</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23b02ddf1835" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decoding Web Application Protection: Essential Defense Mechanisms]]></title>
            <link>https://ravitejbandlekar.medium.com/decoding-web-application-protection-essential-defense-mechanisms-3580f40e6d29?source=rss-3d7b75a5b260------2</link>
            <guid isPermaLink="false">https://medium.com/p/3580f40e6d29</guid>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[web-application-security]]></category>
            <category><![CDATA[network-security]]></category>
            <dc:creator><![CDATA[Ravitej Bandlekar]]></dc:creator>
            <pubDate>Thu, 24 Aug 2023 11:48:15 GMT</pubDate>
            <atom:updated>2023-08-24T11:48:15.135Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GKW-QxViM83coEdW.png" /><figcaption>Source: <a href="https://usersnap.com/">https://usersnap.com/</a></figcaption></figure><p>The World Wide Web has evolved significantly from its early days and is now almost unfamiliar in its current form. A large majority of the websites we encounter today can be better classified as applications. These sites offer extensive functionalities, relying on smooth communication between servers and browsers to facilitate tasks. Activities like user registration, login processes, financial transactions, content creation, and efficient search functions have become commonplace. Yet, these advancements also bring about a host of new and noteworthy security risks that need to be dealt with proactively.</p><p>Web applications serve a variety of common functions, including online shopping, auctions, banking, gambling, emailing, and social media, which collectively form what we know as the public internet. Furthermore, businesses also utilize these web applications internally to provide authorized individuals access to highly confidential information. This internal usage encompasses applications like HR management systems and various business-specific tools.</p><p>As technology continues to advance, web applications have undergone significant transformations, leading to the emergence of a fresh spectrum of security vulnerabilities. The collection of frequently encountered issues has also shifted over time. Novel attack methods have come to light, catching developers off guard as they were not anticipated during the application’s initial development. Certain attack avenues are diminishing due to heightened awareness about them. As new technologies develop, they create opportunities for novel attack vectors and vulnerabilities. Meanwhile, certain types of security weaknesses have diminished in prevalence due to alterations in web browser software.</p><p>Among the most severe and concerning breaches targeting web applications are those that expose confidential information or illicitly access the underlying backend systems supporting the application. However, to this day, numerous organizations still view attacks causing system downtime as a noteworthy threat. For instance, Denial of Service (DoS) attacks, which incapacitate and congest the services offered by organizations to their clients, resulting in reputational damage and various business implications, are seen as having significant repercussions.</p><p>Throughout this progression, breaches of web applications have consistently made headlines. There’s no indication that a turning point has been reached, suggesting that these security challenges are diminishing. In certain assessments, safeguarding web application security has now become the most crucial arena where those with computing assets and valuable data strive to fend off attackers. This dynamic is likely to persist in the foreseeable future.</p><p>What is OWASP?</p><p>The Open Web Application Security Project, abbreviated as OWASP, is a global nonprofit entity with a primary focus on enhancing the security of web applications. A fundamental tenet of OWASP is to ensure that all their resources are openly accessible and conveniently reachable on their website. This accessibility empowers individuals to enhance their web application security independently. The assortment of resources provided by OWASP encompasses written guides, software tools, video content, and discussion forums. Among their most renowned initiatives is the OWASP Top 10.</p><p>The OWASP Top 10 is a periodically updated document that highlights primary security issues concerning web applications. It concentrates on the ten most pivotal risks that these applications face. This report is collaboratively assembled by a panel of security specialists spanning the globe. OWASP labels the Top 10 as an ‘awareness document’ and strongly advises all enterprises to integrate it into their operations as a means to reduce and address security vulnerabilities.</p><p>Top 10 as of year 2021:</p><ol><li>Broken access control.</li><li>Cryptographic failures (previously known as sensitive data exposure)</li><li>Injection</li><li>Insecure design</li><li>Security misconfiguration</li><li>Vulnerable and outdated components</li><li>Identification and authentication failures (previously known as broken authentication)</li><li>Software and data integrity failures</li><li>Security logging and monitoring failures (previously known as insufficient logging and monitoring)</li><li>Server-side request forgery</li></ol><p>The central security challenge faced by web applications, wherein all user inputs are considered untrusted, leads to the implementation of various security measures by these applications to shield themselves from potential attacks. The majority of applications utilize methods that share a common conceptual foundation, even though the specifics of the design and the level of success in their execution exhibit considerable diversity.</p><p>The defense mechanisms employed by web applications comprise the follow core elements.</p><ul><li>Administering user permissions for accessing the application’s data and capabilities, preventing unauthorized entry.</li><li>Controlling user inputs within the application’s functions to prevent malformed input from causing undesired outcomes.</li><li>Addressing assailants to ensure the application responds appropriately when directly targeted, utilizing defensive and proactive measures to thwart the attacker’s intentions.</li><li>Supervising the application’s operations by enabling administrators to observe activities and tailor functionalities.</li></ul><p>Due to their crucial role in tackling the primary security challenges, these mechanisms also constitute the predominant portion of a typical application’s vulnerability to attacks. If recognizing your adversary stands as the initial principle of conflict, then possessing a comprehensive understanding of these mechanisms is the key requirement for successfully targeting applications.</p><p>The progression of web applications has introduced intricate features and security complexities. To adeptly shield against potential threats and maintain the integrity of these applications within the dynamic digital realm, it’s imperative to possess a thorough grasp of security mechanisms and the vulnerabilities tied to them.</p><p>The conversation will be continued and elaborated upon in our next articles.</p><p>Reference:</p><p>The web application hacker’s handbook- Finding and exploiting security flaws.</p><blockquote><em>Let’s connect?</em></blockquote><blockquote><em>LinkedIn: </em><a href="http://www.linkedin.com/in/ravitejmbandlekar"><em>www.linkedin.com/in/ravitejmbandlekar</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3580f40e6d29" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Resilience: Exploring the Power of Redundancy in Systems]]></title>
            <link>https://ravitejbandlekar.medium.com/building-resilience-exploring-the-power-of-redundancy-in-systems-187e24134c2b?source=rss-3d7b75a5b260------2</link>
            <guid isPermaLink="false">https://medium.com/p/187e24134c2b</guid>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[firewall]]></category>
            <dc:creator><![CDATA[Ravitej Bandlekar]]></dc:creator>
            <pubDate>Mon, 21 Aug 2023 16:18:08 GMT</pubDate>
            <atom:updated>2023-08-21T16:18:08.804Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/820/0*FgmnRbv57Ct90mRp.jpg" /><figcaption>Source: <a href="https://teceze.com/">https://teceze.com/</a></figcaption></figure><p>Cybersecurity resilience, also referred to as “resilience,” refers to an entity’s ability to withstand and recover from cyberattacks, data breaches, and other similar cybersecurity breaches, whether it be an organization, system, or person. The goal is to minimize operational disruptions, protect data integrity, and maintain overall functionality. This idea centers on having the ability to adapt, respond, and keep up effective operations despite the constantly shifting world of cyber dangers.</p><h4>Terminology</h4><p>In IT and systems architecture, high availability and fault tolerance are two ideas that strive to maintain consistent and dependable operation of systems and services, particularly in the face of hardware breakdowns, software bugs, or other disturbances.</p><h4>High Availability (HA)</h4><p>In order to reduce downtime and make sure that services are as available and functional for consumers as possible, systems and infrastructure are designed and implemented with high availability. Even when specific parts or systems malfunction, the objective is to maintain access.</p><h4>Fault Tolerance</h4><p>The goal of fault tolerance is to create systems that can function even when some parts or subsystems go down. The objective is to preserve normal operation both during and after failures in addition to minimizing downtime.</p><h4>Redundancy Planning</h4><p>IT, engineering, and business sectors all use redundancy planning as a technique to guarantee the availability, dependability, and continuity of crucial systems, processes, and activities. Redundancy is the idea of having backup or duplicate systems, processes, or components in place so that if one fails or has a problem, another can take over without creating a lot of interruption or downtime. Enhancing fault tolerance, reducing risks, and maintaining functionality even in the face of failures or unforeseen events are the objectives of redundancy planning.</p><p>Implementing methods and steps to guarantee the availability, integrity, and confidentiality of data and systems even in the face of cyberthreats, assaults, or other security incidents is known as redundancy planning in cybersecurity. It focuses on developing redundant or backup systems, procedures, and controls to keep things running smoothly and safeguard sensitive data in the case of a security breach or other disturbance. Enhancing cybersecurity defenses’ resilience and reducing the impact of prospective incidents are the objectives.</p><p>To ensure the protection of systems and network equipment, as well as to establish redundancy for upholding high-availability services, the implementation of fault-tolerant systems is essential. Creating a fault-tolerant system involves integrating multiple redundant components that enable the system to sustain functionality in the event of equipment failures. For instance, a server with a sole hard drive and a lone power supply lacks fault tolerance: a power supply malfunction renders the entire server non-operational due to the absence of power supply. The presence of fault-tolerant systems holds significant importance in maintaining seamless business operations. The central principle of redundancy lies in its ability to eliminate vulnerabilities stemming from solitary points of failure.</p><h4>Equipment Redundancy</h4><p>To ensure ongoing functioning in the event of equipment failure, redundant hardware components are used in the equipment. Critical servers, for instance, might be set up in a data center with several hard drives and redundant power supplies. The redundant components can take over if a hard drive or power source fails, preventing downtime.</p><h4>Redundant Internet Connectivity</h4><p>To assure continuous internet access, redundant internet connectivity refers to having several internet connections from various service providers. A company might, for instance, have a primary fiber optic link as well as a backup satellite connection. The backup connection may automatically switch on to maintain internet access if the primary connection goes down.</p><h4>Geographical Redundancy</h4><p>In order to lessen the effects of local calamities or interruptions, geographic redundancy entails replicating systems or data in many geographic areas. Geographic redundancy is frequently offered by cloud service providers. For instance, a business might keep its data on servers positioned throughout the world. The information is still accessible from the redundant location even if there is a significant outage in one region.</p><h4>Disk Redundancy</h4><p>In order to prevent data loss, disk redundancy requires having numerous hard disks in a storage system. Disk redundancy is frequently achieved using RAID (Redundant Array of Independent Disks). For instance, data is replicated on two disks in a RAID 1 configuration. The data is still accessible on the other drive even if one fails.</p><h4>Network Redundancy</h4><p>By providing alternate data transmission routes, network redundancy provides continuous connectivity. Implementing a network with redundant switches and routers is one example. Traffic is immediately diverted through the backup switch if one switch fails, preventing network disruption.</p><h4>Power Redundancy</h4><p>In order to keep systems working during power outages, power redundancy entails having backup power sources. Uninterruptible power supply (UPS) and generators are frequently used in data centers. When the primary power source fails, the UPS keeps things running until the backup generator kicks in.</p><p>Redundancy solutions are added to systems to improve fault tolerance, reduce single points of failure, and increase overall system resilience. Redundancy planning helps to maintain smooth operations and reduce downtime, which is essential for preserving business continuity and data integrity, whether in equipment, networking, data storage, or power supply.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=187e24134c2b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking Knowledge: Cryptology Revealed]]></title>
            <link>https://ravitejbandlekar.medium.com/unlocking-knowledge-cryptology-revealed-8d4f364e10de?source=rss-3d7b75a5b260------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d4f364e10de</guid>
            <category><![CDATA[cryptography]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[comptia]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[network-security]]></category>
            <dc:creator><![CDATA[Ravitej Bandlekar]]></dc:creator>
            <pubDate>Sat, 19 Aug 2023 23:28:45 GMT</pubDate>
            <atom:updated>2023-08-19T23:28:45.744Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I99brhwQpbSXPrQa.png" /><figcaption>Source: <a href="https://theleaflet.in/">https://theleaflet.in/</a></figcaption></figure><p>Cryptography, originating from the Greek term “kryptos graphein,” entails the discipline and creativity of encoding information to ensure its confidentiality and durability against adversarial actions.</p><p>The core concepts of cryptography are Confidentiality, Integrity, Authentication and Non-repudiation.</p><p>Feel welcome to check out this article to enhance your understanding.</p><p><a href="https://ravitejbandlekar.medium.com/beyond-the-lock-and-key-insights-into-cryptology-34767aa07a61">Beyond the Lock and Key: Insights into Cryptology</a></p><p>The Central function of cryptography is encryption, the transformation of data into unreadable form.</p><p>Plain Text &gt;&gt;&gt; Encryption &gt;&gt;&gt; Cipher Text &gt;&gt;&gt; Decryption &gt;&gt;&gt; Plaintext</p><p>Ciphertext is the encrypted form of plaintext (which is the original, human-readable message or data), which appears as a seemingly random and unreadable sequence of characters. This method facilitates sending sensitive data across unsecure communication routes, like the internet.</p><p>The attributes:</p><ol><li>Plain Text and Cipher Text</li><li>Encryption and Decryption</li><li>Key</li></ol><p>I’ve elaborated on Plain/Cipher Text and Encryption/Decryption in the aforementioned discussion.</p><p><strong>Let’s understand what is a key?</strong></p><p>In the realm of cryptography, a key refers to a data element, typically presented as a sequence of characters or a numeric entity. This data is employed as an input for encryption or decryption algorithms. The key plays a pivotal role in dictating the manner in which the algorithm converts plain, readable text into encoded, unreadable text (encryption), or the reverse process (decryption). The effectiveness of a cryptographic system frequently hinges on the confidentiality of the key and the meticulous control over its handling and usage.</p><p>Key size: Key size in cryptography refers to the length of the cryptographic key, usually measured in bits. It impacts encryption complexity and data security. A larger key size increases possible keys, thwarting attackers from brute-force decryption. Growing computing power demands larger key sizes for sustained security.</p><p>Key space: Key space in cryptography refers to the total potential keys for an encryption algorithm. It quantifies key combinations. In binary, 1 bit has 2 choices (0 or 1), 2 bits have 4 choices (00, 01, 10, 11), and so on. A bigger key space means greater security, as attackers must test all options to decrypt data.</p><p>Algorithms Categories:</p><ol><li>Symmetric key algorithm</li><li>Asymmetric key algorithm</li><li>Hashing algorithm</li></ol><h4>Symmetric key algorithm</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_TRgsZoKJCb-kobU.png" /><figcaption>Source: <a href="https://www.cisco.com/">https://www.cisco.com/</a></figcaption></figure><p>Dependence is placed on an encryption key, known as a “shared secret,” which is provided to all individuals engaging in communication. This key functions as the means to encrypt and decrypt messages and is held by all parties involved, including the sender and receiver.</p><p>When employing a considerably lengthy encryption key, symmetric encryption becomes notably resistant to decryption attempts. This technique is primarily used for extensive data encryption, specifically ensuring the confidentiality of information.</p><p>Algorithms Used:</p><ol><li><strong>AES (Advanced Encryption Standard):</strong> AES is one of the most widely used symmetric encryption algorithms. It supports key sizes of 128, 192, or 256 bits and is known for its efficiency and security. It’s used in various applications, including securing sensitive data and communications.</li><li><strong>DES (Data Encryption Standard):</strong> DES was one of the earliest symmetric encryption algorithms. It uses a 56-bit key and operates on 64-bit blocks of data. While DES has been largely replaced by more secure algorithms due to its relatively short key length, it still holds historical significance.</li><li><strong>3DES (Triple DES):</strong> 3DES is a modification of DES that applies the DES algorithm three times with different keys for added security. It was developed to enhance the security of DES and is still used in certain legacy systems.</li><li><strong>Blowfish:</strong> Blowfish is a symmetric encryption algorithm designed for fast encryption and decryption. It supports variable key lengths and block sizes. It’s not as widely used as AES but has been used in various applications.</li><li><strong>RC4 (Rivest Cipher 4):</strong> RC4 is a stream cipher known for its simplicity and speed. It’s been used in various applications, including early versions of SSL/TLS protocols. However, due to vulnerabilities and weaknesses, it’s generally not recommended for secure applications anymore.</li><li><strong>Serpent:</strong> Serpent is a symmetric encryption algorithm known for its security and strong resistance against various cryptographic attacks. It was one of the finalists in the AES competition but wasn’t selected as the standard.</li><li><strong>Twofish:</strong> Twofish is another algorithm that was a finalist in the AES competition. It’s known for its flexibility and strong security features. While it wasn’t chosen as the AES standard, it’s still considered a reliable encryption algorithm.</li><li><strong>Camellia:</strong> Camellia is a symmetric encryption algorithm developed jointly by Japan and France. It supports various key lengths and block sizes and is considered secure and efficient.</li></ol><p>Instance:</p><p>Consider the scenario where Rick and John aim to establish secure communication over the internet. They opt to employ symmetric encryption for their message exchange. Here’s an overview of how the procedure would unfold:</p><ol><li>Key Generation:</li></ol><ul><li>Rick and John agree on a secret encryption key. This is the “shared secret” key they will use for both encrypting and decrypting messages.</li></ul><p>2. Message Encryption:</p><ul><li>John wants to send a confidential message to Rick. He takes the message and the shared secret key and uses a symmetric encryption algorithm (like AES — Advanced Encryption Standard) to encrypt the message.</li><li>The encrypted message can only be decrypted using the same shared secret key.</li></ul><p>3. Message Transmission:</p><ul><li>John sends the encrypted message to Rick over the internet.</li></ul><p>4. Message Decryption:</p><ul><li>Rick receives the encrypted message. He uses the same shared secret key to decrypt the message using the symmetric encryption algorithm.</li><li>Since both John and Rick have the same key, Rick can successfully decrypt the message and read its contents.</li></ul><p>Within this illustration, the encryption and decryption keys remain identical (referred to as the shared secret), enhancing operational efficiency. Nevertheless, the primary hurdle in symmetric encryption lies in the secure distribution and management of the shared secret key. Should an unauthorized third party obtain access to this key, they would gain the ability to decipher the messages, posing a significant security risk.</p><h4>Asymmetric key algorithm</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/0*KEdhmlSZBHQNax0q.png" /><figcaption>Source: <a href="https://www.ssl2buy.com/">https://www.ssl2buy.com/</a></figcaption></figure><p>Referred to as public key algorithms, these cryptographic methods address the vulnerabilities present in symmetric key encryption. In this approach, each user possesses a pair of keys: a public key, shared openly among all users, and a private key, safeguarded in secrecy and exclusively known to the key’s owner. However, a unique twist emerges — encrypting and decrypting demands the collaborative use of contrasting yet interconnected key pairs.</p><p>Algorithms Used:</p><p>Public-key encryption algorithms, referred to as asymmetric encryption algorithms, operate with a set of keys: a public key for encryption and a private key for decryption (or vice versa). Below are several widely employed asymmetric encryption algorithms:</p><ol><li>RSA (Rivest-Shamir-Adleman):</li></ol><ul><li>RSA is one of the most widely used asymmetric encryption algorithms.</li><li>It’s used for secure communication, digital signatures, and key exchange.</li><li>The security of RSA relies on the difficulty of factoring large prime numbers.</li><li>RSA encryption is slower compared to symmetric encryption, especially for large data.</li></ul><p>2. ECC (Elliptic Curve Cryptography):</p><ul><li>ECC offers strong security with shorter key lengths compared to RSA.</li><li>It’s used in a variety of applications, including secure communication and digital signatures.</li><li>ECC is computationally efficient and suitable for resource-constrained environments.</li></ul><p>3. ElGamal Encryption:</p><ul><li>ElGamal is based on the difficulty of the discrete logarithm problem.</li><li>It’s used for secure key exchange and encryption.</li><li>ElGamal encryption involves randomness and can be slower compared to RSA.</li></ul><p>4. DSA (Digital Signature Algorithm):</p><ul><li>DSA is primarily used for creating digital signatures.</li><li>It’s a variant of ElGamal and is widely used for authentication and non-repudiation.</li><li>DSA relies on the discrete logarithm problem for security.</li></ul><p>5. Diffie-Hellman Key Exchange:</p><ul><li>While not strictly an encryption algorithm, Diffie-Hellman is used to establish a shared secret key between parties.</li><li>It’s the foundation for many encryption protocols and algorithms.</li><li>Diffie-Hellman is based on the difficulty of the discrete logarithm problem.</li></ul><p>These are some examples of asymmetric encryption algorithms. Each algorithm possesses distinct advantages and limitations, and the selection of an algorithm hinges on considerations such as security prerequisites, computational effectiveness, and the constraints of the particular application.</p><p>Instance:</p><p>Let’s explore an example of asymmetric encryption using Rick and John:</p><ol><li>Key Generation:</li></ol><ul><li>Rick generates a key pair consisting of a public key and a private key. The public key is meant to be shared openly, while the private key is kept secure and known only to Rick.</li><li>Similarly, John generates his own key pair: a public key to share and a private key to keep secret.</li></ul><p>2. Message Encryption:</p><ul><li>John wants to send a confidential message to Rick. Instead of using a shared secret key like in symmetric encryption, he uses Rick’s public key to encrypt the message.</li><li>This encrypted message can only be decrypted using Rick’s corresponding private key.</li></ul><p>3. Message Transmission:</p><ul><li>John sends the encrypted message to Rick over the internet. Even if intercepted, the encrypted message remains unintelligible without Rick’s private key.</li></ul><p>4. Message Decryption:</p><ul><li>Rick receives the encrypted message. He uses his private key to decrypt the message, which was encrypted using his public key.</li><li>Since only Rick possesses the corresponding private key, he’s able to successfully decrypt the message and read its contents.</li></ul><p>Asymmetric encryption offers the benefit of secure message transmission without relying on a common secret key. Moreover, it serves as the foundation for diverse security mechanisms such as digital signatures and protocols for secure key exchange.</p><h4>Difference:</h4><p><strong>Symmetric Encryption:</strong></p><p>Uses the same key for both encryption and decryption.</p><ul><li>Faster and more efficient for large amounts of data.</li><li>Requires secure key distribution.</li><li>Not suitable for secure communication between parties that have never interacted before.</li><li>Examples: AES, DES, 3DES.</li></ul><p><strong>Asymmetric Encryption:</strong></p><ul><li>Uses two mathematically related keys: public key for encryption, private key for decryption.</li><li>Slower due to the complex mathematical operations involved.</li><li>Public keys can be openly shared, private keys must be kept secret.</li><li>Eliminates the need for secure key distribution.</li><li>Suitable for secure communication between parties that have never interacted before.</li><li>Examples: RSA, ECC, ElGamal.</li></ul><p>Related article</p><p><a href="https://ravitejbandlekar.medium.com/the-dna-of-security-decoding-confidentiality-integrity-and-availability-b45b6305146e">The DNA of Security: Decoding Confidentiality, Integrity, and Availability</a></p><p>Reference:</p><p>Cryptography and Network Security Principles and Practice (6th Edition) by William Stallings</p><p>Jonathan Katz, Yehuda Lindell — Introduction to Modern Cryptography</p><blockquote>Let’s connect?</blockquote><blockquote>LinkedIn: <a href="http://www.linkedin.com/in/ravitejmbandlekar"><em>www.linkedin.com/in/ravitejmbandlekar</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d4f364e10de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond the Lock and Key: Insights into Cryptology]]></title>
            <link>https://ravitejbandlekar.medium.com/beyond-the-lock-and-key-insights-into-cryptology-34767aa07a61?source=rss-3d7b75a5b260------2</link>
            <guid isPermaLink="false">https://medium.com/p/34767aa07a61</guid>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[cryptography]]></category>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Ravitej Bandlekar]]></dc:creator>
            <pubDate>Tue, 18 Jul 2023 17:02:28 GMT</pubDate>
            <atom:updated>2023-07-18T17:06:23.620Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*YCk4r3kEWwNIKZEf.jpg" /><figcaption>Source: brightlineit.com</figcaption></figure><p><strong>The Wikipedia defines </strong>Cryptography, or cryptology as the practice and study of techniques for secure communication in the presence of adversarial behavior. More generally, cryptography is about constructing and analyzing protocols that prevent third parties or the public from reading private messages.Modern cryptography exists at the intersection of the disciplines of mathematics, computer science, information security, electrical engineering, digital signal processing, physics, and others.</p><p>The prefix “crypt” means “hidden” and suffix “graphy” means “writing”.</p><p>Core concepts related to information security are also central to cryptography.</p><ol><li>Confidentiality</li><li>Integrity</li><li>Authentication</li><li>Non-repudiation</li></ol><p>For a comprehensive understanding, I’ve tackled Confidentiality and Integrity in the article below. You’re welcome to give it a read.</p><p><a href="https://ravitejbandlekar.medium.com/the-dna-of-security-decoding-confidentiality-integrity-and-availability-b45b6305146e">The DNA of Security: Decoding Confidentiality, Integrity, and Availability</a></p><p>Let’s discuss authentication and non-repudiation in this article.</p><h4>Authentication</h4><p>The process of confirming the identity of a user, system, or organization trying to access a resource or system is known as authentication, and it is a key idea in security. It is crucial to ensuring that only authorized users or organizations can access sensitive data, systems, or services and that unauthorized access is avoided.</p><p>Binding a certain ID to a particular computer connection is the process of authentication.</p><p>The three categories to authenticate identity of user are:</p><blockquote>What users know (such as passwords, pins)</blockquote><blockquote>What users have (such as tokens)</blockquote><blockquote>What users are (biometrics such as fingerprints)</blockquote><blockquote>The Framework</blockquote><p><strong>Who:</strong> The user or entity making the attempt to get access is identified in this aspect. During authentication, the system asks for credentials that specifically identify the user in order to confirm “who” they are. These login information may consist of a username, email address, or some other specific identification for the user.</p><p><strong>What: </strong>The specific resource or service that the user wishes to access is included in this aspect. The amount of authorisation required is determined as well as “what” the user is attempting to access. Authentication makes guarantee that only authorized users can access particular resources, even though various resources may have varied access needs.</p><p><strong>Where: </strong>The location or context of the authentication request is the emphasis of this feature. The location can be taken into account in contemporary authentication systems, particularly in network security, to determine whether an access request is valid or possibly suspicious. For instance, if an access request comes from a strange place, it can make additional security precautions necessary.</p><p><strong>When: </strong>This aspect considers the timing of the authentication attempt. The “when” of authentication is essential for security purposes because access rights may be time-bound. For instance, an employee might have access to sensitive data during work hours but not after business hours. Proper authentication ensures access is only granted during the appropriate time frames.</p><p><strong>How: </strong>The technique or techniques used to confirm the user’s identification are covered under this aspect. It has to do with the technology and authentication methods used to verify the legitimacy of the user. As was already noted, different techniques can be employed as part of the authentication process, including passwords, biometrics, tokens, smart cards, and multi-factor authentication.</p><h4>Non-repudiation</h4><p>Non-repudiation is a concept in information security and cryptography that ensures the integrity of a message or transaction by preventing the sender of the message from later denying their involvement or the authenticity of the message. It is one of the fundamental security objectives, alongside confidentiality, integrity, and availability.</p><p>An item of some confusion, the concept of nonrepudiation is actually fairly simple. Nonrepudiation refers to the inability of the message sender to afterwards repent her actions. Because there are no face-to-face encounters involved in electronic data exchanges, this is crucial. Public key cryptography and the idea that only you know your private key form the foundation of nonrepudiation. Nonrepudiation can be demonstrated by the existence of a communication that was signed with your private key, which should only be known by you. Any claim that you did not send the communication is disproved when a third party can verify your signature using your public key. Symmetric algorithms are unable to accomplish nonrepudiation since it is dependent on asymmetric cryptography.</p><p>Non-repudiation is achieved with help of the follow elements</p><ol><li>Digital Signatures</li></ol><p>2. Timestamping</p><p>3. Secure key management</p><p>4. Audit Trail</p><blockquote>The Framework</blockquote><p><strong>Who: </strong>The parties involved in a communication or transaction are identified through non-repudiation. It makes sure that the person who sends a message or starts a certain action cannot afterwards deny their involvement. It also applies to the recipient, who must be able to demonstrate that they actually received the message from the alleged sender.</p><p><strong>What:</strong> The message’s or the transaction’s type are referenced in the “what” part of non-repudiation. It makes sure that the message’s or data’s integrity is preserved and that no unauthorized changes were made while being transmitted. In order to achieve non-repudiation for the message’s content, digital signatures are frequently utilized.</p><p><strong>Where:</strong> Non-repudiation is also influenced by the setting in which the communication or transaction takes place. This can apply to actual places as well as network settings or virtual environments. To guarantee that the security goals are upheld, non-repudiation systems should function in a variety of settings.</p><p><strong>When: </strong>Non-repudiation is time sensitive. It requires that the timestamp of a message or transaction be recorded accurately to provide evidence of the event’s occurrence. Timestamping services play a crucial role in ensuring that the time of the message or action can be reliably verified.</p><p>Who: Digital signatures, secure key management, and cryptographic methods are used to achieve non-repudiation. A sender establishes a digital signature for a message using their private key. The communication is then guaranteed to have not been tampered with and to have truly come from the sender when the recipient uses the sender’s public key to validate the signature.</p><p>Let&#39;s see an example to understand non-repudiation more.</p><p>Online Banking Transaction Scenario</p><p>Scenario: Steve wants to make an online banking transaction to transfer funds to Tony’s account. Both parties need assurance that the transaction is genuine, and Steve cannot later deny initiating the transfer.</p><p><strong>Key Generation:</strong></p><ul><li>Steve and Tony generate a pair of cryptographic keys: a private key (known only to only them) and a corresponding public key (shared with others).</li></ul><p><strong>Transaction Initiation:</strong></p><ul><li>Steve initiates the fund transfer through his online banking portal. The transaction details, including the recipient (Tony’s account) and the amount, are recorded.</li></ul><p>Digital Signature Creation:</p><ul><li>Before submitting the transaction, Steve creates a digital signature for the transaction data using his private key.</li></ul><p>Transaction Submission:</p><ul><li>Steve’s bank receives the transaction request, along with the attached digital signature.</li></ul><p>Signature Verification:</p><ul><li>Steve’s bank uses Steve’s public key to verify the digital signature.</li><li>If the signature is valid and matches Steve’s public key, the bank can be confident that Steve authorized the transaction.</li></ul><p>Non-Repudiation:</p><ul><li>Non-repudiation is achieved because Steve cannot later deny initiating the transfer. His digital signature provides undeniable evidence of his involvement in the transaction. If Steve disputes the transfer, the bank can use the verified signature to refute his denial.</li></ul><h3>The Basics</h3><p><strong>Cryptography</strong> is the science of secret writing with the goal of hiding the meaning of a message.</p><p><strong>Cryptanalysis </strong>which is the study of the cryptographic algorithm and the breaking of those secret codes. The person practicing Cryptanalysis is called a <strong>Cryptanalyst</strong>. By discovering any weak points in the system, it helps us better understand cryptosystems and also enhance them. This allows us to work on the algorithm and produce secret codes that are more secure. An instance of this would be a Cryptanalyst attempting to extract the plaintext from a ciphertext. The plaintext or the encryption key can be deduced with its assistance.</p><p><strong>Encryption</strong> is the process of converting plaintext (readable and understandable data) into ciphertext (unreadable and scrambled data) using an encryption algorithm and a secret key. The goal of encryption is to ensure confidentiality, preventing unauthorized access to the information. The ciphertext can only be decrypted back to plaintext using the corresponding decryption algorithm and the secret key.</p><h4>Encryption</h4><p>Using an encryption algorithm and a secret key, encryption transforms plaintext (data that can be read and understood) into ciphertext (data that cannot be read and is scrambled). Encryption works to protect information’s confidentiality by limiting access by unauthorized parties. Only the appropriate decryption algorithm and secret key can convert the ciphertext back to plaintext. Sensitive data is frequently protected via encryption when it is sent over networks or stored on hardware. It guards against unauthorized persons intercepting or accessing the data.</p><h4>Symmetric Encryption</h4><p>Prior to the invention of public key encryption in the 1970s, the only form of encryption in use was symmetric encryption, often known as conventional encryption or single-key encryption. It uses a single key for both encryption and decryption. The same key is shared between the sender and the recipient.</p><h4>Asymmetric Encryption</h4><p>A pair of mathematically related keys — a public key and a private key — are used in asymmetric encryption, often known as public-key encryption.</p><p>For encryption and decryption, two keys are created: one key is the public key, which is known to all users, and the other key is the private key, which is kept hidden and provided to the user to keep private. With this system, the sender encrypts a message or file using the public key of the recipient who is intended. The recipient uses a private key that she alone has in order to decrypt this message. The private key cannot be inferred from the public key because of the way the keys are generated. Without this private key, no one else will be able to decrypt the message. Users can share public keys directly or look them up in public key directories.</p><h4>Hashing</h4><p>Using the one-way encryption method of hashing, data is converted into a fixed-length character string known as a hash value or digest. It is frequently used to check the accuracy of data and safely store passwords.</p><p>In encryption systems, a message’s “fingerprint” is created using a hashing value. As a result, the message cannot be wrongly altered during transit to its destination. Hashing protects the integrity of a message in the overall information assurance model and is most frequently used in conjunction with digital signatures.</p><p>The one-way hashing function, which converts a variable-sized message into a fixed-length result known as a hash value or a message digest, is the most often used hashing algorithm. Because it’s challenging to reverse the process and the results are never decrypted — only compared to one another when performing the same function again on the same message — this function is referred to as “one-way”.</p><p>Reference:<br>Cryptography and Network Security Principles and Practice (6th Edition) by William Stallings</p><p>Jonathan Katz, Yehuda Lindell — Introduction to Modern Cryptography</p><p><a href="https://www.geeksforgeeks.org/cryptanalysis-and-types-of-attacks/">https://www.geeksforgeeks.org</a></p><blockquote><em>Let’s connect?</em></blockquote><blockquote><em>LinkedIn: </em><a href="http://www.linkedin.com/in/ravitejmbandlekar">www.linkedin.com/in/ravitejmbandlekar</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34767aa07a61" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The DNA of Security: Decoding Confidentiality, Integrity, and Availability]]></title>
            <link>https://ravitejbandlekar.medium.com/the-dna-of-security-decoding-confidentiality-integrity-and-availability-b45b6305146e?source=rss-3d7b75a5b260------2</link>
            <guid isPermaLink="false">https://medium.com/p/b45b6305146e</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cryptography]]></category>
            <category><![CDATA[network-security]]></category>
            <dc:creator><![CDATA[Ravitej Bandlekar]]></dc:creator>
            <pubDate>Fri, 14 Jul 2023 18:16:03 GMT</pubDate>
            <atom:updated>2023-07-14T18:16:03.141Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*otFUUkKFMLMwVWNQVmZ71A.jpeg" /><figcaption>Source: <a href="http://www.securitymagazine.com/">www.securitymagazine.com</a></figcaption></figure><h3>The Triad</h3><p>Security management concepts and principles are important elements in creating a secure environment. They establish the necessary guidelines for a security policy and the implementation of effective security measures. The primary objectives of a secure environment are to protect confidentiality, maintain data integrity, and ensure availability (commonly known as the CIA Triad). Security controls are evaluated based on how well they address these three core principles of information security. Similarly, vulnerabilities and risks are assessed based on the potential harm they can cause to the CIA Triad principles.</p><h3>Confidentiality</h3><p>The idea of confidentiality refers to the procedures used to protect the privacy of information, items, or resources. To prevent or reduce illegal access to data, confidentiality protection aims to protect sensitive information. Protections against disclosure and unauthorized access are provided by confidentiality.</p><p>Confidentiality ensures that information is accessible only to authorized individuals or entities. It involves protecting sensitive data from unauthorized access, disclosure, or theft. Confidentiality measures aim to maintain privacy and prevent data breaches.</p><p>Concepts, conditions, and aspects of confidentiality include the following:</p><ul><li><strong>Sensitivity </strong>— refers to the quality of information, which could cause harm or damage if disclosed.</li><li><strong>Discretion </strong>— is an act of decision where an operator can influence or control disclosure in order to minimize harm or damage.</li><li><strong>Criticality</strong> -the level to which information is mission critical is its measure of criticality. The higher the level of criticality, the more likely the need to maintain the confidentiality of the information.</li><li><strong>Concealment</strong> -is the act of hiding or preventing disclosure. Often concealment is viewed as a means of cover, obfuscation, or distraction. A related concept to concealment is security through obscurity, which is the concept of attempting to gain protection through hiding, silence, or secrecy.</li><li><strong>Secrecy</strong> -is the act of keeping something a secret or preventing the disclosure of information.</li><li><strong>Privacy</strong> -refers to keeping information confidential that is personally identifiable or that might cause harm, embarrassment, or disgrace to someone if revealed.</li><li><strong>Seclusion</strong> -involves storing something in an out-of-the-way location, likely with strict access controls.</li><li><strong>Isolation</strong> — is the act of keeping something separated from others.</li></ul><blockquote><strong>The framework</strong></blockquote><p><strong>Who: </strong>Access to sensitive information should only be granted to authorized individuals or organizations.</p><p><strong>What:</strong> Sensitive information that must be safeguarded against illegal access or publication.</p><p><strong>When:</strong> No matter if the data is in motion (in transit) or at rest (being stored).</p><p><strong>Where: </strong>Data sent via networks, stored in file systems, or stored in databases.</p><p><strong>How:</strong> By implementing access controls, encryption, and secure communication protocols to restrict access to authorized users, prevent eavesdropping, and safeguard data from unauthorized parties.</p><p>Encryption is one method of ensuring confidentiality. For instance, when you visit your online banking account (how), data is transmitted securely through HTTPS utilizing secure communication protocols between your device and the bank’s server (how). Because of the encryption, even if data is intercepted by an unauthorized person during transmission, they will not be able to decrypt the sensitive information (how).</p><p>The use of access controls is another strategy. To limit access to sensitive data, for instance, an organization in a corporate setting may have various levels of access permissions (how). Certain confidential information, such as customer or payroll information, is only accessible to authorized employees who fulfill specific roles (who). By doing this, it is ensured that only those who need access to private information do so, and that unauthorized people cannot access sensitive information, which protects privacy.</p><p>The examples of confidential data include the following:<br>• Intellectual property<br>• Personal identity information<br>• Credit card information<br>• Bank account information<br>• Personal health information<br>• Business or trade secrets</p><blockquote>Breach</blockquote><p>When personal information or data provided by a client of an organization that is subject to certain data confidentiality agreements is either purposefully or mistakenly exposed to a third party without the client’s consent, there has been a breach of confidentiality.</p><p>In many nations across the world, there are numerous laws and guidelines in place that allow a corporation to be sued if it reveals confidential information to a third party without the client’s agreement. Cyber hacking typically results in an inadvertent confidentiality violation. The following are the primary sources of confidentiality violations:</p><p>• Theft of employee laptops<br>• Leaving computers with confidential information unattended<br>• Providing unauthorized access to the unconcerned person<br>• Unauthorized access by hacker through malware<br>• Consulting company employees violating confidentiality agreements<br>• Unlawful use of information for personal or business gains</p><h3>Integrity</h3><p>Integrity is a method of defending the accuracy and dependability of data. Integrity protection stops unauthorized data changes. Integrity protection that is implemented correctly gives authorized users a way to make changes while guarding against malicious and intended unauthorized activities (like viruses and intrusions) as well as errors made by authorized users (like slip-ups or mistakes).</p><p>Throughout its lifecycle, information must maintain its integrity to remain accurate, consistent, and unaltered. It entails safeguarding data from unauthorized addition, deletion, or modification. Integrity controls try to keep data trustworthy and reliable.</p><p>Integrity is dependent on confidentiality and access control. Concepts, conditions, and aspects of integrity include the following:</p><ul><li>Accuracy: Being correct and precise.</li><li>Truthfulness: Being a true reflection of reality.</li><li>Validity: Being factually or logically sound.</li><li>Accountability: Being responsible or obligated for actions and results.</li><li>Responsibility: Being in charge or having control over something or someone.</li><li>Completeness: Having all necessary components or parts.</li><li>Comprehensiveness: Being complete in scope; the full inclusion of all needed elements.</li></ul><blockquote>The Framework</blockquote><p><strong>Who:</strong> Authorized people or groups with the right to view or alter particular data.</p><p><strong>What:</strong> Data that needs to be precise, constant, and unchanged.</p><p><strong>When: </strong>Creation, storage, retrieval, and modification phases of the complete data lifecycle.</p><p><strong>Where:</strong> Data repositories such as databases, file systems, or any storage medium.</p><p><strong>How: </strong>By implementing mechanisms such as data validation, checksums, digital signatures, and access controls to ensure data remains unaltered and trustworthy. Regular backups and recovery processes can also help restore data integrity if it is compromised.</p><p>Data integrity is frequently ensured with digital signatures. For instance, if a software package or document is later modified after being digitally signed (how) by a reputable party (who), the signature will no longer be legitimate. By doing this, users are informed if any unauthorized changes have been made and the data is kept intact.</p><p>Techniques for data validation can also be used to guarantee integrity. For example, websites frequently employ form validation (how) to guarantee that user-submitted data is in the right format and complies with predetermined standards. By preventing inaccurate or malicious input from impairing the system’s usability or security, this helps maintain the integrity of the data contained in the system (what).</p><blockquote>Breach</blockquote><p>For the duration of its storage on the service provider’s server, any data should remain true, consistent, and valid. Data is usually stored and transmitted in encrypted form to protect its secrecy. The formats of the data vary, but ultimately, the data should be accurate and useful.</p><p>Data integrity breach activities include all actions that compromise the consistency, validity, and correctness of the data. The data may be corrupted as a result of the integrity violation, rendering it useless. The following methods are used by hackers to compromise data integrity:</p><p>• Introduction of malware on the server<br>• Undoable malicious encryption of data<br>• Manipulation of original data<br>• Introduction of viruses<br>• Malicious insiders</p><h3>Availability</h3><p>Availability means authorized subjects are granted timely and uninterrupted access to objects. Often, availability protection controls support sufficient bandwidth and timeliness of processing as deemed necessary by the organization or situation. Availability includes<br>efficient uninterrupted access to objects and prevention of denial-of-service (DoS) attacks.</p><p>Availability ensures that information and systems are accessible and usable when needed by authorized users. It involves preventing disruptions, downtime, or denial-of-service attacks that could render data or systems inaccessible. Availability measures aim to ensure continuous operation and timely access to resources.</p><p>Availability depends on both integrity and confidentiality. Without integrity and confidentiality, availability cannot be maintained. Concepts, conditions, and aspects of availability include the following:</p><ul><li>Usability: The trait of being simple to use, simple to understand, or simple to comprehend and control by a subject.</li><li>Accessibility: The assurance that, regardless of their abilities or limitations, the broadest variety of subjects can interact with a resource.</li><li>Timeliness: Being prompt, on time, within a reasonable time frame, or providing low latency response.</li></ul><blockquote>The Framework</blockquote><p><strong>Who:</strong> Users with permission who need access to data or systems.</p><p><strong>What: </strong>Systems, applications, data, or resources that should be accessible and usable.</p><p><strong>When: </strong>Whenever authorized users need to access or utilize the resources.</p><p><strong>Where:</strong> Networks, servers, databases, or any infrastructure hosting the resources.</p><p><strong>How:</strong> By implementing measures such as redundancy, fault tolerance, load balancing, disaster recovery plans, and security measures to protect against downtime, system failures, or denial-of-service attacks. Regular maintenance, monitoring, and response mechanisms help ensure continuous availability.</p><p>To ensure availability, redundancy and failover strategies are frequently used. For instance, load balancing, where many servers are employed to spread incoming traffic (what), may be used by a high-availability website (how). The load balancer automatically sends requests to the remaining servers if one server fails, ensuring continuous access to the website (how).</p><p>Plans for disaster recovery are essential for availability. In the event of a natural disaster or system failure, for instance, a business may periodically back up its data and have a plan in place to quickly restore services. These backup and recovery procedures aid in limiting downtime and ensuring availability (what) by ensuring that crucial systems and data can be restored quickly.</p><blockquote>Breach</blockquote><p>When the authorized user is unable to access online services or personal information that he or she is authorized for, this is known as an availability breach. Availability breaches are when approved digital resources are denied access or made unavailable.<br>The primary malicious behaviors used to interfere with the services’ availability include DoS attacks or network intrusions are used to transmit information. Once the hacker successfully gains access to the network, he or she illegally takes control of the servers and prevents permitted access to the resources or services by the legitimate users.</p><p>The main sources of breach of availability may include the following:<br>• Failure of hardware<br>• Malfunction of software<br>• Choking of data bandwidth<br>• Redundant arrangement failures<br>• DoS attacks</p><p>In summary, confidentiality, integrity, and availability are essential aspects of security. They work together to protect information from unauthorized access, ensure data accuracy and reliability, and maintain uninterrupted access to resources. Organizations and individuals need to consider these principles while designing security measures to safeguard their systems and sensitive data.</p><p>Reference:</p><p>Cybersecurity Fundamentals A Real-World Perspective- Kutub Thakur</p><p>CISSP (ISC)2 Certified Information Systems Security Professional Official Study Guide-Mike Chapple, James Michael Stewart</p><blockquote>Let’s connect?</blockquote><blockquote>LinkedIn: <a href="http://www.linkedin.com/in/ravitejmbandlekar"><em>www.linkedin.com/in/ravitejmbandlekar</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b45b6305146e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Malware Exposed: Understanding the Menace of Virus its Patterns and Behaviors]]></title>
            <link>https://ravitejbandlekar.medium.com/malware-exposed-understanding-the-menace-of-virus-its-patterns-and-behaviors-7ea2d82210a9?source=rss-3d7b75a5b260------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ea2d82210a9</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[malware-analysis]]></category>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[network-security]]></category>
            <dc:creator><![CDATA[Ravitej Bandlekar]]></dc:creator>
            <pubDate>Wed, 12 Jul 2023 10:57:35 GMT</pubDate>
            <atom:updated>2023-07-12T10:57:35.654Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*1A-JcDzluC52-mpTp2BOGg.jpeg" /><figcaption>Source: arstechnica.com</figcaption></figure><p>Now that we have a good understand of malware and have looked at some real-world case studies, let’s go far into this fascinating topic. We shall reveal a wide range of characteristics and complexities in our continuous investigation of malicious software. Our focus will include an in-depth look of several malware types, including viruses, worms, and trojans, each having specific traits and ways of operation. We can better identify and reduce their hazards if we increase our understanding of these many forms of malware.</p><p>Prior to continuing with the current article, I recommend that you read the previous piece on malware, if you haven’t done so already.</p><p><a href="https://ravitejbandlekar.medium.com/malware-exposed-understanding-the-menace-of-malware-and-real-world-cases-2c7aaccecc78">Malware Exposed: Understanding the Menace of Malware and Real-World Cases</a></p><p>Let’s take a closer look at viruses and unravel their mysteries in this article.</p><h3>Virus</h3><p>A computer virus is code that recursively replicates a possibly evolved copy of itself. Viruses infect a host file or system area, or the simply modify reference to such objects to take control and then multiply again to form new generations.</p><p>Otherwise, it is a type of malicious software program that is designed to infect and spread within computer systems and networks. It is analogous to a biological virus that can replicate and spread from one host to another.</p><h4>A. File Virus</h4><p>A file virus is a type of malware that infects executable files on a computer system. When an infected file is executed, the virus code activates and starts replicating itself by infecting other files on the system. These viruses often attach themselves to legitimate program files, such as .exe, .com, or .dll files, and spread when those files are executed.</p><h4>Case:</h4><p>The “Melissa” virus, which emerged in 1999, was a file virus that infected Microsoft Word documents. When an infected document was opened, the virus replicated itself and sent infected emails to the first 50 contacts in the user’s Microsoft Outlook address book.</p><h4>B. Boot Sector Virus</h4><p>A boot sector virus infects the boot sector of a computer’s storage device, such as the Master Boot Record (MBR) or Volume Boot Record (VBR). When the infected device is booted, the virus is loaded into memory, enabling it to control the system and spread to other devices.</p><p>Otherwise, a boot sector virus is a type of computer virus that infects the boot sector of storage devices, such as floppy disks or hard drives. It typically targets the Master Boot Record (MBR) or the boot sector of a partition. When an infected storage device is accessed during the boot process, the virus code is executed, allowing the virus to load before the operating system.</p><p>The vulnerable stage where boot sector viruses can infect the system is during the process of loading the code from the first sector of the boot disk. This applies to both early systems booting from diskettes and newer systems booting from hard drives.</p><p>In early systems, where booting from diskettes was common, the boot sector virus could infect the diskette’s boot sector, which would execute the virus code when the system attempted to boot from the infected diskette. This was possible because the boot order was fixed and the system would automatically load the code from the diskette without any additional checks.</p><p>In newer systems with hard drives, the boot sector virus could infect the Master Boot Record (MBR) or the boot sector of a specific partition. The MBR contains code that runs during the boot process and helps locate the active boot partition. If the MBR or boot sector is infected, the virus code would be executed during the boot process, allowing the virus to gain control before the operating system loaded.</p><p>In both cases, the presence of a boot sector virus in the boot sector could allow the virus to load before the operating system and potentially cause harm, such as spreading to other storage devices or damaging data.</p><h4>Case:</h4><p>The “Stoned” virus, first discovered in 1987, was a boot sector virus that infected the boot sector of floppy disks. When an infected disk was inserted and the computer was booted from it, the virus loaded into memory and infected the computer’s hard drive.</p><h4>C. Macro Virus</h4><p>A macro virus infects documents and spreadsheets that support macros, such as Microsoft Word or Excel files. These viruses embed their malicious code within the macro programming language, and when a file containing the virus is opened, the code is executed, allowing the virus to spread.</p><h4>Case:</h4><p>Today there are thousands of macro viruses, and many of them are in the wild. Users often exchange documents that were created with a Microsoft Office product such as Word, Excel, PowerPoint, Visio, or even Access or Project. The first wild-spread macro virus, WM/Concept.A17, appeared in late 1995. Within a couple of months, only a few dozen such viruses were found, but by 1997 there were thousands of similar creations. The XM/Laroux18, discovered in 1996, was the first wild-spread macro virus to infect Excel spreadsheets. The first known Word macro virus was WM/DMV, written in 1994. The author of the WM/DMV virus also created a nearly functional Excel macro (XM) virus at the same time.</p><h4>D. Source Code Virus</h4><p>A source code virus inserts its own code into the source code of the application it has infected. As a result, when the compromised software is built or run, the virus code is also run, enabling further virus spread. As each infected software becomes a carrier for the virus, possibly infecting additional systems, this sort of infection can spread quickly. Because they can infect numerous programs and can be difficult to find and eliminate, source code viruses can be highly harmful. They may carry out a number of malicious acts, including stealing confidential data, corrupting files or data, or granting unauthorized access to the infected system.</p><h4>Case:</h4><p>The “W32/SQLSlammer” virus, discovered in 2003, targeted Microsoft SQL Server databases. It exploited a vulnerability in the server software and spread rapidly, causing widespread internet congestion and disrupting services.</p><h4>E. Memory-Resident Virus</h4><p>Malware known as memory-resident viruses can infect other computer files without even being executed by becoming embedded in the machine’s memory. By loading its replication module into the RAM, it accomplishes this. The memory-resident virus is one of the worst kinds of computer viruses because the operating system might activate it whenever it loads or executes operations. It can affix to antivirus software, impact the overall system, and obstruct normal operation.</p><p>The typical work of this virus.</p><p>1. The virus gets control of the system.<br>2. It allocates a block of memory for its own code.<br>3. It relocates its code to the allocated block of memory.<br>4. It activates itself in the allocated memory block.<br>5. It hooks the execution of the code flow to itself.<br>6. It infects new files and/or system areas</p><h4>Case:</h4><p>he “CIH” or “Chernobyl” virus, discovered in 1998, infected executable files and the system’s BIOS. On specific dates, it triggered destructive payloads that could render the infected system inoperable by overwriting critical system files or corrupting the BIOS.</p><h4>F. Swapping Virus</h4><p>Another unusual method of creating computer viruses involves constantly putting a little amount of infection code into memory. Possibly, this tiny line of code represents a hook event. The virus loads a section of viral code from the disk and infects a new object each time the hook event is triggered. The virus then erases the loaded section from memory once more.<br>Although it seems like this technique has some benefits, such as the fact that the virus uses less physical memory and can typically keep its code encrypted in files, there are also a lot of drawbacks. For example, it’s possible to introduce significantly increased disk activity, which makes it much easier to detect the attack.</p><h4>G. Tunneling Virus</h4><p>Based on Self-Protecting strategies, a tunneling virus attempts to bypass security measures by creating a covert communication channel, or “tunnel,” between an infected system and an external command-and-control server. This allows the attacker to remotely control the infected system and potentially exfiltrate data.</p><p>This virus attempts to bypass detection by antivirus scanner by installing itself in the interrupt handler chain. Interception programs, which remain in the background of an operating system and catch viruses, become disabled during the course of a tunneling virus. Similar viruses install themselves in device drivers.</p><p>Memory-resident viruses are a type of malicious software that stay in your computer’s memory to hide and carry out their harmful actions. One way they try to avoid detection is by using a technique called tunneling. Imagine a line of people waiting to talk to someone, and each person represents a program or application in your computer.</p><p>The resident tunneling virus tries to be the first person in line so that it can control the conversation. It does this by installing itself at the front of the line, before other programs. When a specific action, called an interrupt, occurs, the virus jumps in and takes control before any other program can respond. It then pretends to be the original program and carries out its malicious activities.</p><p>The goal of the virus is to bypass antivirus programs that are designed to monitor and stop malicious software. By being the first in line and taking control, the virus can execute its own code without being detected by the antivirus software.</p><p>This technique can be used by both resident (stays in memory) and nonresident (not in memory) viruses, but it is commonly used by memory-resident viruses to locate the original program handler and call it directly, allowing the virus to go unnoticed by antivirus programs.</p><h4>Case:</h4><p>The “Zeus” Trojan, discovered in 2007, infected computers and established a hidden communication channel with a command-and-control server. This allowed attackers to remotely control infected systems, steal sensitive information, and initiate fraudulent transactions.</p><h4>H. Armored Virus</h4><p>The term armored virus was coined by the computer crime unit of New Scotland Yard to describe computer viruses that make it even more difficult to detect and analyze their functions quickly. A computer virus’s primary goal is to spread as far as possible without being noticed. The authors of armored viruses want to be sure that the virus code is even more difficult for scanners to detect, even if the scanners use techniques such as<br>heuristics that can pinpoint previously unknown computer viruses.</p><p>Furthermore, if a virus sample is obtained by any means, its author wants to make the analysis of the virus code as difficult as possible to further delay rapid response to the virus attack.</p><p>The following techniques are used by threat actors to armor the virus.<br>■ <strong>Anti disassembly</strong>-Computer viruses written in Assembly language are challenging to understand because they often use tricks that normal programs never or very rarely use.<br>■ <strong>Anti debugging-</strong> Attackers can use a number of tricks as Anti debugging features. The attacker’s goal is to prevent you from using a debugger easily. Because hardware supports debugging, the Anti debug features can be rather platform specific.</p><p>■ <strong>Anti heuristics and Anti emulation</strong>- In 1998, Windows virus development was in a relatively early stage. This is why a wide variety of different infection methods were introduced, making it possible to consider heuristic analysis against 32-bit Windows viruses. Heuristic analysis can<br>detect unknown viruses and closely related variants of existing viruses using static and dynamic methods. Static heuristics rely on file format and common code fragment analysis. Dynamic heuristics use code emulation to mimic the processor and the operating system environment and detect suspicious operations as the code is “running” in the virtual machine of the scanner. Virus writers developed Anti heuristic and Anti emulation techniques to fight back against heuristic analyzers.</p><p>■ Antigoat- A goat file is an <a href="https://www.yourdictionary.com/executable">executable</a> <a href="https://www.yourdictionary.com/file">file</a> with a known <a href="https://www.yourdictionary.com/structure">structure</a> and/or <a href="https://www.yourdictionary.com/file-size">file size</a> , designed to be infected by a file-infecting <a href="https://www.yourdictionary.com/computer-virus">computer virus</a> in order to <a href="https://www.yourdictionary.com/facilitate">facilitate</a> the study of such.</p><p>The infection of goat files facilitates virus analysis since it visibly distinguishes the virus body from the known file content. The goat files often have do-nothing instructions (like NOPs) and return the operating system to its default state without doing any additional tasks. For different types of viruses, goat files are made with a variety of file formats and internal architecture. For instance, a collection of goat files with sizes of 4, 8, 16, or 32 KB is produced.</p><p>Antigoat viruses use heuristic rules to detect possible goat files. For example, a virus might not infect a file if it is too small or if it contains a large number of do-nothing instructions, or if the filename contains numbers.</p><h4>I. Encrypted Virus</h4><p>From the very early days, virus writers tried to implement virus code evolution. One of the easiest ways to hide the functionality of the virus code was encryption. An encrypted virus encrypts its malicious code, making it difficult for antivirus software to detect or analyze them. The virus decrypts itself when executed, allowing it to infect the system.</p><h4>J. Oligomorphic Virus</h4><p>infection creators rapidly learned that as long as the decryptor’s code is lengthy and distinctive enough, antivirus software can still easily detect an encrypted virus. They made the decision to use methods to produce mutant decryptors in order to further test the antiviral software. Oligomorphic viruses do alter their decryptors in new generations, unlike viruses that are encrypted. Using a set of decryptors rather than just one makes changing the decryptors the simplest process possible. Whale was the first virus to be discovered to employ this method. The virus chose one of the many dozen distinct decryptors that Whale was carrying at the time.</p><h4>K. Polymorphic viruses</h4><p>Polymorphic viruses can mutate their decryptors to a high number of different instances that can take millions of different forms. A polymorphic virus is designed to change its code or appearance with each infection. This makes it difficult for antivirus software to detect them using traditional signature-based detection methods.</p><h4>Case:</h4><p>The “Storm Worm” or “Nuwar” virus, observed in 2007, was a polymorphic email worm that used social engineering techniques to entice users to open infected email attachments. Its constantly changing code made it difficult to detect and eliminate.</p><p>To ensure our safety and mitigate the potential consequences of different types of malware, it is crucial to maintain a state of alertness and implement necessary precautions. This involves regularly updating our software, employing reputable antivirus programs, and exercising caution when dealing with attachments or clicking on suspicious links. By staying vigilant, individuals can effectively shield themselves from these potential threats.</p><h3>Reference:</h3><p>The Art of Computer Virus Research and Defense- Peter Szor</p><p>Let’s connect?</p><p>LinkedIn: <a href="http://www.linkedin.com/in/ravitejmbandlekar"><em>www.linkedin.com/in/ravitejmbandlekar</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ea2d82210a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>