<?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"><channel><title><![CDATA[My notes]]></title><description><![CDATA[Artikel about IT Infrastructure, Network, Server, Cyber Security, Endpoint, Cloud, Storage]]></description><link>https://rmadhi.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 13:22:52 GMT</lastBuildDate><atom:link href="https://rmadhi.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[OSI Model – 7 Layers (Open Systems Interconnection)]]></title><description><![CDATA[Networking, OSI model 7 layer]]></description><link>https://rmadhi.hashnode.dev/osi-model-7-layers-open-systems-interconnection</link><guid isPermaLink="true">https://rmadhi.hashnode.dev/osi-model-7-layers-open-systems-interconnection</guid><category><![CDATA[networking]]></category><category><![CDATA[OSI Model]]></category><dc:creator><![CDATA[Rmadhi]]></dc:creator><pubDate>Sat, 14 Nov 2026 12:33:02 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6af80af797fffc20d7ebb646/266d1324-1726-43a2-b069-a1f31b5f420e.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h1><mark>Introduction</mark></h1>
<p>The <strong>OSI Model (Open Systems Interconnection Model)</strong> is a reference model that explains how data is transmitted, received, and processed between devices over a network.</p>
<p>The OSI Model divides the network communication process into <strong>seven layers (layers)</strong>. Each layer has its own functions, responsibilities, protocols, and mechanisms, but all layers work together to enable communication between devices.</p>
<p>The model was developed by the <strong>ISO (International Organization for Standardization)</strong> to establish standardized communication principles, allowing devices from different vendors to communicate with one another.</p>
<p><strong>Examples include:</strong></p>
<ul>
<li>Windows computers communicating with Linux servers.</li>
<li>Cisco switches communicating with MikroTik routers.</li>
<li>Laptops accessing web applications hosted on cloud servers.</li>
<li>IoT devices in OT networks communicating with monitoring servers.</li>
</ul>
<p>All these communication processes can be understood using the OSI Model.</p>
<h1><mark>Overview of the OSI Model</mark></h1>
<img src="https://cdn.hashnode.com/uploads/covers/6af80af797fffc20d7ebb646/11e5ecbd-c0d0-4b21-bff6-db9c3c240bad.png" alt="" style="display:block;margin:0 auto" />

<p><strong>Layer 7 – Application</strong></p>
<p>Function : Network services for applications</p>
<p>Standard : HTTP, HTTPS, DNS, SMTP, FTP</p>
<p><strong>Layer 6 – Presentation</strong></p>
<p>Function : Data formatting, encryption, and compression</p>
<p>Standard : TLS/SSL, JPEG, JSON, UTF-8</p>
<p><strong>Layer 5 – Session</strong></p>
<p>Function : Management of communication sessions</p>
<p>Standard : RPC, NetBIOS, session management</p>
<p><strong>Layer 4 – Transport</strong></p>
<p>Function : End-to-end data transmission</p>
<p>Standard : TCP, UDP</p>
<p><strong>Layer 3 – Network</strong></p>
<p>Function : IP addressing and routing</p>
<p>Standard : IPv4, IPv6, ICMP, routing protocols</p>
<p><strong>Layer 2 – Data Link</strong></p>
<p>Function : Frames, MAC addresses, and switching</p>
<p>Standard : Ethernet, Wi-Fi MAC, VLAN, STP</p>
<p><strong>Layer 1 – Physical</strong></p>
<p>Function : Transmission of bits through physical media</p>
<p>Standard : UTP, Fiber Optic, radio, electrical signals</p>
<p>Data moves from Layer 7 to Layer 1 during transmission, and from Layer 1 to Layer 7 during reception.</p>
<h2><strong><mark>OSI Layer Categories</mark></strong></h2>
<p>The OSI Model can generally be divided into three groups:</p>
<table style="min-width:75px"><colgroup><col style="min-width:25px"></col><col style="min-width:25px"></col><col style="min-width:25px"></col></colgroup><tbody><tr><td><p><strong>Category</strong></p></td><td><p><strong>Layers</strong></p></td><td><p><strong>Focus</strong></p></td></tr><tr><td><p>Application-oriented</p></td><td><p>7, 6, 5</p></td><td><p>Services and data processing</p></td></tr><tr><td><p>Transport</p></td><td><p>4</p></td><td><p>End-to-end communication</p></td></tr><tr><td><p>Network-oriented</p></td><td><p>3, 2, 1</p></td><td><p>Data transmission across networks</p></td></tr></tbody></table>

<h2><strong><mark>Protocol Data Unit (PDU)</mark></strong></h2>
<p>Each layer has its own terminology for the data unit being processed.</p>
<table style="min-width:50px"><colgroup><col style="min-width:25px"></col><col style="min-width:25px"></col></colgroup><tbody><tr><td><p><strong>Layer</strong></p></td><td><p><strong>PDU</strong></p></td></tr><tr><td><p>Layers 7–5</p></td><td><p>Data</p></td></tr><tr><td><p>Layer 4</p></td><td><p>Segment (TCP) / Datagram (UDP)</p></td></tr><tr><td><p>Layer 3</p></td><td><p>Packet</p></td></tr><tr><td><p>Layer 2</p></td><td><p>Frame</p></td></tr><tr><td><p>Layer 1</p></td><td><p>Bits</p></td></tr></tbody></table>]]></content:encoded></item><item><title><![CDATA[MikroTik RouterOS Initial Configuration]]></title><description><![CDATA[Mikrotik configuration, Setting Mikrotik, Mikrotik router OS initial configuration.]]></description><link>https://rmadhi.hashnode.dev/mikrotik-routeros-initial-configuration</link><guid isPermaLink="true">https://rmadhi.hashnode.dev/mikrotik-routeros-initial-configuration</guid><category><![CDATA[network]]></category><category><![CDATA[#Mikrotik]]></category><dc:creator><![CDATA[Rmadhi]]></dc:creator><pubDate>Sat, 14 Nov 2026 11:02:46 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6af80af797fffc20d7ebb646/aa15cdd5-3c93-4ce1-9162-4413341fd1d6.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h1><mark>First time accessing the router</mark></h1>
<ol>
<li>Download Winbox &amp; click Winbox.</li>
<li>Go to “Neighbors” menu.</li>
<li>Enter “192.168.88.1” as default IP Mikrotik Router in Connect to field, enter “admin” in Login field, and leave password field blank. And click Connect.</li>
</ol>
<h2><mark>Change User &amp; Password</mark></h2>
<ol>
<li>On Winbox, go to System -&gt; User -&gt; click admin user.</li>
<li>Click Password section</li>
</ol>
<p>If using Terminal : Type this into terminal= “<em><strong>/user set admin password="YourNewPassword"</strong></em>” Or if want to add new user via terminal = “<em><strong>/user add name=admin2 password= "YourPassword" group=full</strong></em>”</p>
<h2><mark>Change Hostname</mark></h2>
<ol>
<li>On Winbox go to System -&gt; Identity</li>
<li>type hostname in the field, and OK If using Terminal : Type = “<em><strong>/system identity set name="NewHostnameForRouter"</strong></em>”</li>
</ol>
<h2><mark>Set NTP</mark></h2>
<ol>
<li>Verify the current situation, “<em><strong>/system clock print</strong></em>” and “<em><strong>/system ntp client print</strong></em>”</li>
<li>Set time zone to our country, for example change to Indonesia time (WIB) : “<em><strong>/system clock set time-zone-name=Asia/Jakarta</strong></em>”</li>
<li>Configure NTP :<br /><em><strong>/system ntp cliecnt set enabled=yes</strong></em><br /><em><strong>/system ntp cliecnt servers add</strong></em> <a href="http://address=id.pool.ntp.org"><em><strong>address=id.pool.ntp.org</strong></em></a><br /><em><strong>/system ntp cliecnt servers add</strong></em> <a href="http://address=time.google.com"><em><strong>address=time.google.com</strong></em></a><br /><strong>For older version :</strong><br /><em><strong>/system ntp client set enabled=yes primary-ntp=IPNTP</strong></em> //for Indonesian can type 203.160.128.3 for Indonesia’s NTP</li>
<li>If on GUI can go to System -&gt; NTP Client</li>
<li>If want to change the clock, we can go to System -&gt; Clock</li>
<li>If wanto to change the clock via Terminal, we can type= “<em><strong>/system clock set date=2026-10-10 time=14:30:00</strong></em>”</li>
</ol>
<h2><mark>Upgrade RouterOS</mark></h2>
<ol>
<li>Check current version of Router OS GUI : System -&gt; Resources -&gt; Version section CLI : /system resource print</li>
<li>Backup first GUI : Files -&gt; Backup CLI : <em><strong>/system backup save name=backup-before-upgrade</strong></em> and <em><strong>/export file=config-before-upgrade</strong></em></li>
<li>Upgrade Router OS GUI : System -&gt; Packages -&gt; Check for Updates CLI : /system package update install , before can check : <em><strong>/system package update check-for-updates</strong></em> and then <em><strong>/system package update set channel=stable</strong></em></li>
<li>Verifiy : <em><strong>/system resource print</strong></em> <em>;</em> <em><strong>/system package print</strong></em> <em>;</em> <em><strong>/log print</strong></em></li>
</ol>
]]></content:encoded></item><item><title><![CDATA[IAM Introduction]]></title><description><![CDATA[About IAM, IAM introduction, IAM concept]]></description><link>https://rmadhi.hashnode.dev/iam-introduction</link><guid isPermaLink="true">https://rmadhi.hashnode.dev/iam-introduction</guid><category><![CDATA[IAM]]></category><category><![CDATA[cybersecurity]]></category><dc:creator><![CDATA[Rmadhi]]></dc:creator><pubDate>Sat, 14 Nov 2026 09:42:05 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6af80af797fffc20d7ebb646/589e5208-62b6-423f-b8c2-4141e9187447.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><strong>IAM</strong> (Identity and Access Management) is a framework of policies, processes, and technologies in cybersecurity that ensures the <strong>right entities</strong> (humans, devices, or applications) have the <strong>right access</strong> to the <strong>right system resources</strong> at the right time and for legitimate reasons.</p>
<p>In modern cybersecurity, IAM serves as the primary line of defense, shifting the focus of protection from mere physical network perimeters to identity management and verification.</p>
<h2><strong><mark>Four Core Pillars of How IAM Works</mark></strong></h2>
<ul>
<li><strong>Identification:</strong> The process of recognizing and registering an entity's unique identity within a system, such as through a username, email address, or machine ID.</li>
<li><strong>Authentication (AuthN):</strong> The process of verifying that a user is truly who they claim to be, commonly using passwords, passkeys, biometrics, or digital certificates.</li>
<li><strong>Authorization (AuthZ):</strong> The process of determining access privileges and restrictions after successful authentication—governing which data, applications, or commands can be accessed, modified, or deleted.</li>
<li><strong>Accountability &amp; Auditing:</strong> Recording all login histories and access privilege usage activities into system logs for forensic investigation and regulatory compliance (such as ISO 27001 or Personal Data Protection laws).</li>
</ul>
<h2><strong><mark>Key Concepts and Features in IAM</mark></strong></h2>
<ul>
<li><strong>Multi-Factor Authentication (MFA):</strong> Requiring more than one identity verification method (such as a combination of a password and an authenticator app) to prevent account takeover even if a password is compromised.</li>
<li><strong>Single Sign-On (SSO):</strong> Allowing users to log in once to access multiple integrated applications without having to re-enter credentials repeatedly.</li>
<li><strong>Principle of Least Privilege (PoLP):</strong> A security principle that restricts user access rights to the bare minimum, limited strictly to what is required to perform their job.</li>
<li><strong>Role-Based Access Control (RBAC):</strong> Managing access permissions based on a user's job title or role within an organization (e.g., <em>Admin</em>, <em>Manager</em>, or <em>Viewer</em> roles).</li>
<li><strong>Privileged Access Management (PAM):</strong> Dedicated management, monitoring, and restriction of accounts with high-level access privileges (such as server <em>root</em> accounts or system administrators).</li>
</ul>
<h3><em>Popular IAM platform examples:</em></h3>
<p>Microsoft Entra ID (formerly Azure AD), Okta, AWS IAM, Google Cloud IAM, CyberArk (PAM specialist), and Keycloak (open-source).</p>
<p>A mature IAM implementation serves as the core foundation of a <strong>Zero Trust</strong> security architecture (<em>never trust, always verify</em>), while significantly reducing the risk of data breaches caused by credential theft or misuse.</p>
]]></content:encoded></item><item><title><![CDATA[SIEM & SOAR Introduction]]></title><description><![CDATA[SIEM and SOAR, about SIEM, about SOAR]]></description><link>https://rmadhi.hashnode.dev/siem-soar-introduction</link><guid isPermaLink="true">https://rmadhi.hashnode.dev/siem-soar-introduction</guid><category><![CDATA[SIEM]]></category><category><![CDATA[soar]]></category><category><![CDATA[cybersecurity]]></category><dc:creator><![CDATA[Rmadhi]]></dc:creator><pubDate>Sat, 14 Nov 2026 09:24:41 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6af80af797fffc20d7ebb646/498972da-c53c-40fa-b44a-225af348735f.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h1><mark>SIEM (Security Information and Event Management)</mark></h1>
<p><strong>SIEM</strong> combines two primary functions: <strong>SIM</strong> (Security Information Management — long-term log storage and analysis) and <strong>SEM</strong> (Security Event Management — real-time event monitoring and correlation).</p>
<p><strong>SIEM</strong> is responsible for detecting threats by collecting and analyzing log data</p>
<h2>The core workflows of SIEM include:</h2>
<p><strong>Log Collection &amp; Aggregation:</strong> Gathering logs and telemetry from across infrastructure devices—such as firewalls, routers, switches, servers, endpoints, applications, and cloud services (typically via Syslog, APIs, or agents).</p>
<p><strong>Normalization &amp; Parsing:</strong> Standardizing disparate log formats from various vendors into a unified data structure for easier analysis.</p>
<p><strong>Event Correlation &amp; Threat Detection:</strong> Connecting thousands of separate events using correlation rules or machine learning to identify attack patterns. For example, 50 failed SSH login attempts from a single external IP within one minute followed by one successful login will trigger a brute-force alert.</p>
<p><strong>Alerting &amp; Compliance Reporting:</strong> Sending alerts to the security team when anomalies are detected, while maintaining audit trails for forensic investigations and regulatory compliance (such as ISO 27001, PCI-DSS, or Personal Data Protection Law / UU PDP).</p>
<h2>Popular platform examples:</h2>
<p>Splunk Enterprise Security, Microsoft Sentinel, IBM QRadar, Elastic Security, and Wazuh (open-source).</p>
<h1><mark>SOAR (Security Orchestration, Automation, and Response)</mark></h1>
<p>SOAR is designed to address the problem of alert fatigue (analyst burnout caused by an overwhelming volume of alerts from SIEM) by accelerating incident investigation and mitigation processes. SOAR is responsible for responding to those threats automatically through programmed workflows (playbooks).</p>
<h2>The three core pillars of SOAR:</h2>
<p><strong>Security Orchestration:</strong> Connecting disparate security tools and applications (SIEM, firewalls, Threat Intelligence, EDR, and ticketing systems like Jira or ServiceNow) via APIs so they can operate under unified control.</p>
<p><strong>Security Automation:</strong> Executing repetitive investigation and mitigation steps without human intervention using Playbooks (automated workflows based on if-then logic).</p>
<p><strong>Incident Response:</strong> Providing a case management workspace for SOC teams to collaborate, track attack timelines, and document incident handling in a structured manner.</p>
<h2>Popular platform examples:</h2>
<p>Palo Alto Cortex XSOAR, Splunk SOAR, Fortinet FortiSOAR, Swimlane, and Shuffle (open-source).</p>
]]></content:encoded></item></channel></rss>