<?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 Dolly Aswin Harahap on Medium]]></title>
        <description><![CDATA[Stories by Dolly Aswin Harahap on Medium]]></description>
        <link>https://medium.com/@dollyaswin?source=rss-e67ce73e2cd7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5ETrfykMKta8uBHjdCd4oA.png</url>
            <title>Stories by Dolly Aswin Harahap on Medium</title>
            <link>https://medium.com/@dollyaswin?source=rss-e67ce73e2cd7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:34:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dollyaswin/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[Generative AI Leader Certification Preparation Guide Through the Google Gear Get Certified Program]]></title>
            <link>https://medium.com/@dollyaswin/generative-ai-leader-certification-preparation-guide-through-the-google-gear-get-certified-program-8acc12aa0219?source=rss-e67ce73e2cd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/8acc12aa0219</guid>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[generative-ai-solution]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[ai-agent-development]]></category>
            <category><![CDATA[ai-certification]]></category>
            <dc:creator><![CDATA[Dolly Aswin Harahap]]></dc:creator>
            <pubDate>Tue, 14 Jul 2026 11:05:04 GMT</pubDate>
            <atom:updated>2026-07-14T11:05:04.034Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8R0xzalyL24Shn-X1V_w2A.png" /><figcaption>Google Cloud Certified Generative AI Leader Certificate</figcaption></figure><p>In February 2026, I enrolled in <a href="https://developers.google.com/program/gear/getcertified">Google’s Gear Get Certified</a> program. This program offers three certification options: <a href="https://cloud.google.com/learn/certification/generative-ai-leader">Generative AI Leader (GAIL), Associate Cloud Engineer (ACE)</a>, and <a href="https://cloud.google.com/learn/certification/cloud-architect?utm_source=aqilix.com&amp;utm_medium=blog">Professional Cloud Architect (PCA)</a>. Since I had just <a href="https://medium.com/google-cloud/renewing-google-cloud-professional-cloud-architect-certification-2026-96682f4131dd">passed the Professional Cloud Architect renewal exam in early 2026,</a> I chose the Generative AI Leader track in this program to broaden my competency. While this certification isn’t professional-level, it validates my Generative AI skills. This validation specifically covers the ability to develop AI applications, from creating AI agents and mastering prompting techniques to deploying and maintaining AI models in the Google Cloud ecosystem.</p><p>Some time later, the program announced that I had been selected as a participant. This participation provided financial benefits, including a waiver of the certification exam fee. For your information, the Generative AI Leader certification exam has an official fee of $99 for participants outside the program.</p><p>The exam preparation process in this program is designed as a four-week guided learning program. During this period, the participants from this program received technical mentorship from a dedicated coach. This mentorship took the form of three online exam guide review sessions and one in-person session with a technical mentor via Google Meet. Each session had a predetermined content and structure, starting with a kick-off meeting, followed by a guide review, and then two follow-up sessions focused on analyzing the exam material. In addition to these virtual face-to-face sessions, I also received full support through the online community throughout the four-week program.</p><p>In addition to attending meetings and discussions within the community, I studied the material through the Generative AI Leader learning path on the <a href="https://www.skills.google/paths/1951">Google Skills</a> platform. The learning modules and quizzes available on the platform made it easier for me to grasp the core concepts. I also made the official <a href="https://services.google.com/fh/files/misc/generative_ai_leader_exam_guide_english.pdf">Google Study Guide</a> a mandatory reading material.</p><p>To test my understanding, I worked through various practice questions provided. Furthermore, I applied the same self-study strategy I used when preparing for the <a href="https://medium.com/google-cloud/renewing-google-cloud-professional-cloud-architect-certification-2026-96682f4131dd#9697">Professional Cloud Architect renewal exam</a>. I used Gemini to design an interactive mock exam specifically for the Generative AI Leader material. The combination of technical guidance from mentors, community discussions, official materials, and this self-study mock exam proved extremely helpful in passing this certification exam!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fOhoh5EpMGd0MGgH8v9GyA.png" /><figcaption>Mock exam created by Gemini</figcaption></figure><p>This experience provided me with valuable technical insights, particularly in understanding the application of Generative AI in the cloud ecosystem. I hope these notes will help you plan and prepare for similar certification exams. If you have any questions about the exam process or would like to discuss further the integration of artificial intelligence into IT infrastructure, please leave a comment in the comments section. You can also connect with me on <a href="https://www.linkedin.com/in/dollyaswin/">LinkedIn</a> to exchange information and experiences professionally.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8acc12aa0219" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Renewing Google Cloud Professional Cloud Architect Certification (2026)]]></title>
            <link>https://medium.com/google-cloud/renewing-google-cloud-professional-cloud-architect-certification-2026-96682f4131dd?source=rss-e67ce73e2cd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/96682f4131dd</guid>
            <category><![CDATA[google-cloud-professional]]></category>
            <category><![CDATA[google-cloud-plaform]]></category>
            <category><![CDATA[google-cloud-certified]]></category>
            <category><![CDATA[cloud-professional]]></category>
            <category><![CDATA[google-cloud-architect]]></category>
            <dc:creator><![CDATA[Dolly Aswin Harahap]]></dc:creator>
            <pubDate>Sat, 21 Feb 2026 02:22:00 GMT</pubDate>
            <atom:updated>2026-02-22T07:02:19.762Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YuIxqKDWQgcIRE5mw-Jr7w.png" /><figcaption>Professional Cloud Architect Certificate Renewal</figcaption></figure><p>I’ve held the Google Cloud Professional Cloud Architect certification since <a href="https://medium.com/google-cloud/pass-the-google-cloud-professional-cloud-architect-exam-2024-1f391ec16515">January 2024</a>. As we know, the Google Cloud Professional certification is valid for two years. Last January, my certificate expired. Fortunately, Google Cloud provided a one-month grace period for certificate holders to renew their certificate before it expired.</p><p>Here, I’ll share my experience taking the renewal exam, including the cost, exam format, and the latest material tested.</p><h3>Renewal Fee</h3><p>One of the advantages of the renewal exam is that it’s much more affordable than the initial certification exam. The base price for the Google Cloud Professional Cloud Architect Renewal is $100. However, there’s a way to get a much lower price.</p><p>During checkout, the system automatically applied a 40% discount. I didn’t stop there, taking advantage of my certification benefits by using the 50% OFF voucher code from Google Cloud Certified Benefits.</p><p>With the accumulated discount, I ended up paying just $30 for this renewal exam. I chose the online proctored method so I could take the exam from the comfort of my own home.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xAU8mIlXP2A-Osjn4Bl2Rw.png" /><figcaption>The total payment for this renewal exam.</figcaption></figure><h3>Exam Format</h3><p>The renewal exam format differs significantly from the initial certification exam. While the new certification exam consists of 50 to 60 questions and lasts 120 minutes (2 hours), the renewal exam is designed to be more concise.</p><p>The renewal exam consists of only 25 questions that must be completed within 60 minutes (1 hour). Despite the smaller number of questions, each question demands in-depth understanding, making time for each question extremely valuable.</p><h3>Exam Focus</h3><p>The most crucial aspect to note is the change in focus of the <a href="https://services.google.com/fh/files/misc/professional_cloud_architect_renewal_exam_guide_eng.pdf">exam material</a>. In the 2026 version of the exam, there is a significant shift in topics, divided as follows:</p><h4>~60% Traditional PCA Foundations</h4><p>This section tests a core understanding of cloud architecture, including:</p><ul><li><strong>Compute Strategy:</strong> The ability to select the right computing service, such as distinguishing between using GKE Autopilot (for operational simplicity), Cloud Run (for scaling-to-zero scenarios), or Compute Engine (for legacy or specific needs).</li><li><strong>Networking:</strong> Designing complex networks using Shared VPCs, Private Service Connect, and hybrid connectivity (Interconnect/VPN).</li><li><strong>Security:</strong> Applying IAM least-privilege principles, using VPC Service Controls, and encryption with Cloud KMS.</li><li><strong>Data: </strong>Migration strategies from RDBMS to Spanner for global scale or BigQuery for analytics.</li></ul><h4>~40% Modern Services &amp; AI Focus</h4><p>A significant portion is now dedicated to generative AI technologies:</p><ul><li><strong>Vertex AI &amp; Gemini:</strong> Deployment of the Gemini Cloud Assist architecture, use of Model Garden to select foundation models, and implementation of the Vertex AI Agent Builder.</li><li><strong>AI Governance:</strong> Responsible AI principles, human-in-the-loop patterns, and securing AI workloads (e.g., using Sensitive Data Protection on input prompts).</li><li><strong>Observability:</strong> Use of Operations Suite (formerly Stackdriver) with a focus on Gemini in Security features for faster incident response.</li></ul><h3>Preparation Strategy</h3><p>To tackle this new material, I prepared using two main methods:</p><p>First, I did hands-on practice through <a href="https://partner.skills.google/paths/1834">Google Skills</a>. Google Cloud provides a dedicated learning path for this exam preparation. This material was very helpful in refreshing my technical understanding.</p><p>Second, I used <a href="https://gemini.google.com/">Gemini</a> as a study partner. I asked Gemini to create specific mock practice questions based on a case study from 2026. This method was very effective in testing my understanding of AI implementation scenarios and modern architectures that might appear on the exam.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cguB5zuaWvOzLa7ZShj0Bg.png" /><figcaption>Mock exam created by Gemini</figcaption></figure><h3>Mental and Environmental Preparation</h3><p>In addition to material preparation, technical preparation on exam day is also crucial. Make sure you have a quiet room, a desk free of prohibited items, and a stable internet connection for a smooth online proctoring process.</p><p>Finally, don’t forget to pray a lot. I believe that for those of you who use <a href="https://console.cloud.google.com/">Google Cloud Platform</a> in your daily work, you will be able to answer the questions on this exam well. Field experience will greatly assist your instincts in choosing the most architecturally correct answers.</p><p>I hope this experience is helpful for those of you who are renewing your certification. Let’s discuss and share study strategies in the comments section. You can also connect with me on <a href="https://www.linkedin.com/in/dollyaswin/">LinkedIn</a> to exchange ideas about cloud architecture, cybersecurity, and real-world AI implementations.</p><p>Happy studying and good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96682f4131dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/renewing-google-cloud-professional-cloud-architect-certification-2026-96682f4131dd">Renewing Google Cloud Professional Cloud Architect Certification (2026)</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cybersecurity in Google Cloud and Incident Case Studies]]></title>
            <link>https://medium.com/google-cloud/cybersecurity-in-google-cloud-and-incident-case-studies-5d94261e5470?source=rss-e67ce73e2cd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d94261e5470</guid>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[gcp-certification]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[gcp-security-operations]]></category>
            <dc:creator><![CDATA[Dolly Aswin Harahap]]></dc:creator>
            <pubDate>Wed, 31 Dec 2025 14:50:13 GMT</pubDate>
            <atom:updated>2026-01-05T02:38:13.979Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*l-fMSIoygkh1SwJ3yjvang.png" /><figcaption>Google Cloud Cybersecurity Certificate</figcaption></figure><p>In today’s era of digital transformation, data has become a company’s most valuable asset. However, with increasing reliance on technology, the risk of cyberattacks is also increasing. This article will discuss the fundamentals of cybersecurity, the urgency of mastering security on <a href="https://cloud.google.com/?utm_source=aqilix.com">Google Cloud Platform (GCP)</a>, and analyze a case study to understand how a small vulnerability can lead to a massive data disaster.</p><h4>What Is Cybersecurity and Why Do We Need It?</h4><p>In general, cybersecurity is the practice of protecting systems, networks, and programs from attacks. These attacks typically aim to access, alter, or destroy sensitive information, extort money from users (such as ransomware), or disrupt business processes. Cybersecurity is necessary because the threat landscape has changed. Companies no longer to store data solely on physical servers in their own data centers. Data is now accessed across global networks. Without a robust cybersecurity strategy, companies face the risk of significant financial losses, loss of customer trust, and severe regulatory sanctions. Cybersecurity for a company is no longer merely an add-on; it is fundamental to business continuity.</p><h4>Why Do We Need to Learn Cybersecurity in Google Cloud?</h4><p>Moving to cloud computing doesn’t mean security responsibilities shift entirely to the cloud service provider. Google Cloud implements the Shared Responsibility Model concept. Google Cloud is responsible for security within the cloud, such as physical infrastructure and hardware. Customers, on the other hand, are responsible for security within the cloud, such as data configuration, user identity, and access management.</p><p>Google Cloud is a superior choice compared to other providers because its security infrastructure is designed with Zero Trust (BeyondCorp) principles by default, as well as its data analytics and AI capabilities for real-time threat detection. Learning cybersecurity specifically on Google Cloud Cloud (GCP) is crucial for two reasons:</p><p>GCP has a unique architecture. It includes native tools like the <a href="https://cloud.google.com/security/products/security-command-center?utm_source=aqilix.com">Security Command Center (SCC)</a>, <a href="https://cloud.google.com/security/products/iam?utm_source=aqilix.com">Identity and Access Management (IAM)</a>, and <a href="https://cloud.google.com/vpc?hl=en&amp;utm_source=aqilix.com">Virtual Private Cloud (VPC)</a> Service Controls, which require specialized expertise to configure correctly.</p><p>Misconfiguration can pose significant risks. The majority of data breaches in the cloud are not caused by cloud provider failures but by user misconfigurations. For example, granting overly broad permissions or allowing database access to the public.</p><h4>Case Study: Security Incident Analysis</h4><p>This is a case study from Google Cloud for a cybersecurity incident. Cymbal, a company, experienced a security breach that resulted in the exfiltration of sensitive customer data, including credit card information and personal data. The incident began with the detection of anomalous activity in the company’s cloud system, which, upon further investigation, was confirmed as a large-scale cyberattack impacting the company’s applications, network, and data repositories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cnsJq7hnRuzcTbzleknTwQ.png" /><figcaption>Risk overview on Google Cloud Security Command Centre</figcaption></figure><p>Analysis revealed that the initial attack was a malware-infected application virtual machine (VM). The VM was found to have an insecure network configuration, with Secure Shell (SSH) and Remote Desktop Protocol (RDP) services enabled with a public IP address, allowing the attacker to establish remote connections through the open ports.</p><p>A critical factor exacerbating this incident was a violation of the principle of least privilege. The compromised VM was configured using a <em>Default Service Account</em> that had full access to cloud APIs. This configuration, combined with excessive IAM roles, enabled the attacker to perform privilege escalation. By gaining control of the account’s service keys, the attacker could move laterally within the network, gain unauthorized access to other services, and target sensitive data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*srmiyu2PVaKGcrmDOitcow.png" /><figcaption>All finding vulnerabilities on Google Cloud Security Command Centre</figcaption></figure><p>The culmination of this attack was the exfiltration of unencrypted credit card data. The attacker exploited a vulnerability in a storage bucket with public internet access due to a misconfiguration of Access Control Lists (ACLs) at the object level, which could have been used to exfiltrate data from the corporate environment.</p><h4>Solution</h4><p>The Cymbal case is one example of this misconfiguration. The following are the technical solutions for each breach and how to prevent them on Google Cloud Platform:</p><p><strong>1. Publicly Open SSH and RDP Ports</strong><br>Implement strict VPC Firewall rules to block ingress traffic from the public internet (0.0.0.0/0) on the port management. Access should be done via a Virtual Private Network (VPN) or use an <a href="https://cloud.google.com/security/products/iap?hl=en&amp;utm_source=aqilix.com">Identity-Aware Proxy (IAP)</a> for secure TCP forwarding.</p><p><strong>2. Using Default Service Accounts &amp; Excessive Access Rights</strong><br>Avoid using the <em>Default Service Account</em>. Instead, create a dedicated Service Account with a custom IAM role that follows the principle of Least Privilege (only the minimum necessary access rights).</p><p><strong>3. Publicly Accessible Storage Buckets &amp; Unencrypted Data</strong><br>Enable Uniform Bucket-Level Access to disable individual object ACLs and ensure that buckets are not publicly accessible. Furthermore, sensitive data such as credit card information should be encrypted and processed through <a href="https://cloud.google.com/security/products/dlp?hl=en&amp;utm_source=aqilix.com">Cloud Data Loss Prevention (DLP)</a>.</p><h4>Conclusion</h4><p>Cybersecurity in cloud environments is not a ready-to-use service but rather a process that must be implemented. The case study above teaches us that even the smallest vulnerability, such as a forgotten port or overly lax access permissions and can be exploited by attackers to bring down a company’s entire digital infrastructure. Effectively mitigating these risks requires a combination of secure-by-design architecture and professionals who understand the GCP environment.</p><p>In the face of the complexity of cybersecurity threats, the role of a professional with a <a href="https://www.skills.google/paths/419">Google Cloud Cybersecurity Certificate</a> is vital. Holders of this certificate are required to have the ability to secure cloud infrastructure. They can also design layered network security through VPC configuration and firewall rules. And also create defense-in-depth that effectively closes external attack gaps.</p><p>Internally, mastering the principles of Authentication, Authorization, and Auditing (AAA) enables them to properly manage Cloud IAM, restricting access rights granularly to prevent malicious privilege escalation. This expertise is complemented by a strong understanding of Data Protection and Governance, which ensures data security <em>at rest</em> and <em>in transit</em>, while also ensuring organizational compliance with stringent global standards such as <a href="https://www.pcisecuritystandards.org/?utm_source=aqilix.com">PCI-DSS</a>, the <a href="https://www.nist.gov/?utm_source=aqilix.com">National Institute of Standards and Technology (NIST)</a> Cybersecurity Framework, and MITRE ATT&amp;CK.</p><h4>Secure Your Google Cloud Infrastructure Now</h4><p>Does your GCP infrastructure have hidden vulnerabilities like the Cymbal case above? Don’t wait until an incident occurs. As a <a href="https://www.credly.com/badges/4f3c81b1-12ea-4d9c-83bf-6799dace50fd">professional with Google Cloud Cybersecurity Certificate</a>, I have the verified expertise to audit, secure, and monitor your GCP environment for threats. I’m ready to help you implement the principle of <em>Least Privilege</em>, close network gaps, and ensure compliance with global security standards.</p><p>Contact me for a consultation and security assessment of your infrastructure. <a href="https://www.upwork.com/services/consultation/development-it-dolly-aswin-1471056956571004928?utm_source=aqilix.com">I am available to help</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d94261e5470" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/cybersecurity-in-google-cloud-and-incident-case-studies-5d94261e5470">Cybersecurity in Google Cloud and Incident Case Studies</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Medan Akhirnya Punya Arena!]]></title>
            <link>https://medium.com/@dollyaswin/medan-akhirnya-punya-arena-2a5f2e4f28ba?source=rss-e67ce73e2cd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a5f2e4f28ba</guid>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyber-hack]]></category>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[capture-the-flag]]></category>
            <dc:creator><![CDATA[Dolly Aswin Harahap]]></dc:creator>
            <pubDate>Fri, 22 Aug 2025 08:50:02 GMT</pubDate>
            <atom:updated>2025-09-07T03:24:58.198Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Medan Akhirnya Punya Arena! Catatan dari Kompetisi Siber Tangguh Bangsa Merdeka 2025</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0zTkp2D_OoRj1D0CB7-iGA.jpeg" /></figure><p>Pagi itu, tanggal 21 Agustus 2025, langit <a href="https://id.wikipedia.org/wiki/Kota_Medan">Kota Medan</a> seolah bersekongkol untuk menguji semangat kami. Awan kelabu menggantung rendah, menebarkan suasana muram, sementara hujan gerimis yang turun tanpa henti setelah subuh membuat udara di Laboratorium Komputer <a href="https://vokasi.usu.ac.id/id?utm_source=medium.com/@dollyaswin">Fakultas Vokasi Universitas Sumatera Utara</a> terasa semakin dingin. Di dalam ruangan yang dipenuhi deretan komputer, kabel LAN yang menjulur rapi, dan layar-layar yang masih gelap, sebuah pertanyaan besar menggantung di udara, terasa lebih mendesak di tengah hawa dingin itu: <em>Datangnya orang ini?</em></p><p>Pertanyaan itu bukan tanpa alasan. Selama bertahun-tahun, para pegiat keamanan siber di Kota Medan, sering berdiskusi dalam lingkaran kecil. Kami tahu ada potensi, kami merasakan ada talenta-talenta terpendam di balik layar-layar laptop mahasiswa dan pelajar di kota ini. Mereka yang belajar <em>ethical hacking</em> secara otodidak, yang rasa penasarannya melampaui kurikulum formal, namun tak pernah memiliki panggung untuk unjuk gigi. Medan, sebuah kota yang begitu dinamis, terasa sunyi dari gemuruh kompetisi <em>hacking</em> yang legal dan terstruktur.</p><p>Latar belakang inilah yang menjadi pemicu lahirnya <a href="https://www.instagram.com/d4instrumentasiusu/p/DNmQRrkyqfR/"><strong>Hackathon Siber Tangguh Bangsa Merdeka 2025</strong></a>. Ini bukan sekadar acara, melainkan ini adalah sebuah misi. Bersama <a href="https://www.instagram.com/digitalliteracyaccess/"><strong>Digital Literacy Access</strong></a>, kami bertekad untuk membangun sebuah wadah, sebuah arena pertama di mana para ksatria siber muda Kota Medan bisa bertemu, bertarung, dan yang terpenting, ditemukan. Visi ini disambut dengan tangan terbuka oleh <a href="https://vokasi.usu.ac.id/id/d4-rekayasa-instrumentasi??utm_source=medium.com/@dollyaswin"><strong>Program Studi Teknologi Rekayasa Instrumentasi Fakultas Vokasi USU</strong></a>, yang menyediakan kami <em>“medan pertempuran”</em> yang hangat dan sempurna untuk berlindung dari cuaca dingin di luar.</p><h3>Memilih Capture The Flag (CTF)</h3><p>Untuk mengetahui kemampuan para calon talenta ini, kami membutuhkan format yang tidak hanya menguji pengetahuan, tetapi juga kreativitas, ketekunan, dan kemampuan berpikir di luar kotak. Pilihan kami jatuh pada format kompetisi yang paling efektif dan populer di dunia keamanan siber global, yaitu <a href="https://www.dicoding.com/blog/capture-the-flag-cara-seru-belajar-cyber-security/?utm_source=medium.com/@dollyaswin"><strong>Capture The Flag (CTF)</strong></a>.</p><p>Bagi yang belum familiar, CTF adalah simulasi perburuan digital. Bendera atau “<em>flag”</em> adalah sepotong teks rahasia yang disembunyikan di dalam sistem yang penuh kerentanan. Tugas peserta adalah menjadi <em>ethical hacker, </em>dengan menemukan celah, mengeksploitasinya, dan merebut bendera itu sebagai bukti kemenangan. Ini adalah cara untuk mengasah kemampuan teknis seperti <a href="https://id.wikipedia.org/wiki/Rekayasa_balik?utm_source=medium.com/@dollyaswin">reverse engineering</a>, <a href="https://id.wikipedia.org/wiki/Kriptografi?utm_source=medium.com/@dollyaswin">kriptografi</a>, <a href="https://id.wikipedia.org/wiki/Eksploit_(keamanan_komputer)">eksploitasi web</a>, dan juga <a href="https://id.wikipedia.org/wiki/Forensik_digital?utm_source=medium.com/@dollyaswin">forensik digital</a> dalam lingkungan yang 100% aman dan legal.</p><p>Lebih dari sekadar skill teknis, CTF adalah ujian mental. Ia memaksa peserta untuk berpikir kritis saat menghadapi masalah yang belum pernah mereka lihat sebelumnya dan mendorong kerja sama tim yang solid untuk memecahkan teka-teki kompleks.</p><p>Kami memilih format <a href="https://ctf-wiki.org/en/introduction/mode/#jeopardy-problem-solving?utm_source=medium.com/@dollyaswin"><strong>Jeopardy-style</strong></a>, di mana peserta disajikan sebuah papan penuh tantangan dengan berbagai kategori — seperti eksploitasi web, forensik, kriptografi — dengan poin yang bervariasi sesuai tingkat kesulitannya. Mirip kuis Jeopardy di televisi, tim bebas memilih tantangan mana yang ingin mereka taklukkan terlebih dahulu. Ini memungkinkan setiap tim untuk bermain sesuai kekuatan mereka, menciptakan strategi unik dalam perburuan poin. Dengan mensimulasikan skenario dunia nyata, kompetisi ini mempersiapkan mereka untuk menghadapi ancaman keamanan siber yang sesungguhnya di masa depan.</p><h3>Juice Shop dan Papan Skor CTFd</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wvrVHgze9-xAJzQsxYOECQ.png" /><figcaption>Papan Skor CTFd</figcaption></figure><p>Medan pertempuran digital kami berlangsung selama 6 jam penuh, dari pukul 10.00 pagi hingga 16.00 sore. Kami menyiapkan total 38 tantangan dengan tingkat kesulitan yang beragam, dari soal pemanasan bintang satu hingga tantangan <em>“Final Boss”</em> bintang enam yang nyaris mustahil, dengan total nilai maksimal <strong>14.450 poin</strong>.</p><p>Target serangan mereka adalah <a href="https://owasp.org/www-project-juice-shop/?utm_source=medium.com/@dollyaswin"><strong>OWASP Juice Shop</strong></a>, sebuah aplikasi toko online modern yang sengaja dirancang penuh dengan lubang keamanan. Ini adalah <em>“sasana latihan”</em> standar industri yang sempurna, memungkinkan peserta untuk mempraktikkan serangan nyata tanpa merusak apa pun. Di sisi lain, <a href="https://ctfd.io/?utm_source=medium.com/@dollyaswin"><strong>CTFd</strong></a> berperan sebagai wasit digital dan papan skor “<em>real-time”</em>, tempat di mana setiap “<em>flag”</em> yang berhasil direbut akan ditukarkan dengan poin yang berharga.</p><p>Satu per satu, kekhawatiran kami tentang cuaca sirna. Para peserta datang menembus gerimis, membawa jaket dan ransel, namun yang terpenting, mereka membawa semangat yang jauh lebih hangat dari udara pagi itu. Sebanyak 26 peserta yang terbagi dalam 10 tim mulai memenuhi ruangan registrasi. Nama-nama tim mereka mencerminkan kreativitas dan humor khas anak muda: ada yang terdengar profesional seperti <strong>KNPI Jaya</strong> dan <strong>Hipmi Techies</strong>, ada yang jenaka seperti <strong>Kak, abangku mau foto</strong> dan <strong>RM. Warung Simpang Berdikari</strong>, hingga yang terang-terangan mengaku seperti <strong>Hengker Pesbuk</strong>.</p><h3>Enam Jam Pertempuran</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W1dcbrUlgH8TXiRGuEAubw.jpeg" /><figcaption>Tim KNPI Jaya, HIPMI Techie, TRI NIH BOS dan 0xFam</figcaption></figure><p>Tepat pukul 10.00, aba-aba <em>“Mulai!”</em> diberikan. Suara hujan gerimis di luar jendela seolah menjadi suara latar yang kontras dengan simfoni ketukan keyboard yang cepat dan serempak di dalam ruangan. Wajah-wajah yang tadinya santai berubah menjadi fokus, mata mereka terpaku pada baris-baris kode dan antarmuka Juice Shop, seolah dunia di luar sana lenyap seketika.</p><p>Papan skor di CTFd mulai hidup. Di menit-menit awal, tim-tim mulai memanen poin dari tantangan-tantangan level 1 yang lebih mudah, seolah sedang melakukan pemanasan. Namun, tidak butuh waktu lama bagi persaingan untuk memanas. Di layar proyektor utama, nama <strong>KNPI Jaya</strong> dan <strong>Hipmi Techies</strong> melesat ke puncak, saling salip dengan kecepatan yang mengagumkan.</p><p>Di bawah mereka, pertempuran tak kalah sengit. Tim-tim mahasiswa seperti <strong>Kak, abangku mau foto</strong>, <strong>Rex Regum Query</strong>, <strong>Hengker Pesbuk </strong>dan<strong> RM. Warung Simpang Berdikari </strong>menunjukkan perjuangan yang luar biasa. Sorak-sorai kecil sesekali terdengar dari sudut meja mereka setiap kali sebuah tantangan sulit berhasil dipecahkan. Itulah suara euforia murni dari sebuah penemuan. Enam jam terasa berlalu dalam sekejap. Ruangan yang tadinya dingin mulai terasa hangat oleh panasnya persaingan dan kerja keras otak.</p><h3>Plot Twist: Sebuah Pelajaran Tentang Sportivitas</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wf-e89ZS64J3hHCzZS8SIQ.jpeg" /><figcaption>Tim “Kak, abangku mau foto”, Rex Regum Query, Hengker Pesbuk dan RM. Warung Simpang Berdikari</figcaption></figure><p>Tepat pukul 16.00, waktu habis. Papan skor dibekukan. Suara ketukan keyboard berhenti, digantikan oleh helaan napas lega dan tepuk tangan untuk perjuangan bersama.</p><p>Hasil akhir di papan skor tidak mengejutkan. <strong>KNPI Jaya</strong> kokoh di puncak dengan skor fenomenal <strong>11.450 poin</strong>, diikuti oleh <strong>Hipmi Techies</strong> dengan <strong>11.100 poin</strong>. Di urutan ketiga, dengan perjuangan yang tak kalah hebat, adalah tim mahasiswa <strong>Kak, abangku mau foto</strong>.</p><p>Namun, setelah para pemenang diumumkan, sesuatu yang luar biasa dan sama sekali tak terduga terjadi. Perwakilan dari tim <strong>KNPI Jaya</strong> dan <strong>Hipmi Techies</strong> dengan penuh kerendahan hati, mereka mengumumkan pengunduran diri dari perebutan gelar juara.</p><p>Alasan mereka sederhana, namun sangat menginspirasi. Mereka menjelaskan bahwa anggota tim mereka bukanlah pelajar atau mahasiswa lagi, melainkan sudah berada di level profesional. Tujuan mereka mengikuti kompetisi ini bukan untuk merebut piala, tetapi untuk mengukur denyut nadi komunitas, melihat sejauh mana talenta-talenta muda di Kota Medan berkembang, dan turut meramaikan arena yang baru saja lahir ini.</p><p>Seluruh ruangan lalu meledak dalam tepuk tangan yang paling gemuruh hari itu. Itu adalah momen yang mendefinisikan semangat sejati dari acara ini. Bukan tentang siapa yang paling hebat, tapi tentang membangun ekosistem bersama. Sebuah pelajaran tentang sportivitas dan mentorship yang tak akan pernah bisa diajarkan oleh tantangan teknis mana pun.</p><h3>Para Pemenang dan Gema dari Arena</h3><p>Dengan pengunduran diri yang terhormat dari dua tim teratas, podium juara kini menjadi milik para mahasiswa yang telah berjuang habis-habisan. Kami dengan bangga mengumumkan para pemenang sejati dari Hackathon Siber Tangguh Bangsa Merdeka 2025:</p><ul><li><strong>Juara 1: Kak, abangku mau foto (Mahasiswa Fasilkom TI-USU)</strong></li><li><strong>Juara 2: Rex Regum Query (Mahasiswa Fasilkom TI-USU)</strong></li><li><strong>Juara 3: Hengker Pesbuk (Mahasiswa Fasilkom TI-USU)</strong></li></ul><p>Sebuah kebetulan yang indah bahwa ketiga tim pemenang berasal dari almamater yang sama, Fasilkom TI-USU, menunjukkan betapa besar potensi yang tersimpan di sana.</p><p>Sebagai ketua penyelenggara, hati saya dipenuhi rasa haru dan bangga. Melihat antusiasme mereka, mendengar tawa dan diskusi teknis mereka, adalah bayaran yang tak ternilai. Beberapa pemenang memberikan komentar. <em>“Bang, ini pertama kalinya kami ikut CTF offline,”</em> kata salah satu dari mereka dengan mata berbinar. <em>“Acaranya gila, benar-benar di luar ekspektasi kami. Kapan dibuat lagi, Bang?”</em></p><p>Kalimat sederhana itu adalah validasi dari semua kerja keras kami. Misi kami berhasil. Api itu tidak hanya ada, ia membara dengan terang, cukup untuk menghangatkan ruangan yang dingin oleh mendung di luar.</p><h3>Sebuah Harapan untuk Generasi Siber Kota Medan</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*op8DUkkQeHnmR9W8o2_n-Q.png" /><figcaption>Kompetisi berakhir.</figcaption></figure><p><a href="https://www.instagram.com/d4instrumentasiusu/p/DNmQRrkyqfR/"><strong>Hackathon Siber Tangguh Bangsa Merdeka 2025</strong></a> telah berakhir, namun jejaknya baru saja dimulai. Saya berharap, akan menjadi titik awal, sebuah fondasi dari wadah bagi para pegiat <em>ethical hacking</em> di Kota Medan. Harapan saya, dan juga harapan Digital Literacy Access, adalah kita bisa terus menggelar acara seperti ini, mungkin dengan skala yang lebih besar dengan format yang berbeda. Mungkin Attack-Defense? Atau tantangan yang lebih gila lagi.</p><p>Acara ini tidak akan terwujud tanpa adanya dukungan yang luar biasa. Terima kasih yang sebesar-besarnya kepada para sponsor: <a href="https://www.linkedin.com/in/alfianlinux"><strong>Alfian Linux</strong></a> dari <a href="https://www.instagram.com/digitalliteracyaccess/"><strong>Digital Literacy Access</strong></a><strong> </strong>dan <a href="https://xtendindonesia.co.id/"><strong>PT. Xtend Integrasi Indonesia</strong></a>, <a href="https://vokasi.usu.ac.id/id/d4-rekayasa-instrumentasi??utm_source=medium.com/@dollyaswin"><strong>Program Studi Teknologi Rekayasa Instrumentasi Fakultas Vokasi USU</strong></a>, dan juga <strong>United States Mission Indonesia</strong>. Dan terima kasih juga kepada segenap panitia yang telah bekerja keras untuk semua ini, yang tidak dapat saya sebutkan namanya satu per satu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9HN8f8SQJeQP0DGDMNzLGA.jpeg" /><figcaption>Photo bersama dengan seluruh peserta</figcaption></figure><p>Untuk para peserta, kalian semua adalah pemenang. Namun lebih dari itu, kalian adalah bukti. Bukti bahwa di bawah langit Kota Medan yang terkadang mendung, ada bara api semangat siber yang siap menyala. Kepada generasi muda, para mahasiswa dan pelajar yang pada hari itu telah menunjukkan taringnya. Teruslah belajar, dan teruslah merasa penasaran. Arena ini milik kalian sekarang. Jadikan ia tempat bertumbuh, dan suatu hari nanti, jadilah mentor bagi generasi setelah kalian, seperti yang telah dicontohkan pada hari itu. Sampai jumpa di pertempuran berikutnya.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a5f2e4f28ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Modus Penipuan Mengatasnamakan JNE Dengan Klaim Paket Hilang via Zoom Meeting]]></title>
            <link>https://medium.com/@dollyaswin/modus-penipuan-mengatasnamakan-jne-dengan-klaim-paket-hilang-via-zoom-meeting-8d6484b63001?source=rss-e67ce73e2cd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d6484b63001</guid>
            <dc:creator><![CDATA[Dolly Aswin Harahap]]></dc:creator>
            <pubDate>Tue, 19 Aug 2025 06:19:45 GMT</pubDate>
            <atom:updated>2025-08-19T06:19:45.552Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xzvGL7OvM6KXD6Knlj-4HA.jpeg" /></figure><p>Melalui tulisan ini, saya bermaksud untuk memaparkan secara rinci kronologi upaya penipuan yang saya alami pada tanggal 19 Agustus 2025, yang melibatkan oknum yang mengatasnamakan perusahaan jasa pengiriman <a href="http://jne/">JNE</a>. Tujuan dari pemaparan ini adalah untuk memberikan edukasi kepada masyarakat serta menjadi masukan bagi pihak-pihak terkait agar dapat meningkatkan sistem keamanannya.</p><h3>Kronologi Upaya Penipuan</h3><h4><strong>1. Kontak Awal</strong></h4><p>Pada hari Selasa, 19 Agustus 2025, pukul 09.34 WIB, saya menerima panggilan telepon dari sebuah nomor pribadi (provider teridentifikasi sebagai <a href="https://indosatooredoo.com/portal/id/indexpersonal?utm_source=medium.com/@dollyaswin">Indosat Ooredoo</a>). Penelepon, yang memperkenalkan diri sebagai Dea dari <a href="https://www.jne.co.id/?utm_source=medium.com/@dollyaswin">JNE</a> Pusat Jakarta Barat, Tomang Raya.</p><p>Ia mengetahui detail pesanan saya dan menginformasikan bahwa paket pesanan saya dari <a href="https://www.tokopedia.com/?utm_source=medium.com/@dollyaswin">Tokopedia</a> telah mengalami insiden dalam perjalanan menuju gudang sehingga dinyatakan hilang. Untuk mengatasi kerugian tersebut, pihak mereka menawarkan solusi berupa pengembalian dana penuh sesuai nilai barang, ditambah dengan dana kompensasi sebesar Rp 300.000,-.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/1*hDHwwuthBKGAX958jV8-nA.jpeg" /><figcaption>Riwayat telepon dari oknum JNE</figcaption></figure><h4><strong>2. Pengarahan ke Prosedur Klaim yang Tidak Standar</strong></h4><p>Untuk memproses klaim tersebut, saya diinstruksikan untuk bergabung dalam sebuah sesi Zoom Meeting dengan bagian keuangan. Saya diberikan informasi berikut:</p><ul><li><strong>Meeting ID:</strong> 9570212717</li><li><strong>Password:</strong> <em>[Diberikan oleh oknum tersebut]</em></li></ul><p>Saat saya hendak menggunakan aplikasi Zoom pada laptop, oknum tersebut menyarankan agar saya wajib menggunakan aplikasi pada ponsel dengan dalih bahwa sesi pada komputer tidak dapat direkam. Hal ini menjadi <strong>indikasi mencurigakan pertama</strong>, karena alasan yang diberikan tidak logis dan tidak relevan dengan prosedur klaim pada umumnya. Meskipun demikian, saya tetap melanjutkan proses untuk memahami modus operandi mereka lebih jauh.</p><h4><strong>3. Proses Klaim Fiktif dan Bukti Transfer Palsu</strong></h4><p>Setelah bergabung dalam Zoom Meeting, oleh oknum di meeting tersebut saya diminta untuk mengisi data permohonan klaim. Oknum tersebut menjanjikan proses transfer dana hanya akan memakan waktu 3–5 menit. Setelah saya memberikan nomor rekening, tidak lama kemudian mereka mengirimkan sebuah tangkapan layar (screenshot) bukti transfer dari Bank BRI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IXU6PQKUDuJrDmXdAT20ag.jpeg" /><figcaption>Tangkapan layar Zoom Chat</figcaption></figure><p>Di sini, muncul <strong>indikasi mencurigakan kedua</strong>: dana ditransfer dari <strong>rekening atas nama perorangan</strong>, bukan rekening atas nama perusahaan. Ketika saya mempertanyakan hal ini, oknum tersebut beralasan bahwa rekening tersebut adalah milik petugas yang sedang bertugas pada shift pagi.</p><p>Setelah dilakukan pengecekan berulang kali melalui aplikasi mobile banking, tidak ada dana masuk ke rekening saya.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*uIqgXGSATFa-XEEObgTxZQ.jpeg" /><figcaption>Riwayat zoom meeting dengan oknum JNE yang mengaku bagian keuangan</figcaption></figure><h4><strong>4. Eskalasi Penipuan: Modus “Konfirmasi Penutupan Klaim”</strong></h4><p>Setelah saya konfirmasi bahwa dana belum diterima, oknum tersebut memulai tahap final dari modus penipuannya. Ia menyatakan bahwa sistem klaim harus ditutup terlebih dahulu dan saya diminta melakukan <em>“konfirmasi penutupan”</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i4qrbrMe5F6mYnIXp0RSUw.jpeg" /><figcaption>Tangkapan layar Zoom Chat</figcaption></figure><p>Oknum tersebut mengarahkan saya untuk melakukan langkah-langkah berikut:</p><ul><li>Membuka aplikasi mobile banking dan memilih menu <strong>Transfer</strong>.</li><li>Memasukkan nomor rekening Bank <a href="https://bri.co.id/?utm_source=medium.com/@dollyaswin">BRI</a> milik mereka (rekening perorangan).</li><li>Mengisi kolom keterangan sesuai instruksi.</li><li>Memasukkan nominal transfer sebesar <strong>Rp 888.999,-</strong>.</li></ul><p>Oknum tersebut meyakinkan saya bahwa transaksi ini hanyalah sebuah bentuk konfirmasi dan saldo saya tidak akan berkurang. <strong>Ini adalah</strong> <strong>indikasi penipuan yang paling jelas</strong>. Tidak ada satu pun prosedur perbankan atau klaim yang mengharuskan nasabah mentransfer sejumlah uang sebagai bentuk konfirmasi.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fdourQBiZCCyRHOOPm1WWQ.jpeg" /><figcaption>Nomor Rekening BRI yang digunakan untuk menerima uang hasil penipuan</figcaption></figure><p>Menyadari bahwa ini adalah upaya penipuan yang mutlak, saya segera mengonfrontasi oknum tersebut dan mengakhiri komunikasi.</p><h3>Himbauan dan Pertanyaan kepada Pihak Terkait</h3><p>Berdasarkan pengalaman ini, saya ingin menyampaikan beberapa poin penting:</p><h4><strong>1. Kepada Masyarakat Umum dan Pelanggan E-commerce</strong></h4><ul><li><strong>Verifikasi Informasi<br></strong>Perusahaan logistik resmi tidak akan menghubungi Anda melalui nomor telepon pribadi untuk urusan klaim. Selalu verifikasi melalui call center atau kanal resmi perusahaan.</li><li><strong>Waspadai Prosedur Tidak Baku<br></strong>Proses klaim melalui Zoom Meeting personal, terutama dengan dalih yang tidak masuk akal, adalah modus penipuan.</li><li><strong>Periksa Rekening Pengirim<br></strong>Setiap pengembalian dana atau kompensasi dari institusi resmi akan selalu menggunakan rekening atas nama perusahaan, bukan perorangan.</li><li><strong>Tolak Permintaan Transfer<br></strong>Jika Anda diminta mentransfer uang dengan alasan apa pun (verifikasi, konfirmasi, pembukaan blokir), dapat dipastikan itu adalah penipuan. Segera akhiri komunikasi.</li></ul><h4><strong>2. Kepada Tokopedia dan JNE</strong></h4><p>Muncul pertanyaan fundamental mengenai keamanan data pelanggan. <strong>Bagaimana data spesifik mengenai transaksi saya seperti: detail pesanan, kurir yang digunakan, dan nomor telepon pribadi saya dapat diakses oleh pihak yang tidak bertanggung jawab?</strong></p><p>Saya menghimbau untuk diadakan investigasi internal dan penguatan sistem proteksi data pelanggan untuk mencegah kejadian serupa terulang kembali.</p><h4><strong>3. Kepada Pihak Perbankan (Bank BRI)</strong></h4><p>Mohon agar rekening yang digunakan untuk tindak kejahatan ini dapat segera ditinjau dan diproses sesuai hukum yang berlaku untuk memutus rantai penipuan.</p><h4><strong>4. Kepada Provider Telekomunikasi (PT Indosat Ooredoo Hutchison)</strong></h4><p>Nomor yang digunakan oleh oknum teridentifikasi berasal dari jaringan Anda. Mohon untuk melakukan penelusuran terhadap nomor tersebut dan mengambil tindakan tegas untuk mencegah penyalahgunaannya di kemudian hari.</p><h4><strong>5. Kepada Pihak Zoom Video Communications</strong></h4><p>Platform Anda, yang sejatinya dirancang untuk memfasilitasi komunikasi dan kolaborasi yang produktif, telah disalahgunakan sebagai sarana untuk melakukan upaya penipuan. Dalam kasus ini, oknum penipu memanfaatkan fitur Zoom Meeting untuk membangun ilusi profesionalitas dan memanipulasi korban dalam sebuah lingkungan yang terkontrol. Kami mengimbau agar Zoom dapat meningkatkan sistem pengawasan dan pelaporan penyalahgunaan (<em>abuse reporting</em>), serta mempertimbangkan implementasi peringatan keamanan bagi pengguna terkait potensi penipuan yang dapat terjadi melalui platform.</p><h3>Kesimpulan</h3><p>Semoga kasus upaya penipuan ini dapat meningkatkan kesadaran kita semua akan bahaya modus penipuan yang semakin canggih. Kerja sama yang sinergis antara penyedia platform digital, institusi keuangan, perusahaan logistik, dan regulator sangatlah krusial dalam menciptakan ekosistem digital yang aman. Mari bersama-sama menjadi konsumen yang lebih cerdas, kritis, dan waspada.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d6484b63001" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Responsibilities of a Google Cloud Security Analyst]]></title>
            <link>https://medium.com/google-cloud/the-responsibilities-of-a-google-cloud-security-analyst-a551af21c955?source=rss-e67ce73e2cd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a551af21c955</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[gcp-security-operations]]></category>
            <category><![CDATA[cloud-security-analysis]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Dolly Aswin Harahap]]></dc:creator>
            <pubDate>Mon, 18 Aug 2025 03:56:17 GMT</pubDate>
            <atom:updated>2025-08-19T04:48:30.714Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WVNg4tzEM22zjXZo21vCow.png" /></figure><p>Let’s step away from technology for a moment and think about something simpler, that is a brand-new house. When you first build it, it’s perfect. The foundation is solid. The doors have strong locks. The windows are secure. On day one, your house is a fortress. But a house isn’t a museum piece, but it is a place where life happens. <em>And life is messy.</em></p><p>One day, you need a friend to water the plants while you’re away, so you leave a key under the doormat. You fully intend to take it back, but you get busy and forget. <em>(This is like making a Cloud Storage bucket temporarily public).</em></p><p>On the another day, a family member needs access to the whole house for a project, so you give them a copy of the master key that opens every single door. The project ends, but the key is never returned. <em>(This is like granting a temporary Project Editor role that becomes permanent).</em></p><p>And someday, you install a new smart TV. It works great. But six months later, a major security flaw is discovered in its software, turning that TV into a potential gateway for hackers to get onto your home Wi-Fi network. <em>(This is a microservice with a newly discovered vulnerability).</em></p><p>Individually, none of these actions feel like a major security breach. But over time, your once-perfect fortress is now full of hidden keys, forgotten master keys, and vulnerable devices. This slow, silent decay of security, caused by the normal, everyday business of <em>“living”</em> in your environment, is the single biggest risk in the cloud.</p><p>This is exactly why a Cloud Security Analyst is needed. They are the home security expert who doesn’t just install the locks on day one. They are the ones who regularly walk the property, checking for keys left under doormats, taking inventory of who has a master key, and ensuring your smart TV’s software is patched. They are the guardians against the slow, silent drift from secure to vulnerable. To do this, they rely on a set of core responsibilities that form a continuous cycle of vigilance and improvement.</p><p>To truly understand this vital role, we must move beyond the abstract and break down the core responsibilities that define a security analyst’s daily mission on the <a href="https://cloud.google.com/??utm_source=aqilix.com">Google Cloud Platform</a>. These duties are not a simple checklist; they are an interconnected cycle of vigilance, analysis, and continuous improvement that forms the backbone of any robust cloud security program.</p><h3>Map Security Concepts to Cloud Products</h3><p>At its core, this is the foundational responsibility of a security analyst. It is the ability to translate abstract security principles into the concrete reality of cloud services. An analyst who understands the concept of <em>“</em><a href="https://csrc.nist.gov/glossary/term/least_privilege?utm_source=aqilix.com"><em>least privilege</em></a><em>”</em> is valuable; an analyst who knows how to apply it to a specific <a href="https://cloud.google.com/security/products/iam?utm_source=aqilix.com">Google Cloud IAM</a> role for a <a href="https://cloud.google.com/functions?utm_source=aqilix.com">Cloud Run Function</a> is indispensable.</p><p>This responsibility requires a deep understanding of the cloud’s building blocks—compute, network, and storage—and the unique attack vectors associated with each.</p><ul><li><strong>Compute<br></strong>For a <a href="https://cloud.google.com/products/compute?utm_source=aqilix.com&amp;hl=en">Compute Engine</a> virtual machine, the analyst must consider threats like unpatched operating systems, open RDP/SSH ports, and malware. For <a href="https://cloud.google.com/kubernetes-engine?utm_source=aqilix.com&amp;hl=en">Google Kubernetes Engine (GKE)</a>, they must think about container security, insecure configurations in the cluster, and risks within the container registry.</li><li><strong>Storage<br></strong>For a <a href="https://cloud.google.com/storage?utm_source=aqilix.com&amp;hl=en">Cloud Storage</a> bucket, the primary concern is data exposure. The analyst must understand the difference between IAM roles and legacy Access Control Lists (ACLs), the dangers of granting public access, and the importance of data encryption at rest.</li><li><strong>Networking<br></strong>For a <a href="https://cloud.google.com/products/compute?utm_source=aqilix.com&amp;hl=en">Virtual Private Cloud (VPC)</a>, the analyst maps concepts like network segmentation and defense-in-depth to firewall rules, private IP addressing, and secure interconnects like <a href="https://cloud.google.com/network-connectivity/docs/vpn/concepts/overview?hl=en&amp;utm_source=aqilix.com">Cloud VPN</a>.</li></ul><p>In practice, when a tool flags a Cloud Storage bucket as <em>“publicly accessible,”</em> the analyst doesn’t just see an alert. They see a potential violation of data privacy regulations (like <a href="https://gdpr-info.eu/?utm_source=aqilix.com">GDPR</a> or <a href="https://oag.ca.gov/privacy/ccpa?utm_source=aqilix.com">CCPA</a>), a risk of sensitive data leakage, and a potential entry point for attackers to drop malicious files. This ability to connect a technical configuration to a tangible business risk is what makes this responsibility so crucial.</p><h3>Master the Specialized Tools</h3><p>An analyst is only as effective as their tools. The Google Cloud environment is a vast, dynamic ecosystem, and it is impossible to monitor manually. Therefore, a security analyst must be a master of the specialized tools that provide visibility, evidence, and the means to act.</p><p>The modern analyst’s toolkit is extensive:</p><ul><li><strong>Security Command Center (SCC)<br></strong>This is the central nervous system. The <a href="https://medium.com/google-cloud/how-security-command-center-in-google-cloud-exposed-hidden-backdoor-in-my-project-744deeb9551b">Security Command Center</a> (SCC) consolidates information from various sources, offering a unified view of misconfigurations, vulnerabilities, and threats. An analyst uses SCC to get the high-level <em>“what is wrong?”</em> picture.</li><li><strong>Cloud Logging<br></strong>This is the forensic laboratory. When SCC provides the <em>“what,”</em> Cloud Logging provides the “who, when, where, and how.” An analyst must be skilled in querying and interpreting audit logs to trace the sequence of events during an incident.</li><li><strong>Linux &amp; gcloud CLI<br></strong>These are the hands-on inspection tools. An analyst uses the command line to directly interact with resources, inspect configurations, check permissions, and execute remediation scripts.</li><li><strong>Terraform &amp; Infrastructure as Code (IaC)<br></strong>To understand and secure an environment, an analyst must understand how it was built. By reading <a href="https://developer.hashicorp.com/terraform?utm_source=aqilix.com">Terraform</a> code, an analyst can identify potential misconfigurations <em>before</em> they are ever deployed.</li><li><strong>Intrusion Detection Systems (IDS) like Cloud IDS<br></strong>These tools monitor network traffic for suspicious patterns, detecting threats that might otherwise go unnoticed.</li></ul><p>In practice, an alert in SCC might identify an <em>“Anomalous IAM Grant.”</em> The analyst would then pivot to Cloud Logging to identify the user and IP address that made the call. Using the gcloud CLI, they would inspect the permissions of the affected service account. Finally, they might review Terraform&#39;s code to see if this change was intentional or a deviation from the approved infrastructure plan. Each tool contributes to the overall picture.</p><h3>Communicate the Security Posture Effectively</h3><p>Technical findings are useless if they are not understood or acted upon. A critical, and often overlooked, responsibility of a security analyst is to act as a bridge between the technical world of security and the broader business. They must be able to translate complex risks into clear, concise, and actionable information for different audiences.</p><p>This involves avoiding jargon and tailoring the message:</p><ul><li><strong>For a Development Team<br></strong>The communication can be technical, focusing on the specific vulnerability (e.g., a <a href="https://www.cve.org/?utm_source=aqilix.com">CVE</a> number), the affected library, and the required patch.</li><li><strong>For a Project Manager<br></strong>The communication should focus on the impact and the required action. <em>“A high-severity vulnerability has been found in the user authentication service. We need to prioritize a patch in the next sprint to avoid a potential account takeover risk.”</em></li><li><strong>For Senior Management<br></strong>The communication should be high-level, focusing on business risk. <em>“We’ve identified a pattern of misconfigurations that increases our risk of a data breach. We are implementing an automated guardrail to address this, which will strengthen our overall compliance posture.”</em></li></ul><p>In practice, for clear &amp; actionable: <em>“We’ve found a critical security flaw in one of our running applications that could allow an attacker to take control of the server. The development team has a patch ready, and we need to schedule an emergency deployment to fix it.”</em></p><h3>Monitor and Respond to Security Incidents</h3><p>This is the most well-known responsibility of the front-line defense. The analyst is the first responder in the event of a security incident. This process is a structured discipline:</p><ol><li><strong>Detection<br></strong>Actively monitoring dashboards (like SCC), alerts, and log streams to identify suspicious activity. This could be anything from a malware signature detected on a VM to a pattern of failed logins.</li><li><strong>Analysis<br></strong>Quickly assessing the nature and severity of the threat. Is it a false positive? Is it an automated scanner or a real attacker? What is the potential impact?</li><li><strong>Containment<br></strong>Taking immediate action to limit the damage. This could involve isolating an infected VM from the network, revoking a compromised user’s credentials, or adding a deny rule to a firewall.</li><li><strong>Eradication &amp; Recovery<br></strong>Removing the threat from the environment and restoring systems to a known-good state.</li><li><strong>Post-Mortem &amp; Escalation<br></strong>Documenting the incident, identifying the root cause, and communicating the findings and lessons learned to the appropriate parties.</li></ol><h3>Test and Validate New Security Products and Controls</h3><p>A security analyst’s job is not just to operate the existing security stack but to constantly improve it. The threat landscape and the technology used to defend against it are in a constant state of evolution.</p><p>This responsibility involves:</p><ul><li><strong>Evaluating New Tools<br></strong>The responsibilities also include researching and testing new Google Cloud security services (such as <a href="https://cloud.google.com/security/products/intrusion-detection-system?hl=en&amp;utm_source=aqilix.com">Cloud IDS</a> or <a href="https://www.beyondcorp.com/?utm_source=aqilix.com">BeyondCorp</a>) or third-party solutions to determine their potential to supplement the current defenses.</li><li><strong>Performing Proof-of-Concepts (PoCs)<br></strong>Setting up sandbox environments to test a new product’s effectiveness and its impact on performance and operations.</li><li><strong>Testing Applications<br></strong>Collaborating with development teams to test new applications before they are deployed to production, ensuring they don’t introduce new security risks.</li><li><strong>Validating Existing Controls<br></strong>Regularly testing that existing security measures are working as intended. For example, running a controlled test to ensure a firewall rule is correctly blocking traffic.</li></ul><h3>Stay Current with Security Advancements</h3><p>This final responsibility underpins all the others. A security analyst cannot effectively defend against threats they don’t understand. The commitment to continuous learning is non-negotiable.</p><p>This involves:</p><ul><li><strong>Monitoring Threat Intelligence<br></strong>Following security news, reading blogs from security researchers, and subscribing to alerts from sources like the <a href="https://www.isaca.org/credentialing/cisa?utm_source=aqilix.com">Cybersecurity and Infrastructure Security Agency (CISA).</a></li><li><strong>Understanding Common Attack Patterns<br></strong>Regularly studying resources like the <a href="https://medium.com/@dollyaswin/most-common-web-application-security-risks-2e925a4e950a">OWASP Top 10 list</a>. Knowing that <em>“Broken Access Control”</em> and <em>“Injection”</em> are top threats provides the context to understand why certain alerts in SCC are more critical than others.</li><li><strong>Continuous Education.<br></strong>Pursuing new certifications, attending webinars, and participating in security communities to learn about new defensive techniques and emerging attack vectors.</li></ul><h3>Conclusion</h3><p>The role of a Google Cloud Security Analyst is dynamic and demanding. It requires a person to be a technician, an investigator, a communicator, and a lifelong student. They are the human intelligence layer on top of the powerful automated tools of the cloud, providing the context, analysis, and decisive action that turns security data into meaningful protection. They are the modern guardians of the digital world.</p><p>If the story of the <em>“perfectly secure” </em>house and its slow, silent decay sounds familiar, and you’re worried about the hidden risks and blind spots in your own Google Cloud environment, you don’t have to solve it alone. As a specialist in Google Cloud security, I help businesses assess their security posture, identify vulnerabilities, and build more resilient, secure systems.</p><p>If you need an experienced Google Cloud Security Analyst for a consultation or a project, <a href="https://www.upwork.com/services/consultation/development-it-dolly-aswin-1471056956571004928?utm_source=aqilix.com">I am available to help</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a551af21c955" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/the-responsibilities-of-a-google-cloud-security-analyst-a551af21c955">The Responsibilities of a Google Cloud Security Analyst</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A 15-year Journey of Freelancing: #7 You Need Validation]]></title>
            <link>https://medium.com/@dollyaswin/a-15-year-journey-of-freelancing-7-you-need-validation-1fb1b1adc07c?source=rss-e67ce73e2cd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fb1b1adc07c</guid>
            <category><![CDATA[remote-work]]></category>
            <category><![CDATA[freelancers]]></category>
            <category><![CDATA[online-freelancing]]></category>
            <category><![CDATA[upwork-tips]]></category>
            <category><![CDATA[upwork]]></category>
            <dc:creator><![CDATA[Dolly Aswin Harahap]]></dc:creator>
            <pubDate>Mon, 11 Aug 2025 05:09:03 GMT</pubDate>
            <atom:updated>2025-08-11T05:09:03.130Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9enGToDgXw4mrCaF8KVEyA.png" /></figure><p>Over the last fifteen years, I’ve built a sustainable career in remote work, a career that has afforded me a life of flexibility and purpose.</p><p>Throughout this journey, I’ve had to relearn a fundamental lesson over and over again: the difference between looking valuable on paper and <em>being</em> valuable in practice. This is the story of how I learned to combine two different types of validation to build a career that is resilient, respected, and rewarding.</p><h3>My First Misunderstanding About Validation</h3><p>Let’s go back to 2010. I was a decent programmer, but I was struggling to land the better-paying gigs. I felt invisible. I resolved to find a unique solution that would set me apart. Therefore, I invested time and money into getting <a href="https://www.linkedin.com/in/dollyaswin/details/certifications/">my first formal certification</a> from <a href="https://zend.com/?utm_source=dollyaswin&amp;utm_medium=blog&amp;utm_campaign=content">Zend Technology</a>.</p><p>I proudly displayed the badge on my LinkedIn profile and waited. And… not much changed. Perhaps there were a few more views on my profile, but there was no influx of offers. I was frustrated. My <em>“magic bullet”</em> felt like a dud.</p><p>This was my first, crucial lesson about validation. I had mistaken a key for the treasure map. I thought possessing the credential was the end goal. I didn’t understand its true, tactical purpose. A certificate is not the destination. It’s just the very first step on the journey.</p><h3>The Two Types of Validation</h3><p>To build a truly resilient freelance career, you need to understand and strategically combine two different types of validation: <em>passive and active.</em></p><h4>1. Passive Validation is Your Passport</h4><p>Think of things like your university degree or your industry certifications (like my Zend certificate or a modern <a href="https://www.credly.com/users/dollyaswin/badges#credly">Google Cloud Professional</a> certification). These are formal, third-party credentials.</p><p>Their primary job is to get you past the gatekeepers. Large companies and automated HR systems often use these as keyword filters. Without the right “<em>passport stamp,</em>” your application might be filtered out before a human ever sees it. It proves you meet a baseline requirement. <em>It gets you in the room.</em></p><p>Believing the passport is enough. <em>No one is going to hire you just because you have a valid passport. They want to know where you’ve been and what you’ve done.</em></p><h4><strong>2. Active Validation is Your Travel Stories</strong></h4><p>This is the proof of your competence that you create yourself, every single day. It includes your technical case studies, your writing (<a href="https://medium.com/@dollyaswin">blog posts, tutorials</a>), your teaching (answers on <a href="https://stackoverflow.com/users/1136666/dolly-aswin">Stack Overflow</a>), and your public work (like a <a href="https://github.com/dollyaswin">GitHub profile</a>).</p><p>Your work is the substance. This is what you talk about once you’re in the room. The content is what builds trust, demonstrates your expertise, and convinces a client that you are the right person to solve their specific problem.</p><p>Unlike a static passport, your travel stories are dynamic. They show your current skills, your thought process, and your passion. They are undeniable proof of your value.</p><p><em>The most successful freelancers don’t choose one over the other. They use their passport to arrive to the destination, and then they captivate everyone with their incredible travel stories.</em></p><h3>Conclusion</h3><p>Understanding the crucial difference between a <em>“passport”</em> and your <em>“travel stories”</em> helps you identify the most dangerous distraction in the modern remote work world. It is very competitive, and it can feel overwhelming. It’s natural to look for a guide. <em>But the most dangerous guides are the ones who promise you a map to a treasure that doesn’t exist.</em> <em>They sell you the intoxicating idea of a shortcut, when the real treasure lies in the journey itself.</em></p><p>The journey of building your career is the journey of building yourself. Your degrees and certifications are your passport. They can get you past the first gate, and it’s strategic to have them. <em>But they are not the destination.</em></p><p><em>The real, sustainable, and deeply satisfying work is in crafting your travel stories. It’s in the patient, consistent effort of creating a body of work that speaks for itself. It’s in the articles you write, the problems you solve, the code you share, and the value you provide, day in and day out.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fb1b1adc07c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A 15-year Journey of Freelancing: #6 Stop Listening to Upwork ‘Gurus’]]></title>
            <link>https://medium.com/@dollyaswin/a-15-year-journey-of-freelancing-6-stop-listening-to-upwork-gurus-ee129c1b86f0?source=rss-e67ce73e2cd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee129c1b86f0</guid>
            <category><![CDATA[remote-work]]></category>
            <category><![CDATA[freelancers]]></category>
            <category><![CDATA[upwork]]></category>
            <category><![CDATA[upwork-tips]]></category>
            <category><![CDATA[online-freelancing]]></category>
            <dc:creator><![CDATA[Dolly Aswin Harahap]]></dc:creator>
            <pubDate>Mon, 21 Jul 2025 07:45:54 GMT</pubDate>
            <atom:updated>2025-07-21T07:45:54.743Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IRQfMWPuVsQDqkW7vLM6TA.png" /></figure><p>My journey as a freelancer started in 2009. The platform wasn’t even called Upwork yet; it was a scrappy, promising site named <a href="https://en.wikipedia.org/wiki/Upwork">oDesk</a>. The world of remote work was a frontier, full of opportunity but with very few maps. Over the last decade and a half, I’ve managed to build a sustainable, rewarding career through that platform, navigating its evolution from a simple marketplace into the global giant it is today.</p><p>But something has changed recently. A new, noisy industry has sprung up around platforms like Upwork. I call them the <em>“Upwork Gurus.”</em></p><p>You’ve probably seen them. They pop up in your social media feeds with flashy promises and a confident smile. They offer a “<em>secret formula</em>” or a “<em>proven blueprint</em>” to dominate the platform. They tell you to use their “<em>killer proposal template,</em>” to “bid on 30 jobs a day to play the numbers game,” or to use psychological tricks to land your first few gigs.</p><p>And then comes the sales pitch. For just $99, you can buy their ebook. For $499, you can join their exclusive mastermind group. For a “small” monthly fee, you get access to their private community where they’ll share the “<em>real secrets.”</em></p><p>I’m writing this post today to give you a piece of advice born from over a decade of experience: <strong>be very, very careful.</strong></p><p>These <em>“gurus”</em> often prey on the desperation and uncertainty that every new freelancer feels. They sell you shortcuts because the idea of a shortcut is intoxicating when you’re facing a mountain of competition. However, I&#39;m here to inform you that these shortcuts typically result in a stalemate. These shortcuts teach you to become a <em>“commodity, competing on speed and price”</em> rather than value.</p><p>The real path to a long-term, high-earning freelance career is entirely different. It’s slower, it requires more thought, but it’s built on a foundation of solid rock, not sand.</p><p>My own philosophy wasn’t shaped by a <em>“guru” </em>but by two old books that have nothing to do with freelancing platforms: <a href="https://www.amazon.com/Remote-Office-Required-Jason-Fried/dp/0091954673?utm_source=aqilix.com"><strong>REMOTE</strong></a> and <a href="https://www.amazon.com/Rework-Jason-Fried/dp/0307463745"><strong>REWORK</strong></a> by <a href="https://world.hey.com/jason?utm_source=aqilix.com">Jason Fried</a> and <a href="https://world.hey.com/dhh?utm_source=aqilix.com">David Heinemeier Hansson</a>. These books challenged my entire approach. They taught me to stop thinking like a frantic job seeker and start acting like a respected, independent business partner.</p><p>What follows are the real “<em>tips and tricks</em>” that have worked for me. They aren’t hacks. They are principles. They take work, but they will distinguish you from the 99% of freelancers who follow the same bad advice.</p><h4>1. Stop Selling, Start Consulting</h4><p>The average Upwork proposal is a frantic plea: “Please hire me! I have the skills! I’m reliable!” The <em>REWORK</em> philosophy is to flip this entirely. Instead of selling yourself, <em>teach</em> your potential client. Your proposal should be your first act of providing value, a free mini-consultation.</p><p>I transformed my proposals from simply saying, &quot;<em>Pick me!</em>&quot; to offering a diagnostic session. I’d break down their problem and offer insights immediately, demonstrating expertise and guiding them toward a solution before even being hired. This simple shift elevates you from “<em>bidder</em>” to “<em>expert consultant.</em>”</p><p>Let me show you a real-world “<em>before and after</em>” of my proposal style.</p><p><strong>My Old, Generic Proposal:</strong></p><blockquote>Hello,</blockquote><blockquote>I have read your job description for a Cloud Architect and I am very interested. I have over 5years of experience with Google Cloud Platform, Kubernetes, and CI/CD pipelines. I am a hard worker, a great communicator, and I am confident I can deliver excellent results for your project. I am available to start immediately.</blockquote><blockquote>Thank you for your consideration.</blockquote><p>The focus of this proposal is solely on himself, emphasizing &quot;me, me, me.&quot; It’s a slightly more formal way of saying, “<em>Pick me!</em>”</p><p><strong>My New, Value-First Proposal:</strong></p><blockquote>Hello,</blockquote><blockquote>Thanks for the detailed post about your need to migrate your monolithic application to a microservices architecture on GCP. This is a powerful move for improving scalability and developer velocity.</blockquote><blockquote>A common challenge I’ve helped clients navigate with this exact transition is managing inter-service communication and observability. Based on your description, it sounds like you’re at a crossroads: should you use a full service mesh like Istio, or would a simpler approach with direct gRPC calls and custom metrics be more cost-effective at your current scale? Often, starting simple is the better path to avoid unnecessary operational complexity.</blockquote><blockquote>To help clarify the best approach for you, I have three quick questions:<br>- What is your current strategy for service discovery? Are you using something like Consul or relying on internal DNS?<br>- How is your team currently handling logging and tracing across services<br>- What are your primary business drivers for this migration? Is it faster feature deployment, cost savings, or system stability?</blockquote><blockquote>Answering these will help us map out a phased migration plan that minimizes risk. Looking forward to hearing your thoughts.</blockquote><p>Do you feel the difference? The second proposal isn’t asking for a job. It’s starting a professional consultation. It shows I’ve thought deeply about their problem, anticipated future challenges, and am already guiding them toward a solution. It instantly elevates you above the sea of <em>“bidders”</em> and positions you as an <em>“expert”</em> partner.</p><h4>2. Build an Audience Beyond Upwork</h4><p>One of the most powerful actions you can take to advance your Upwork career occurs outside of the Upwork platform. Instead of constantly hunting for customers, you should build an audience that comes to you. Relying 100% on the Upwork algorithm to bring you work. You are completely at the mercy of their system.</p><p>I started a simple technical blog. I would take a complex problem I solved for a client (with their permission and all sensitive data removed) and write a detailed tutorial about it. I’d post links to these articles on <a href="https://www.linkedin.com/in/dollyaswin/">LinkedIn</a>. At the bottom of every article, I had a simple line: <em>“If you’re facing similar challenges, you can find me on Upwork.”</em></p><p>This strategy does two things. First, it builds social proof. A client who finds your <a href="https://www.upwork.com/freelancers/~01ffee6645c5c106ce">Upwork profile</a> through your insightful blog post is already convinced of your expertise. The trust is pre-built. Second, it gives you a powerful asset to use in your proposals. You can now write:</p><blockquote>“This challenge of migrating a legacy database with zero downtime is very similar to a project I documented in a case study here: [link to your blog post]. That post details the exact DMS strategy I used. I believe a similar approach would work well for you.”</blockquote><p>You are no longer just “<em>telling”</em> them you can do the work, but you are “<em>showing”</em> them with publicly available proof.</p><h4>3. Show the Messy Process, Not Just the Polished Result</h4><p>A screenshot of a finished website is pleasing. It’s clean. But high-quality clients, especially technical ones, are often more interested in the messy <em>“how”</em> than the polished <em>“what.”</em> They want to see how you think.</p><p>Create portfolio items that reveal your thought process. I started maintaining a public <a href="https://github.com/dollyaswin">GitHub repository</a> for my personal projects. I’d document my code, explain my architectural choices in the “<em>README”</em> file, and even leave comments about trade-offs I had to make.</p><p>For my Upwork portfolio, I moved beyond the &quot;<em>problem, solution, impact</em>&quot; framework for some projects and created deeper dives. I might include a short video screen recording where I walk through a piece of complex code I wrote or a link to a diagram explaining the system architecture I designed. Such an approach shows a level of transparency and confidence that is incredibly rare. It signals to a client, <em>“I have nothing to hide. Here is the quality of my thinking, presented openly for you to see.”</em></p><h4>4. Prove You’re a “Manager of One”</h4><p>This is perhaps the most critical trait for any remote professional. A <em>“manager of one”</em> is someone who doesn’t need a manager. They are self-motivated, proactive, and can take a goal and run with it without constant supervision. Clients are terrified of hiring freelancers who require micromanagement.</p><p>Your every interaction is an audition for this role. When a client posts a job with a vague description, a <em>“manager of one”</em> doesn’t just send a proposal with a price. They take control of the process.</p><blockquote>Thanks for the post. To move forward, it looks like we first need to define the project scope more clearly. I’ve attached a short questionnaire with 5 key questions. Once you’ve had a chance to answer those, I can draft a detailed project plan with milestones and a fixed price. This will ensure there are no surprises for either of us down the line.</blockquote><p>This response shows that you are not a passive task-taker; you are a strategic partner who can bring order to chaos. <em>You are already taking charge of the project before it has even started</em>. Such an approach is pure gold to a busy client.</p><h4>5. Let Your Work Do the Talking</h4><p>In a remote environment, what matters is the quality of the output, not how many hours you were green on Slack or Discord. Your reputation is built on the tangible results you deliver.</p><p>Obsessing over the quality of the work delivered to the client. This sounds obvious, but it’s amazing how many people forget it. When you deliver a project, don’t just hand over the files.</p><ul><li>Provide a clean, well-documented code.</li><li>Please prepare a concise handover document or video that explains how to deploy or manage what you’ve built.</li><li>Please follow up in a week to ensure everything is running smoothly.</li></ul><p>This <em>“after-sales service”</em> is what turns a one-time client into a repeat client who leaves a glowing, detailed 5-star review. And on Upwork, those reviews are the currency of trust. They are far more powerful than any proposal template you could ever buy.</p><h4>6. Master Asynchronous Communication</h4><p>In a remote work environment, clear, concise writing is not a <em>“soft skill.”</em> It is a fundamental, non-negotiable requirement. Every message you send is a sample of your work and a preview of what it’s like to collaborate with you.</p><p>Clients often fear hiring a freelancer who lacks communication skills or necessitates frequent meetings to complete tasks. Proving you are a master of asynchronous communication is a superpower on Upwork.</p><p><strong>The Amateur’s Approach:</strong></p><blockquote>Hi, I’ve read the job post. Looks interesting. Are you free to hop on a quick call sometime this week to discuss?</blockquote><p>This message creates work for the client. They must check their calendar, coordinate with you, and prepare for a possibly unnecessary meeting.</p><p><strong>The Professional’s Approach:</strong></p><blockquote>Hi,</blockquote><blockquote>I’ve reviewed your project brief for the database migration. It’s a well-defined project. To provide you with the most accurate proposal and timeline, I just need clarification on two points:</blockquote><blockquote>- You mentioned minimizing downtime. What is the acceptable maintenance window for the final cutover (e.g., under 5 minutes, up to 1 hour)? This will determine whether we use a DMS strategy or a simpler in-place upgrade.</blockquote><blockquote>- Are there any specific compliance requirements (like HIPAA or PCI-DSS) for the data being migrated?</blockquote><blockquote>Once I have this information, I can send over a detailed plan and a fixed-price quote. No need for a call at this stage unless you’d prefer one.</blockquote><blockquote>Thanks,”</blockquote><p>This message is a gift to a busy client. It’s clear, respectful of their time, and demonstrates that you are a proactive <em>“manager of one.”</em> You are guiding the process and making it easy for them to give you what you need. Such an approach is the hallmark of a true remote professional.</p><h3>Conclusion: Stop Hunting, Start Being Hunted</h3><p>When you adopt these principles, a profound shift begins to happen. You start winning better jobs with better clients. You deliver exceptional value, which leads to glowing 5-star reviews and long, detailed testimonials. Your Job Success Score hits 100%. You become <em>“Top Rated Plus.”</em></p><p>And then, the magic happens. The grind stops. You no longer have to spend hours every day scrolling through the job feed, sending out dozens of proposals into the void.</p><p>These are the hidden gems of Upwork. High-quality clients who don’t want to sift through a hundred low-quality bids. They use Upwork’s search filters to find the best of the best, and they invite you directly. They’ve already seen your <em>“story-driven”</em> portfolio. They’ve read your stellar reviews. They are already 80% sold on hiring you before you even write a single word.</p><p>This is the endgame. This is the sustainable career that the <em>“gurus”</em> and their <em>“secret formulas”</em> can never give you. It’s not a hack. It’s the natural outcome of building a reputation based on genuine expertise, clear communication, and a relentless focus on delivering value.</p><p>So, the next time you see an ad for a <em>“guaranteed Upwork success”</em> course, I urge you to pause. <em>The real investment isn’t in someone else’s template. The real investment is in yourself: in honing your craft, in learning to tell your story, and in treating every potential client not as a target, but as a partner.</em> That is the path that has sustained me, and it’s the only path I’d recommend.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee129c1b86f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Security Command Center in Google Cloud Exposed Hidden Backdoor in My Project]]></title>
            <link>https://medium.com/google-cloud/how-security-command-center-in-google-cloud-exposed-hidden-backdoor-in-my-project-744deeb9551b?source=rss-e67ce73e2cd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/744deeb9551b</guid>
            <category><![CDATA[gcp-security-operations]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[cloud-cybersecurity]]></category>
            <dc:creator><![CDATA[Dolly Aswin Harahap]]></dc:creator>
            <pubDate>Fri, 18 Jul 2025 04:35:22 GMT</pubDate>
            <atom:updated>2025-07-21T02:24:16.123Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6hzUruFWPbltn6Sj0wO3-w.png" /></figure><p>There’s a question that eventually haunts everyone who manages a complex cloud environment for a living. It doesn’t matter how well you designed it or how many best practices you followed. You look at the sprawling, intricate system you’ve built and maintained for years, and a simple, terrifying question whispers in the back of your mind: <em>What am I missing?</em></p><p>I’ve lived with this question for years. The B2B SaaS platform I helped build wasn’t new; it was a mature, well-oiled machine on <a href="https://console.cloud.google.com/">Google Cloud Platform</a>, the product of countless sprints and iterative improvements. Our security posture, on paper, was excellent. I could speak with confidence about our segmented networks, our principle of least privilege, and our end-to-end encryption. However, this confidence was not without flaws.</p><p>Our platform was a bustling city, not a static blueprint. Multiple engineering teams, each with their own priorities, were constantly building new structures, opening new roads, and sometimes, accidentally, leaving a side door unlocked. My architecture diagrams represented the city’s original plan, but the reality on the ground was far more complex and chaotic.</p><p>I was the city planner, but I had no real-time satellite feed. My knowledge was based on design documents, code reviews, and trust in my teams. But trust isn’t a security control. I needed data. I needed visibility.</p><h4>The Architect’s Blind Spot</h4><p>Why does this blind spot exist even in well-managed systems? It’s a phenomenon that’s called <strong>“</strong><em>Architectural Drift.</em><strong>” </strong>A system is designed with clean, secure principles. But over time, things change:</p><ul><li>A developer, needing to quickly debug a production issue, creates a firewall rule to allow SSH from their home IP and forgets to delete it.</li><li>A new microservice is deployed using a base container image that was secure at the time, but six months later, that image has known vulnerabilities.</li><li>A temporary service account created for a data migration is given broad permissions “just for the weekend” and becomes a permanent, over-privileged fixture.</li></ul><p>Each of these changes is a small, understandable deviation. But hundreds of them, over several years, create a massive gap between the <em>intended</em> design and the <em>actual</em> state of the infrastructure. This was my blind spot. I was managing the blueprint, not the living city.</p><h4>Turn on The Lights.</h4><p>My search for a “<em>satellite feed</em>” for our cloud city led me to take a serious look at <a href="https://cloud.google.com/security/products/security-command-center?utm_source=aqilix.com">Security Command Center</a> (SCC)<strong>.</strong> I needed to understand what it actually does. It isn’t just one tool; it’s a unified platform that performs four critical jobs 24/7:</p><ul><li><strong>It Discovers Your Assets<br></strong>It continuously maps everything you own in GCP—every VM, every storage bucket, every service account.</li><li><strong>It Scans for Misconfigurations<br></strong>It compares your assets against security best practices and compliance standards (like <a href="https://www.cisecurity.org/cis-benchmarks?utm_source=aqilix.com">CIS</a> and <a href="https://www.pcisecuritystandards.org/?utm_source=aqilix.com">PCI-DSS</a>).</li><li><strong>It Hunts for Vulnerabilities<br></strong>It actively probes your web apps and performs deep analysis of your running container images for known software vulnerabilities (<a href="https://www.cve.org/?utm_source=aqilix.com">CVEs</a>).</li><li><strong>It Watches for Threats<br></strong>It analyzes your cloud audit logs in real-time to detect suspicious activity like malware or brute-force attacks.</li></ul><p>You can start with the Standard Tier (<em>free</em>), which gives you basic misconfiguration scanning, or enable the Premium Tier (<em>paid</em>) to unlock the advanced vulnerability scanning and threat detection. I knew we needed the full picture.</p><h4>The Humbling Reality of a Good System</h4><p>I enabled SCC Premium on our staging environment first. Within hours, the dashboard lit up. The findings were a mix of simple mistakes and deeply hidden risks. Here are the sample misconfigurations found:</p><ul><li><strong>The Leaky Firewall Rule</strong><br>It flagged a firewall rule allowing RDP traffic (<em>port 3389</em>) from any IP address (<em>0.0.0.0/0</em>) to a group of Windows VMs. It was a remnant from an old project and had been forgotten for over a year.</li><li><strong>The Over-Privileged Service Account<br></strong>IAM Recommender found a service account for our CI/CD system with the Project Owner role. It was a ticking time bomb. SCC recommended a custom role with only the specific permissions needed to deploy to GKE and Cloud Run.</li><li><strong>Disabled MFA for Admin Users<br></strong>It alerted us that two highly privileged user accounts in our organization did not have <a href="https://en.wikipedia.org/wiki/Multi-factor_authentication">Multi-Factor Authentication (MFA)</a> enabled, a direct violation of our own security policies.</li></ul><p>But the most humbling discovery came from the vulnerability scanner. This is where the illusion of our “<em>well-designed system</em>” truly shattered. We believed our architecture was solid. We thought our critical services were secure. We were wrong.</p><p>The SCC scanner didn’t just look at our public-facing APIs. It looked everywhere. It flagged an internal-only microservice, a small data-processing tool that ingested logs and transformed them for our analytics dashboard. It wasn’t customer-facing, so it wasn’t on anyone’s priority list for updates. The scan revealed that this forgotten service was running on a container image that contained a vulnerable, outdated version of a common open-source library for handling images, ImageMagick.</p><p>I remembered the vulnerability: “<a href="https://imagetragick.com/?utm_source=aqilix.com">ImageTragick.</a>” It allowed an attacker who could upload a specially crafted image file to achieve remote code execution. While our main application had strict image validation, this internal service did not. A clever attacker who found a single, small entry point elsewhere could potentially upload a malicious file to a log bucket, trigger this internal service, and gain a powerful foothold deep inside our network.</p><p>Our elegant design was compromised by one forgotten component. Our CI/CD scanner had missed it because it only scanned <em>new</em> artifacts, not the “<em>architectural drift</em>” of what was already running. SCC didn’t just find the vulnerability; it gave us an “<em>Attack Exposure Score</em>” of 8.9, highlighting it as a critical risk. It was a humbling, terrifying, and incredibly valuable discovery.</p><h4>Use SCC Wisely Without Broke Your Wallet</h4><p>A powerful tool like SCC can generate a lot of data and, if you’re not careful, a high bill. The key isn’t just to use SCC, but to use it wisely. Here are the practical ways to maximize its value while controlling costs.</p><p><strong>1. Start Free, Win Early</strong><br>Before you even think about the premium price tag, enable the Standard tier across your entire organization. It’s free. It takes five minutes. Let it run for a week. It will immediately find your most glaring misconfigurations, like public storage buckets or open firewalls. Fixing these “<em>easy wins</em>” provides immediate security value at zero cost and builds momentum for a more advanced security program. It’s the best free lunch in Google Cloud.</p><p><strong>2. Go Premium with a Scalpel, Not a Sledgehammer</strong><br>The biggest mistake is enabling SCC Premium on every project on day one. You’ll be flooded with alerts and a hefty bill. Instead, take a surgical, risk-based approach:</p><ul><li><strong>Start with Production<br></strong>Enable Premium only on your most critical, production projects first. This is where your customer data lives, where your risk is highest, and where you’ll get the most value from threat detection and deep scanning.</li><li><strong>Fix, then Expand<br></strong>Work through the findings in your production environment. Build the muscle memory and automation for remediation. Once you have a handle on it, progressively roll out Premium to your staging environment, then to other important projects. This “<em>crawl-walk-run</em>” approach keeps costs predictable and prevents alert fatigue.</li></ul><p><strong>3. Filter Your Logs to Cut Costs<br></strong>A significant portion of the SCC Premium cost can come from Event Threat Detection, which analyzes your logs and is priced per gigabyte (<em>GB</em>) ingested. But not all logs are created equal. You don’t need to pay for threat detection on terabytes of verbose, debug-level logs from a development environment.</p><p>The solution is to configure your log sinks with exclusion filters. Before sending logs to be analyzed by SCC, you can create a rule to drop the noise.</p><p><strong>4. Embrace the Mute Button to Fight Alert Fatigue<br></strong>SCC will inevitably find things that are “<em>by design</em>” or are an accepted risk for your business. For example, it might flag a service account key that you know is intentionally long-lived for a legacy, third-party integration that doesn’t support short-lived tokens.</p><p>Instead of letting this finding create a new alert every day, use the mute functionality. Muting a finding tells SCC, “<em>I’ve seen this, I’ve accepted the risk, please stop telling me about it.</em>” This does two things:</p><ul><li>It cleans up your dashboard, allowing your team to focus on new, unknown threats.</li><li>It serves as a formal record that this risk has been reviewed and accepted.</li></ul><h4>Conclusion</h4><p>My journey with Security Command Center taught me a fundamental lesson: in a complex, evolving cloud environment, security isn’t a project you complete; it’s a state of continuous visibility. Building a well-designed fortress is the start, but you need a 24/7 watchtower to see the “<em>architectural drift</em>” happening in real-time.</p><p>SCC became that watchtower. It didn’t just give us a list of problems; it gave us a new way of seeing our own system. It replaced the nagging anxiety of the “<em>unknown unknowns</em>” with a clear, actionable picture of our real-world risk.</p><p>The truth is, your cloud environment is hiding things from you. Not because it’s malicious, but because it’s complex. It has drifted from your original design in a hundred small ways, creating blind spots you can’t see with your normal tools. <a href="https://cloud.google.com/security/products/security-command-center?utm_source=aqilix.com">Security Command Center</a> is the lens that brings those blind spots into sharp focus. The only real question is,<em> are you brave enough to look?</em></p><p>Answering that question is the first step. The next step is to know how to act on what you discover. If you need a seasoned expert to help you deploy Security Command Center, interpret the findings, and implement these cost-saving strategies, I’m here to help. Feel free to find and contact me on <a href="https://www.upwork.com/services/consultation/development-it-dolly-aswin-1471056956571004928">Upwork</a> to start the conversation. Together, we can transform your vulnerabilities into your most potent security assets.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=744deeb9551b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/how-security-command-center-in-google-cloud-exposed-hidden-backdoor-in-my-project-744deeb9551b">How Security Command Center in Google Cloud Exposed Hidden Backdoor in My Project</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Perjalanan 15 Tahun Menjadi Freelancer: #5 Tips Hidup Sebagai Pekerja Remote]]></title>
            <link>https://medium.com/@dollyaswin/perjalanan-15-tahun-menjadi-freelancer-5-tips-hidup-sebagai-pekerja-remote-ef24c9ad625f?source=rss-e67ce73e2cd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef24c9ad625f</guid>
            <category><![CDATA[remote-work-tips]]></category>
            <category><![CDATA[freelancers]]></category>
            <category><![CDATA[remote-work]]></category>
            <category><![CDATA[upwork]]></category>
            <category><![CDATA[online-freelancing]]></category>
            <dc:creator><![CDATA[Dolly Aswin Harahap]]></dc:creator>
            <pubDate>Sun, 29 Jun 2025 15:10:24 GMT</pubDate>
            <atom:updated>2025-06-29T15:10:24.009Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ksb9CXeeFPuUaDDhf6mz9Q.png" /></figure><p>Buka Instagram, lihat story kawan. Laptop di pinggir pantai di Bali, dan secangkir flat white di sebelahnya, dengan caption “<em>Work-life balance is not a myth</em>.” Geser lagi, lihat LinkedIn. Seseorang membagikan foto desk setup-nya yang super rapi, monitor melengkung, keyboard mekanik, dan daftar 10 tools produktivitas yang katanya “<em>wajib dimiliki para remote worker.</em>”</p><p>Sebagai orang yang sudah bekerja secara remote sejak tahun 2009 dan jauh sebelum pandemi membuatnya jadi tren, saya seringkali tersenyum melihat fenomena “<em>si paling remote</em>” ini. Seolah-olah, “<em>kerja remote</em>” adalah sebuah kompetisi tentang siapa yang punya tools paling canggih atau siapa yang bisa kerja dari tempat paling eksotis.</p><p>Saya senang melihat semakin banyak orang bisa menikmati fleksibilitas yang dulu saya perjuangkan. Tapi saya juga melihat banyak yang terjebak. Mereka fokus pada pernak-pernik “<em>kerja remote</em>”, bukan pada esensinya. Mereka sibuk mengoptimalkan tools, tapi lupa mengoptimalkan hidup. Hasilnya? Banyak yang merasa lebih capek, lebih terisolasi, dan batasan antara kerja dan hidup pribadi jadi makin kabur. Bangun tidur langsung buka laptop, makan siang sambil balas pesan di Slack, dan baru sadar sudah jam 8 malam saat punggung terasa pegal.</p><h3><strong>Tips Hidup Sebagai Pekerja Remote</strong></h3><p>Di tengah hiruk pikuk tren ini, saya sering kembali ke sebuah buku yang saya baca bertahun-tahun lalu dan membentuk cara saya bekerja hingga hari ini, yaitu: <a href="https://www.amazon.com/Remote-Office-Required-Jason-Fried/dp/0091954673"><strong>REMOTE: Office Not Required</strong></a> karya <a href="https://dhh.dk/">David Heinemeier Hansson (DHH)</a> dan <a href="https://world.hey.com/jason">Jason Fried</a>. Buku ini dirilis tahun 2013, sebuah era di mana “<em>kerja remote</em>” masih dianggap aneh dan hanya untuk para <em>freelancer</em> atau <em>programmer introvert</em>. Akan tetapi prinsip-prinsip di dalamnya terasa masih relevan daripada tips produktivitas terbaru yang beredar di media sosial.</p><p>Ada satu bab dalam buku ini yang jadi favorit saya, yaitu <strong>“Life As A Remote Worker”</strong> dan bisa kita lihat kenapa prinsip-prinsip lamanya justru jadi solusi untuk masalah-masalah remote working modern, terutama dalam konteks kita di Indonesia.</p><h4>1. Building a Routine (Membangun Rutinitas)</h4><p>Buku ini menekankan bahwa tanpa struktur kantor, kita harus menciptakan struktur kita sendiri. Dulu, kita punya ritual: bangun, mandi, sarapan, berjibaku dengan macet, sampai di kantor, bikin kopi, baru mulai kerja. Ritual ini, suka atau tidak, memberi sinyal pada otak kita: “<em>Oke, sekarang waktunya mode kerja.</em>” Saat <em>Working From Home</em>, ritual itu hilang. Ada yang bangun pagi 10 menit sebelum <em>meeting</em> pagi, cuci muka, dan langsung kerja. Kedengarannya enak, tapi ini bisa membuat otak bingung membedakan mana waktu kerja dan waktu istirahat.</p><p>Di kantor fisik, kita punya sinyal jelas bahwa hari kerja selesai, teman-teman mulai berkemas, lampu dimatikan, dan kita berjalan keluar kantor. Di rumah, sinyal itu tidak ada. Kita bisa terus bekerja sampai larut malam.</p><p>Untuk itu kita perlu membuat rutinitas kita sebagai penanda waktu kerja dimulai seperti setelah olah raga pagi, menyiram tanaman atau mengantar anak ke sekolah. Jangan lupa mandi sebelum bekerja agar tetap segar dan merasakan feel benar — benar bekerja. Begitu juga untuk berhenti bekerja kita perlu menciptakan rutinitas sendiri.</p><h4>2. Morning Remote, Afternoon Local (Pagi Remote, Siang Lokal)</h4><p>Ini adalah ide yang jenius. Buku ini menyarankan agar kita tidak terpaku di rumah seharian. Mungkin kita bisa fokus kerja dari rumah di pagi hari saat energi masih penuh, lalu siangnya kita bisa “kembali ke dunia nyata.”</p><p>Lupakan istirahat makan siang 1 jam yang terburu-buru. Kita semua tahu soal ‘jam rawan’ setelah makan siang, di mana produktivitas anjlok dan godaan untuk rebahan begitu kuat. Karena itu, saya mengadopsi ritme yang mungkin terdengar aneh: saya bekerja dari pagi hingga jam makan siang. Kemudian, dari jam 1 siang hingga jam 5 sore, saya <em>benar-benar berhenti</em>. Saya offline. Saya menjadi warga lokal, mengurus urusan pribadi, menjemput anak, berkontribusi untuk kegiatan sosial, atau bahkan tidur siang tanpa rasa bersalah. Setelah makan malam, saat rumah sudah tenang dan pikiran kembali segar, saya akan lanjut bekerja selama beberapa jam hingga sekitar pukul 10 malam.</p><p>Ritme ‘terbelah’ ini adalah <em>game-changer</em>. Jeda panjang di siang hari bukan sekadar istirahat, tapi sebuah <em>reset</em> total. Ini memungkinkan saya untuk hadir sepenuhnya dalam urusan keluarga dan tidak lagi merasa terburu-buru.</p><p>Tentu, butuh disiplin tingkat tinggi untuk bisa kembali membuka laptop setelah makan malam. Dan yang terpenting, komunikasi yang transparan dengan tim. Mereka tahu kapan saya ‘<em>menghilang</em>’ dan kapan saya akan kembali. Ini bukan tentang bekerja lebih lama, tapi tentang menyesuaikan jam kerja dengan ritme energi dan kebutuhan hidup saya, bukan sebaliknya.</p><h4>3. Compute Different (Pisahkan Perangkat Kerja )</h4><p>Buku ini menyarankan, jika memungkinkan, pisahkan perangkat untuk kerja dan untuk pribadi. Menggunakan laptop yang sama untuk bekerja dan keperluan pribadi atau keluarga bisa mengaburkan batas.</p><p>Jika belum memungkinkan untuk memisahkan perangkat, maka bisa dengan “<em>memisahkan secara digital.</em>” Di laptop yang sama, buat dua <em>user profile</em>: satu “Profile Kerja” dan satu “Profile Pribadi.” Di <em>profile</em> kerja, <em>bookmark browser</em> hanya berisi hal-hal terkait pekerjaan. Sebaliknya, di <em>profile</em> pribadi, isinya adalah hiburan. Batasan sederhana ini secara psikologis sangat membantu otak kita melakukan <em>context switching</em> dengan lebih mudah.</p><h4>4. Working Alone in a Crowd (Bekerja Sendirian di Tengah Keramaian)</h4><p>Manusia butuh kehadiran manusia lain, tapi tidak selalu butuh interaksi. Terkadang, berada di tengah keramaian tanpa harus bicara dengan siapa pun sudah cukup untuk mengusir rasa sepi.</p><p>Inilah alasan kenapa “WFC” (<em>Work From Cafe</em>) meledak di Indonesia. Karena ada yang datang ke kedai kopi bukan untuk networking, tapi untuk merasakan “energi” sekitar. Dia tetap bisa fokus pada pekerjaannya, tanpa merasa terisolasi. Istilahnya “<em>dia sendirian, tapi tidak kesepian</em>”.</p><p>Walaupun begitu, saya bukanlah tipe yang seperti itu, bagi saya cafe/kedai kopi itu berisik dan penuh distraksi. Saya adalah tipe orang yang butuh keheningan total untuk bisa fokus.</p><h4>5. Staying Motivated (Menjaga Motivasi)</h4><p>Tanpa ada atasan yang mengawasi, motivasi harus datang dari pekerjaan itu sendiri. Dari rasa puas saat kita menyelesaikan sebuah tugas, bukan dari pengawasan eksternal. Kuncinya, menurut saya, adalah memecah pekerjaan besar menjadi tugas-tugas kecil yang bisa dicentang. Buat <em>to-do list</em> harian yang realistis. Sensasi mencentang satu per satu tugas di daftar itu memberikan suntikan dopamin kecil yang membuat kita ingin lanjut ke tugas berikutnya. Fokuslah pada kemajuan, sekecil apa pun itu.</p><h4>6. Nomadic Freedom (Kebebasan Nomaden)</h4><p>Buku ini meluruskan bahwa “<em>nomaden</em>” bukan berarti harus keliling dunia. Ini tentang kebebasan untuk berada di tempat yang paling berarti bagi kita. Menjadi nomaden digital yang pindah setiap bulan itu melelahkan dan tidak cocok untuk semua orang. Ada cara yang lebih santai dan terencana, yaitu <em>workation </em>atau mengunjungi keluarga di luar kota.</p><p>Kebebasan ini bukan tentang pamer di media sosial, tapi tentang kualitas hidup yang nyata dan fleksibilitas untuk hadir di momen-momen penting keluarga.</p><h4>7. A Change of Scenery (Perubahan Pemandangan)</h4><p>Otak kita butuh stimulus baru. Bekerja di tempat yang sama setiap hari bisa membuat kita jenuh. Terkurung di ruangan yang sama setiap hari bisa membunuh kreativitas. Jika menjadi nomaden terasa terlalu ekstrem, perubahan pemandangan sederhana pun bisa sangat membantu.</p><p>Ini bisa sesederhana memindahkan laptop dari meja kerja di kamar ke meja makan. Perubahan kecil pada lingkungan fisik bisa memberikan kesegaran besar bagi pikiran kita.</p><p>Atau bisa juga pergi ke luar rumah untuk mencari tempat bekerja seperti perpustakaan ataupun <em>co-working space. </em>Perubahan sederhana ini dapat menjaga pikiran agar tetap segar dan mencegah kebosanan.</p><h4>8. Waktu Bersama Keluarga (Family Time)</h4><p>Salah satu janji terbesar “<em>kerja remote</em>” adalah “<em>lebih banyak waktu bersama keluarga.</em>” Tapi ini pedang bermata dua. Kita mungkin secara fisik, tapi butuh usaha untuk hadir secara mental.</p><p>Budaya kita sangat berorientasi keluarga, jadi poin ini sangat krusial. Keuntungannya jelas: kita bisa makan siang bareng pasangan atau melihat momen-momen kecil anak yang dulu sering terlewatkan.</p><p>Tantangannya adalah, kemampuan untuk menetapkan batasan. Misalnya, jika pintu ruang kerja tertutup, artinya kita tidak bisa diganggu kecuali darurat. Memisahkan waktu secara tegas justru membuat kualitas kebersamaan menjadi lebih baik saat kita benar-benar “hadir.”</p><h4>9. No Extra Space at Home (Tidak Punya Ruang Ekstra di Rumah)</h4><p>Banyak yang membayangkan <em>“pekerja remote”</em> punya ruang kerja khusus yang <em>instagrammable</em>. Realitanya? Masih banyak di antara kita yang tinggal di apartemen studio atau rumah kontrakan kecil.</p><p>Ini adalah realita bagi banyak pekerja di kota-kota besar. Anak kos yang tinggal di hunian mungil seringkali tidak punya pilihan selain bekerja dari kasur atau meja makan. Inilah kenapa poin “<em>Working Alone in a Crowd</em>” dibahas dalam bab ini. Kedai kopi, perpustakaan umum, atau <em>co-working space</em> bukan lagi kemewahan, tapi menjadi “kantor” alternatif yang vital.</p><h4>10. Making Sure You’re Not Ignored (Memastikan Kamu Tidak Diabaikan)</h4><p>Ketakutan terbesar <em>“pekerja remote”</em> adalah “<em>jauh di mata, jauh di hati.</em>” Khawatir tidak dapat promosi karena jarang kelihatan oleh atasan, atau proyek bagus diberikan kepada teman yang kerja dari kantor.</p><p>Jadilah proaktif. Berikan <em>update</em> progres secara teratur di grup Slack atau WhatsApp tanpa harus ditanya. Tulis ringkasan mingguan tentang apa yang sudah dicapai. Di dunia “<em>kerja remote</em>”, umumnya kontribusi lebih penting daripada kehadiran secara fisik. Tidak perlu lagi kekhawatiran akan diabaikan.</p><h3>Kesimpulan</h3><p>Tidak ada yang salah dengan berinvestasi pada <em>tools</em> yang membuat kita nyaman dan sehat. Sebuah kursi ergonomis yang menopang punggung, <em>adjustable desk</em> yang memungkinkan kita bekerja sambil berdiri, monitor besar yang memanjakan mata, keyboard mekanik yang memuaskan jari, atau bahkan <em>walking pad</em> untuk tetap aktif adalah investasi yang sangat baik untuk kesehatan jangka panjang. Saya sendiri menikmati beberapa di antaranya.</p><p>Akan tetapi, semua <em>tools</em> itu adalah pendukung, bukan inti. Tools itu tidak akan ada artinya jika kita tidak punya pondasi yang kuat. Pondasi itu sendiri terletak pada hal-hal yang tak lekang oleh waktu: disiplin diri, komunikasi yang baik, dan kemampuan untuk membangun batasan yang sehat. Ini tentang mendesain sebuah sistem kerja yang mendukung kehidupan kita, bukan sebaliknya.</p><p>Fenomena “<em>si paling remote</em>” mungkin akan terus ada, dan tidak ada masalah dengan itu. Tapi bagi yang ingin benar-benar membangun karier dan kehidupan yang seimbang dalam jangka panjang, mungkin ada baiknya kita sesekali menengok ke belakang, ke prinsip-prinsip dasar yang sudah terbukti berhasil. Karena terkadang, jawaban terbaik tidak datang dari tren terbaru, tapi dari prinsip-prinsip dasar yang sudah lama ada.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef24c9ad625f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>