<?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 Erik Lacson on Medium]]></title>
        <description><![CDATA[Stories by Erik Lacson on Medium]]></description>
        <link>https://medium.com/@elacson?source=rss-1bc8ac852d3c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Hvhb30QqHObYgY82</url>
            <title>Stories by Erik Lacson on Medium</title>
            <link>https://medium.com/@elacson?source=rss-1bc8ac852d3c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:38:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@elacson/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[Security Starts With Six Questions]]></title>
            <link>https://medium.com/@elacson/security-starts-with-six-questions-8f9c1f1de7ed?source=rss-1bc8ac852d3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f9c1f1de7ed</guid>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cybersecurity-governance]]></category>
            <category><![CDATA[goverance-risk-compliance]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Erik Lacson]]></dc:creator>
            <pubDate>Fri, 10 Apr 2026 01:24:40 GMT</pubDate>
            <atom:updated>2026-04-24T05:53:35.424Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why most startups and SMEs are exposed and how CSFLite helps close the gap.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*g7T267-Z49dmDJKB.jpeg" /></figure><p>A healthtech company was closing a major deal with a chain of HMO clinics. One requirement stood between them and the contract: HIPAA compliance documentation from all partners. They had an IT team. They had security tools. They couldn’t answer the questionnaire.</p><p>A retailer received a 10-point security compliance form from a new supplier, a condition to access the ordering system. Tools are in place, the IT team on hand, but no clear answers.</p><p>For a small travel agency it wasn’t a questionnaire at all. They got hit with ransomware their antivirus failed to catch. Four days of disruption. IT scrambling to fix it. Operations crippled. They eventually paid the ransom in bitcoin so they could go back to work.</p><p>Three different companies. Three different situations. They would have all said yes if asked if they have security. None of them could prove it when it mattered.</p><p>Security is often treated as a shopping list. Antivirus. Firewall. Maybe a VPN or a file backup tool. The tools get deployed, someone in IT gets assigned to handle it, and it’s assumed that things are covered.</p><p>Tools are useful. But they only tell you what’s installed. They don’t answer the questions that matter when something actually goes wrong, or when someone asks you to prove you’re secure. Who is responsible for security decisions? What happens when something gets through? Is your client data protected and how would you demonstrate that? What’s missing is a framework: a structured way of thinking about security and defining what secure actually looks like.</p><p>For organizations that take security seriously, the gold standard for frameworks is NIST CSF or ISO 27001. The problem is who they were built for. NIST CSF has 106 controls and was originally created for U.S. critical infrastructure and government agencies. ISO 27001 was designed for large enterprises and requires formal certification infrastructure. Both assume a dedicated security team, legal counsel, and the bandwidth for an 18-month implementation.</p><p>Most startups and SMEs have none of that. There’s no dedicated team, no security budget line, and no time allocated to anything that doesn’t ship product or serve customers. In this situation, frameworks are largely ignored and companies hope for the best. This isn’t a failure of effort. The frameworks that exist weren’t designed for this business stage, team size, or constraints. It’s a security gap nobody talks about.</p><p>Who owns security in the organization? What assets and data should be protected? How are they being protected? How would you know if something went wrong? What do you do when it does? How do you get back to normal?</p><p>These are questions any CTO, IT manager, or operations lead can answer. They don’t require a security specialist or a certification program. They only require someone to have sat down, think and decide. Most companies haven’t, not because they don’t care, but because nobody told them this was the starting point. The tools got bought, the IT person got assigned, and everyone assumed that things got secure along the way.</p><p>Compliance is not the only reason to build security foundations. It is not even the most important one. A breach does not care about your team size, your budget. It happens. Security foundations determines how badly it damages a business.</p><p>83% of SMBs are not financially prepared to recover from a cyberattack (VikingCloud, 2025 SMB Threat Landscape Report). That number isn’t about tools. Companies that get hit and recover know who owned security, had a response plan, and knew what they were protecting. Companies that don’t recover are still figuring out what happened while the damage compounds.</p><p>Security foundations work whether the threat is a compliance questionnaire or an attacker.</p><p>CSFLite came out of a simple realization: you can’t improve what doesn’t exist.</p><p>Most frameworks measure the maturity of security controls. CSFLite asks something basic: do they exist at all? It’s a lightweight implementation of NIST CSF v2.0, focused on 25 high-impact controls covering all six functions: Govern, Identify, Protect, Detect, Respond, and Recover. These controls represent the security baseline every organization should have before anything else: who owns what, what’s being protected, how to tell when something goes wrong, and what to do about it.</p><p>The assessment tool is intentionally simple. For each control, the answer is Yes, Partial, or No. Any technical person in the organization can answer it. It takes days, not months. The output is straightforward: what exists, what doesn’t, what to fix first.</p><p>CSFLite is open source. The framework, the questionnaire, and the assessment tool are all on <a href="https://github.com/eriklacson/CSFLite">GitHub</a>. The framework is free. For those who want guided help, <a href="http://leansecurity.pro/">Lean Security</a> offers fixed-scope assessments built around CSFLite.</p><p>Don’t find out your foundations are missing when someone else is already asking.</p><p>Start with the six questions in this article. If you can answer all of them clearly, you’re ahead of most. If you can’t, that’s the gap CSFLite was built to close. Run it yourself or have someone run it with you. The starting point is the same either way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f9c1f1de7ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Engineering Governance Pipelines]]></title>
            <link>https://medium.com/@elacson/engineering-governance-pipelines-626e81f6e110?source=rss-1bc8ac852d3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/626e81f6e110</guid>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[engineering-governance]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[goverance-risk-compliance]]></category>
            <dc:creator><![CDATA[Erik Lacson]]></dc:creator>
            <pubDate>Fri, 21 Nov 2025 06:59:48 GMT</pubDate>
            <atom:updated>2025-11-21T07:22:59.923Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jVsdplY6eb5FJ2RijJz7UQ.jpeg" /></figure><h3>The Limited Value of Written Policy</h3><p>Even in most modern organizations, compliance is still a set of static documents; shared cloud-drives with files of policies and procedures, and evidence captured in spreadsheets. The model worked when change was slow and infrastructure was built on hardware. In a world where cloud assets and code are continuously redeployed, the value of these artifacts in mitigating threats rapidly diminishes as they become outdated. Static documents cannot defend dynamically evolving systems.</p><h3>Governance as an Operations Architecture</h3><p>Engineering operates on the principle that what is not executed does not exist. Governance is not prescribed, controls are instantiated through code and configuration embedded into systems that continuously validate itself.</p><p>Automation pipelines verify compliance in each deployment or modifications in configuration. Controls expressed as code are continuously tested and verified. Logs and metrics are generated that readily confirms if a policy effective. Instead of waiting each quarterly audit, the system immediately states when a policy is breached. Compliance is no longer a static record of what was correct at a point in time; it becomes a dynamic system that continuously keeps itself in a correct state. Risk posture is constantly observable and actionable.</p><h3>The Role of The Frameworks</h3><p>Frameworks guide cybersecurity risk management by providing a structured set of standards, guidelines, and best practices. The widely adopted NIST Cybersecurity Framework (CSF) organizes the cybersecurity life-cycle into six high-level functions: Govern, Identify, Protect, Detect, Respond, and Recover. Each is divided into Categories that define broad outcomes and Subcategories that prescribe specific and measurable activities as shown in this example:</p><blockquote>Function: Identify (ID)Category: Asset Management (<a href="http://id.am/">ID.AM</a>) Subcategories: ID.AM-01: Physical devices and systems are inventoried. ID.AM-02: Software platforms and applications are inventoried.</blockquote><p>Governance Engineering translates the prescriptively normative domain of frameworks into an technical discipline. Policy becomes a reference model that is express as dynamic environment of executable controls written in code, automatically enforced and validated.</p><h3>Governance Engineering in Practice</h3><p>At the core of Governance Engineering are patterns that enable software environments to express policies, enforce control , generate evidence, validate itself, and allow organizations to observe security posture over time. The following components outline this model in practice.</p><p><strong>1. Policy-as-Code: Executable Rules</strong></p><p>Instead of a policy document with a rule such as <em>“All data at rest must be encrypted with managed keys”,</em> policy engines like the <strong>Open Policy Agent (OPA)</strong>, define the rule in Rego, a policy definition language. This is captured in an executable file and embedded into the CI/CD pipeline.</p><blockquote>deny[&quot;Encryption not enabled&quot;] {<br> input.storage.encryption != true<br>}</blockquote><p>Every build or configuration change triggers an automated check. When a policy is violated, such as storage resources deployed without encryption, the pipeline fails the build. OPA is open-source, vendor-agnostic and provides consistent enforcement across cloud infrastructure, microservices, CI/CD pipelines, and APIs.</p><p>Cloud vendor environments provide native policy-as-code implementation. Properties of resources and actions of Azure resources can be compared to business rules defined in JSON by A<strong>zure Policy</strong>. <strong>AWS Config Rules</strong> continuously records and evaluates the configuration settings of AWS resources.</p><p>Several cross-vendor approaches are also available. <strong>Hashicorp’s Sentinel</strong> integrates with Terraform’s ecosystem, providing support for version control, CI integration across multi-cloud infrastructure. Mentioned earlier, <strong>Open Policy Agent</strong> is an open-source vendor-neutral policy engine that can run on any cloud, Kubernetes platform, or CI pipeline. <strong>Checkov</strong>, an open-source static analysis tool, extends neutrality by scanning for misconfiguration in Infrastructure-as-Code settings for a variety of environments.</p><p>These services and tools enable managed and custom rules to check compliance against environment configurations. Cloud-vendor services are readily available options for their specific ecosystems, while vendor-neutral products offer portable governance that works across heterogeneous environments.</p><p><strong>2. Automated Evidence: System Generated Proof</strong></p><p>Manual compilation of evidence as screenshots, spreadsheets and documents has been a staple of the audit process. This can be replaced by automation that generate logs, metrics and scans directly mapped to framework requirements.</p><p>My open-source project <a href="https://github.com/eriklacson/CSFLite"><strong>CSFLite</strong></a>, offers scripts written in Python that maps Nuclei vulnerability scan results to <strong>NIST 2.0</strong> categories (e.g <em>PR.DS-01</em> for encryption issues, <em>DE.CM-08</em> for vulnerability management, <em>PR.AA-03</em> for authentication gaps). It generates timestamped CSV evidence files and severity-weighted heatmaps that represent the current risk posture or compiled to show historical trends.</p><p>Several security assessment tools can provide broad cloud-specific evidence generation. <strong>Prowler</strong> performs automated assessments of cloud accounts and compares it with industry standards, frameworks and benchmarks. <strong>ScoutSuite</strong> collects configuration data across environments and generates a unified audit report.</p><p>These approaches enable automated and continuously generated audit evidence. <strong>CSFLite</strong> demonstrates how outputs from scanners and monitoring systems can translate into evidence mapped directly to policy.</p><p><strong>3. Continuous Control Validation</strong></p><p>Modern technology environments change constantly. Code is deployed and infrastructure is modified continuously. Controls drift as a result. What was compliant during the last audit may not be compliant today. Continuous validation ensures that controls remain in place after changes are made.</p><p>At the code level, security checks can be made before changes are committed. For my own projects, I use <strong>pre-commit</strong> to enforce automated linting and security checks on every Git commit. Among the hooks I use is <strong>Bandit</strong>, a Python code scanner for common security issues and flags them early in the development workflow. The same checks run again in <strong>GitHub Actions</strong> before a merge into a production branch, insuring that nothing has slipped from the local hooks. Similar patterns are available in for other languages. ESLint for JavaScript, Brakeman for Ruby, gosec for Go, and SpotBugs for Java.</p><p>Most Policy-as-Code tool stack enforce continuous infrastructure validation. <strong>Checkov</strong> scans Terraform scripts before being applied. <strong>AWS Config</strong> evaluates resource changes against compliance rules. <strong>Azure Policy </strong>does the same for the Microsoft ecosystem, evaluating every resource continuously, checking for drifts from approved configurations policies.</p><p>Controls become reliable when each change is automatically verified against policy. The environment validates itself. Drift is detected immediately and not during the next audit cycle.</p><p><strong>4. Telemetry as Attestation</strong></p><p>Although operations and compliance are often treated as separate concerns, operational telemetry can serve both. Logs and metrics describe how controls behave in real time, making them natural inputs for continuous compliance.</p><p>A SIEM such as <strong>Splunk</strong> or <strong>Azure Sentine</strong>l can generate the live status of CSF functions. Simple scripts can map specific log events to CSF sub-categories: encryption and access-control activity under <em>Protect</em>, IDS or WAF alerts under <em>Detect</em>, and ticket-resolution metrics under <em>Respond</em>. These signals can be summarized in a dashboard for stakeholders and leadership.</p><p>One telemetry stream supports both operational monitoring and governance attestation. The environment becomes its own source of evidence, and control performance shows up in the same data teams already rely for operations. No duplicate collection and no parallel compliance systems</p><h3>Integrated Governance Pipelines</h3><p>Each of these patterns addresses a specific aspect of governance engineering. In isolation, they improve discrete parts of the compliance workflow. Integrated, they form a self-reinforcing governance pipeline where each stage compliments the next.</p><p><strong>The Reference Pattern:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TinpPB0GPbvDrWMnpyZ_aQ.png" /></figure><p><strong>Stage 1: Policy Definition: </strong>Policies exist as executable code in version control. Security requirements are expressed as rules that are programmatically evaluated . Policy changes deploy automatically when merged.</p><p><strong>Stage 2: Validation: </strong>Pre-deployment checks run automatically against policy definitions. Infrastructure code, application configurations, and container definitions validate before provisioning. Non-compliant changes block immediately with feedback to developers.</p><p><strong>Stage 3: Scanning: </strong>Automated scanners evaluate running systems and code. Endpoints are scanned for vulnerabilities, configurations are audited, code is analyse, container images are checked. Each produces structured output with findings, severity, and timestamps.</p><p><strong>Stage 4: Mapping: </strong>Scan results translate into framework language. Vulnerability findings map to control categories. Configuration issues aligned with governance requirements. Technical findings are translated into compliance context.</p><p><strong>Stage 5: Evidence Generation: </strong>Timestamped artifacts are generated, versioned and stored. Visual heatmaps show risk distribution. Evidence is collected automatically and continuously.</p><p><strong>Stage 6: Dashboard Updates: </strong>Visualization platforms present real-time posture. Metrics show coverage, risk scores, and trends. Executive views aggregate across frameworks. Dashboards update dynamically with each pipeline run. Policies can be adjusted based on outcomes.</p><h3>Cultural Shift: Governance as Architecture</h3><p>The approach doesn’t replace people but changes their role. They set the principles, define risk appetite, and determine intent. Systems enforce these with consistency at scale. Evidence is generated as the environment operates and attestation becomes continuous,</p><p>Governance engineering changes risk management from a reactive clerical task to an observable and measurable architectural capability designed to scale with the organization.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=626e81f6e110" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Operational Resilience: Quick Primer]]></title>
            <link>https://medium.com/@elacson/operational-resilience-quick-primer-f291d33c16e9?source=rss-1bc8ac852d3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f291d33c16e9</guid>
            <category><![CDATA[risk-technology]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[operational-resilience]]></category>
            <category><![CDATA[crisis-recocery]]></category>
            <dc:creator><![CDATA[Erik Lacson]]></dc:creator>
            <pubDate>Fri, 11 Jul 2025 01:04:17 GMT</pubDate>
            <atom:updated>2025-07-11T05:52:56.480Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*hGZAU8Ni_2YhxfoJ7aRazw.jpeg" /><figcaption>Image by: <a href="https://unsplash.com/@markuswinkler">Mark Winkler</a></figcaption></figure><p>The COVID-19 pandemic showed how quickly things can go from normal to chaos. What started as a health crisis brought the world into a standstill, exposing weak spots in how organizations have been managing technology, supply chains, process and communications.</p><p>Today, risks come in many forms: cyber-attacks, outages, supply delays, natural disasters, or even another pandemic. Operational resilience is making sure your your business continues to deliver when things inevitably go wrong.</p><h3><strong>Resilience as a Strategic Priority</strong></h3><p><strong>Risk is Complex and Interconnected</strong></p><p>The effect of a disruption cuts across several domains. Cyber attacks often leverage simple over-looked vulnerabilities. From there, seemingly unrelated critical systems across the network are eventually compromised. Customer-facing services are brought down, causing delays in orders, payments, and internal processes. Isolated risks results in more risks, and the impact can multiply across the organization.</p><p><strong>Expectations Are Higher</strong></p><p>Continuous availability is inseparable from quality. Customers today expect uninterrupted service. A single breakdown can weaken trust and undermine business reputation. Resilience directly impacts brand perception, customer loyalty, and ultimately equity value. It goes beyond best-practice, the resiliency of an organization is a competitive advantage.</p><p><strong>Regulatory and Stakeholder Pressure</strong></p><p>Investors are now more concerned about equity value during an unexpected crisis. A proactive approach to mitigating risks is an expected component of a business strategy. Regulators are also requiring oversight on operational resilience. Standards such as DORA in the EU and APRA CPS 230 in Australia shows the increase demand for risk accountability. This reflects the emphasis on resilience as a standard for good business governance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BUyOPLrKbmGvrlIsMlbA8g.jpeg" /></figure><h3><strong>Operational Resilience vs. Disaster Recovery</strong></h3><p>Disaster-recovery plans are focused on restoring systems after an incident. Operational resilience means keeping essential services up during a crisis with little or no impact to end-users and stakeholders. Shifting from recovery to resilience requires new mindset about people, processes, and technology. It involves identification of key processes, its respective failure points, and building necessary elements that will keep these process operation in an event of a crisis.</p><p><strong>Emphasis on People and Partnerships</strong></p><p>Effective resilience planning goes beyond technology. It requires a responsive workforce, along with external partners that align with your organizations standards for continuity and risk management. Responsibilities are clearly defined, and teams have the capacity to act decisively under pressure.</p><p><strong>Continuous Testing and Learning</strong></p><p>Real-world scenarios are tested regularly. Systems are monitored for early warning signs, and every incident or near miss is reviewed to improve future responses. Resilience is built around a culture of continuous learning and adaptation.</p><h3><strong>Supporting Frameworks</strong></h3><p>There are widely recognized frameworks that support compliance and strengthen internal resiliency programs for organizations. The following serves as good starting point for organizations starting a resiliency initiative.</p><p><strong>ISO 22301</strong> is an internationally recognized standard for operational resilience. It provides a structured business continuity management methodology for identifying risks, developing response strategies, and maintaining operations during disruptions. It highlights ongoing improvements and ensures key services continue to be delivered when businesses are faced with unexpected events. Obtaining and <strong>ISO 22301</strong> certification clearly demonstrates an organization’s commitment to operational resilience.</p><p>Originally developed for U.S federal agencies, the <strong>NIST Risk Management Framework (RMF)</strong> has been increasingly implemented by private-sector organizations. It provides a comprehensive, repeatable, measurable yet flexible framework for managing information system risks effectively. It uses an adaptable seven-step process that scales from small environments to large enterprises. Its controls can fit into new systems or integrated into existing ones without the need for a complete overhaul.</p><p>Another framework that’s widely adopted for best practices in managing IT services is the <strong>Information Technology Infrastructure Library (ITIL)</strong>. It presents a set of best practices for delivering effective and reliable technology services aligned with the business direction. <strong>ITIL </strong>emphasizes continuous-improvement practice services to match evolving business needs.</p><h3><strong>Building a Resilient Organization</strong></h3><p><strong>Identify Critical Services</strong></p><p>The foundation for resilience is a clear understanding of what process and functions are essential to the operational objectives of an organization. These should be identified and map to their dependencies (people, systems, data, third parties, etc ) and prioritized based on business impact. This serves as a reference point for an effective risk strategy.</p><p><strong>Plan for Failure</strong></p><p>An organization should adopt a mindset that anticipates failure as a rule and not an exception. It should embrace an engineering approach that revolves around redundancy and graceful degradation. Components supporting key services should be duplicated and designed to take over when one fails. These components should be be able to keep core functionalities operational even at lower quality during incidents of failure (e.g. manual payment processing when POS is down) This reduces the mean time to recovery (MTTR) and maintain client confidence during an outage.</p><p><strong>Empower People</strong></p><p>Resilience depends on people. Organizations should foster a culture of accountability. Teams should be trained regularly for failure scenarios. Roles must be clear, and staff must be empowered to act immediately during a crisis. Clear communication channels and well‑defined escalation paths are essential to an effective response. People are the ones who turn a resilience plan into practice.</p><p><strong>Include the Third-Parties</strong></p><p>Resilience extends to an organization’s partners and suppliers. Vendors must be continually assessed for their failure and recovery capabilities. Resilience requirements must be written into contracts, and fallback options should be established for critical third‑party services. Incorporating partners and suppliers into the resilience plan helps maintain operational continuity if any single dependency fails.</p><p><strong>Embrace an Iterative Mindset</strong></p><p>A resilience plan is not a one-time deliverable; it needs ongoing attention and continuous improvement. Teams should regularly review incident metrics and run scenario-based drills. Lessons learned must refine the plan’s components and processes. Regular testing and feedback keep the resilience program aligned with changing business priorities.</p><h3>The Bottom Line</h3><p>Operational resilience keeps the business running, protects its reputation, and preserves customer trust. Planning for failure, empowering people, and strengthening partnerships help an organization stay operational during a crisis. Building resilience today positions an organization to handle future disruptions with confidence.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f291d33c16e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Technology Risk: Beyond Cybersecurity]]></title>
            <link>https://medium.com/@elacson/technology-risk-beyond-cybersecurity-7b1e976094c9?source=rss-1bc8ac852d3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b1e976094c9</guid>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[risk-technology]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Erik Lacson]]></dc:creator>
            <pubDate>Sun, 23 Mar 2025 00:54:58 GMT</pubDate>
            <atom:updated>2025-03-23T00:58:37.032Z</atom:updated>
            <content:encoded><![CDATA[<p>Technology Risk often brings to mind cybersecurity threats like ransomware, data breaches, and phishing attacks. Although cybersecurity is crucial, technology risk covers many other issues that businesses must address to remain resilient and competitive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L4h26d0h7ghDfHw7GK3Raw.jpeg" /><figcaption>Photo:<a href="https://unsplash.com/s/photos/erik-maclean"> Erik McLean</a></figcaption></figure><h3>The Scope of Technology Risk</h3><h4>Operational Resilience and System Failures</h4><p>Critical business functions depend on complex technology systems. Network problems, software issues, cloud outages, and other failures can significantly disrupt operations.</p><p>Customers may be unable to access funds if a bank’s system goes down. Automated production lines or just-in-time inventory systems can experience costly disruptions if technology fails.</p><p>Mitigating these risks involves robust disaster recovery plans, fail-over systems, and continuous testing of IT infrastructure.</p><h4>Third-Party Risks</h4><p>Organizations increasingly rely on third-party vendors, such as cloud providers and outsourced services, to improve efficiency and reduce costs. However, this reliance introduces elements of risk.</p><p>A cloud provider outage can halt business operations entirely. Third-party vendors with weak security practices might expose sensitive customer data. Dependence on a single vendor, such as AWS or Microsoft Azure, creates potential single-point of failure.</p><p>Managing third-party risks requires thorough vendor assessments, clear contractual agreements, and continuous monitoring.</p><h4>Regulatory and Compliance Risks</h4><p>Governments and regulatory bodies worldwide enforce strict technology regulations. Non-compliance can result in significant fines and reputational harm.</p><p>Regulations like GDPR, CCPA, and PDPA set strict standards for data protection and breach reporting. Additionally, new guidelines are emerging to regulate technologies like AI, addressing ethical use, transparency, and algorithmic bias. The rapid adoption of digital banking and crypto technologies also demands updated compliance measures.</p><p>Organizations must proactively establish compliance programs and maintain ongoing engagement with regulatory bodies.</p><h4>Technology Obsolescence and Legacy Systems</h4><p>Many organizations still rely on outdated legacy systems, which introduce significant operational risks.</p><p>Legacy systems often lack necessary security updates, making them vulnerable to cyber threats. They may also struggle to integrate effectively with modern technologies, causing inefficiencies and higher maintenance costs. Skilled professionals to maintain these systems are becoming scarce.</p><p>A strategic technology modernization plan — including cloud migration, application updates, and phased system decommissioning — can mitigate these risks.</p><h4>Process Risk</h4><p>Technology-dependent processes introduce risks requiring careful oversight. Communication breakdowns within digital processes can cause inefficiencies. Automated system failures can disrupt operations. Human errors during system interactions can be costly. Weak governance over processes increases risks of fraud, waste, and compliance issues.</p><p>Organizations should establish strong internal controls, validate processes rigorously, and continuously monitor systems to manage process-related risks effectively.</p><h4>Emerging Technology Risks</h4><p>Rapid adoption of emerging technologies introduces risks due to unfamiliarity and integration challenges.</p><p>AI technologies present issues such as model bias and unexpected consequences on existing workflows. IoT device integration can create numerous security vulnerabilities. Blockchain, despite benefits like transparency, brings complexities in governance, scalability, regulatory uncertainty, and integration.</p><p>Organizations need an innovation strategy focused on training, rigorous testing, ethical standards, and standardized adoption practices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ty2cHnNgXWVmDdVub968Cg.jpeg" /><figcaption>Photo: <a href="https://unsplash.com/s/photos/marvin-meyer">Marvin Meyer</a></figcaption></figure><h3>Building a Holistic Technology Risk Framework</h3><p>Technology risk goes far beyond cybersecurity, encompassing operational resilience, regulatory compliance, third-party dependencies, legacy systems, process management, and the challenges associated with emerging technologies. As businesses accelerate digital transformation, a comprehensive approach to managing technology risks is essential.Proactive management of these risks not only minimizes disruptions but also provides a competitive edge in today’s increasingly technology-driven world.</p><p>Organizations must shift from a cybersecurity-centric approach to comprehensive technology risk management. This involves integrating technology risks into broader enterprise risk frameworks, promoting collaboration across departments, and leveraging continuous monitoring and advanced analytics for proactive risk assessment. Senior management and board-level involvement ensure alignment between technology risk management and business objectives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b1e976094c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Civilian’s Guide to Cybersecurity]]></title>
            <link>https://medium.com/@elacson/a-civilians-guide-to-cybersecurity-2bb6d411fddc?source=rss-1bc8ac852d3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/2bb6d411fddc</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[internet-security]]></category>
            <category><![CDATA[digital-privacy]]></category>
            <category><![CDATA[tech-guide]]></category>
            <category><![CDATA[online-safety]]></category>
            <dc:creator><![CDATA[Erik Lacson]]></dc:creator>
            <pubDate>Thu, 30 Jan 2025 08:22:09 GMT</pubDate>
            <atom:updated>2025-01-30T08:22:09.676Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ex6H34XqCgHL2xW6PFypbA.jpeg" /></figure><p>Cybersecurity often feels like a street fight between digital mobs and corporate establishments, with regular citizens left trying to navigate the chaos unharmed. Companies invest millions in defending against attacks, but regular individuals are often the easiest targets. Humans are inherently trusting and prone to mistakes: 82% of data breaches involve some form of human error, and a shocking 98% of social engineering attacks rely on manipulating trust (Verizon DBIR 2023; Trend Micro, 2023).</p><p>Why spend energy breaking through complex firewalls when one person can click a bad link or use “password123” on multiple accounts? Phishing emails, stolen credentials, and ransomware attacks all start with simple mistakes. Personal cybersecurity doesn’t have to be overwhelming. A few practical steps can prevent you from being an easy target. Here’s a straightforward guide on how civilians — like you — can stay safe out there in the online wild.</p><h3>1. Passwords: Your First Line of Defense</h3><p>“123456” isn’t a password — it’s an invitation for disaster. It’s like locking your door with a piece of string and assuming nobody will try to open it. Businesses enforce strict password policies for a reason, and you should hold yourself to the same standard.</p><p>Here’s why: Weak or reused passwords are a goldmine for hackers. If they crack one account, they often gain access to many others because people tend to recycle passwords. To protect yourself, make passwords unique and hard to guess. Think of something long, strange, and random, like “ToasterBanana42!” And yes, remembering these can be tricky, so use a password manager to safely store and manage them for you. Popular options include <a href="https://www.lastpass.com/">LastPass</a>, <a href="https://www.dashlane.com/">Dashlane</a>, and <a href="https://bitwarden.com/">Bitwarden</a> — each offers secure storage and convenient features for generating strong passwords.</p><p>Want to step it up? Enable two-factor authentication (2FA). This extra layer of protection means that even if someone gets your password, they’ll need a second verification — like a code sent to your phone — to access your account. It’s an easy win for your security.</p><h3>2. Phishing: Don’t Take the Bait</h3><p>Phishing attacks are cleverly placed mousetraps. They’re baited with something seemingly urgent or essential: an email from your bank, a delivery notice, a message from a friend, or an irresistible bargain. Take the bait, and you are handing over sensitive information.</p><p>If you receive something that feels unexpected or is written in strange grammar, ignore it. Don’t click links in suspicious emails. If it looks too legit but came unexpectedly, go directly to the website by typing in the official URL or call customer service to verify. Always check the email sender. A scammer might use “AmaoznSupport” instead of “AmazonSupport.” Spotting the difference can keep you out of trouble. Unless you’re expecting one, treat all attachments with suspicion and don’t download them. Phishing thrives on fear and urgency, but by staying cautious and double-checking, you can avoid getting caught in their traps.</p><h3>3. Updates: Annoying but Necessary</h3><p>We’ve all seen those annoying pop-ups that nag you to update your device while you are in the middle of doing something or about to leave work. Resist the urge to click “remind me later,” even if it’s tempting. Updates are crucial for security fixes and not just for new features. It’s easier to exploit outdated software because, of course, the flaws have not been fixed. Keep in mind, as long as hackers exist, there will always be flaws. Skipping updates essentially leaves your door wide open.</p><p>Enable automatic updates to ensure that you don’t forget. Updates often need a reboot to take effect, so restart your device regularly — for computers, at least at the end of each day, and for phones, at least once a week. Check for updates manually if you suspect you missed one. If you hear of widespread malware in the news, make sure you have updated your system with the patch for it. A few minutes of inconvenience can save you heaps of trouble.</p><h3>4. Public Wi-Fi: Don’t Trust It</h3><p>Public Wi-Fi networks are a hacker’s playground. Hackers often use these networks to launch attacks, making it difficult to determine who is behind them. These networks are set up with devices out-of-the-box and are mostly not encrypted. Any device on the same network is potentially vulnerable.</p><p>Avoid accessing sensitive accounts. Do your online banking, shopping, or any financial transactions when you get home or are on a secure network. Protect your connection from snoopers by encrypting it using a VPN. Forget the network when you’re done. Don’t let your device auto-connect next time. Public Wi-Fi may be convenient, but it’s far from secure. Treat it with caution.</p><h3>5. Think Before You Share</h3><p>Each post you make is a clue to your personal life. These clues are valuable to someone paying close attention. Small details such as vacation plans, daily routines, or even small habits can, surprisingly, be used to exploit you. By revealing too much online, you make yourself vulnerable to identity theft, scams, or even physical security threats.</p><p>Avoid posting your address, vacation dates, or any sensitive personal details. Ensure only trusted friends can see your posts by reviewing your privacy settings. Before you post anything, consider if someone could use this information against you. Keep your digital footprint small and make it secure.</p><h3>6. Lock Down Your Wi-Fi at Home</h3><p>Your home Wi-Fi is the gateway to your digital life, connecting your personal devices and data to the rest of the online world. Default router passwords are often public knowledge, and weak network settings leave it exposed and vulnerable.</p><p>Change the default router password to something strong and unique. Ensure that you are using the latest, most secure standard (WPA3 at the time of this writing). Unless you absolutely need it, disable remote management.</p><p>Think of your Wi-Fi router as the gate to your digital life. Keep it locked and fortified.</p><h3>Final Thoughts</h3><p>Keeping yourself safe online does not have to be technically overwhelming. You can take small, simple, and intentional steps to make yourself a more difficult target. Start with one or two tips from this guide, and slowly build the rest into your habits.</p><p>Online security isn’t just for businesses — it should be for everyone. With a bit of effort, you can go about your digital life with confidence and peace of mind.</p><p>If you have questions, feedback, or suggestions on improving this guide, feel free to leave a comment. Your can help make online safety a more accessible topic for others. Stay safe, stay informed, and let’s continue the conversation!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2bb6d411fddc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Three technologies for the “new normal”]]></title>
            <link>https://medium.com/@elacson/three-technologies-for-the-new-normal-4ffa1105f2bc?source=rss-1bc8ac852d3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ffa1105f2bc</guid>
            <dc:creator><![CDATA[Erik Lacson]]></dc:creator>
            <pubDate>Tue, 26 May 2020 12:47:55 GMT</pubDate>
            <atom:updated>2020-05-27T06:56:28.178Z</atom:updated>
            <content:encoded><![CDATA[<p>Apart from news updates on COVID-19, perhaps the most popular topic around the Internet these days is what our “new normal” lives will be like. As our hope for a vaccine still remains quite distant, and future pandemics have become more imaginable, people from different sectors and disciplines are figuring out ways to help us adapt to this new and different world.</p><p>We the geeks of <a href="https://metatechlab.io/">MetaTech Lab</a> haven’t been immune (pun intended!) to the temptation to be among the “new normal” pundits. After many virtual discussions, we’ve decided to refocus our efforts in three technology areas that we believe are relevant to post-pandemic life.</p><p><strong>Smart Urban Farming</strong></p><p>Lockdowns and social distancing measures have disrupted agricultural production and supply chains — making food availability a cause for anxiety.</p><p>The risk of infection in crowded stores and the need for self-sufficiency are shifting mindsets towards growing our own food. Interest in personal and community urban farming has increased. There are reports of heightened demand for seeds in the U.S. as people start planting “pandemic gardens.” In the Philippines, people growing their own food will be part of the ‘new normal’ according to Glenn B. Gregorio, director of Southeast Asian Regional Center for Graduate Study and Research in Agriculture (SEARCA) Director, saying in a <em>Manila Bulletin</em> article.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*FVyS-rvq7mPTBzdT3edyNg.jpeg" /><figcaption>Photo by: <a href="https://www.flickr.com/photos/kevinkrejci/">Kevin Krejci</a></figcaption></figure><p>Adopting the smart farming concept and applying it to a smaller urban context, <a href="https://metatechlab.io/">MetaTech Lab</a> is working on tech products to make growing food more accessible to city dwellers. Smart farming, or precision agriculture, leverages cloud applications and Internet of Things (IoT) devices to monitor, analyze and automate the process of growing plants. The benefits include reduced production costs, better yield, and improved product quality.</p><blockquote>For the urban farmer, MetaTech Lab is developing <strong>InstaGreens, </strong>a software-managed and sensor-monitored system designed to automate the grow process inside small building spaces.</blockquote><p>It allows one to have a vegetable garden in small apartments and high-rise condominiums units. It autonomously provides water and nutrients to the plants based on soil and environment conditions. We are looking into adding artificial lights for ideal indoor settings. The aim of this product is to reduce the time and effort involved in nurturing plants in an urban setting. The software application can also provide preset parameters for specific crops, allowing people with little knowledge of agriculture to get started growing food quickly.</p><p><strong>Asset and Logistics Tracking</strong></p><p>Home delivery from groceries, restaurants and even non-essentials like exercise equipment and vintage wine has exploded as quarantined communities are restricted from going out. In this new retail environment, concerns will be less about managing stores and more focused on bringing products to customers who can’t or won’t leave their homes. Social distancing concerns will also accelerate the need for contact-less supply chain management. Filling out, passing around and signing forms are already considered a health risk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*AlCuf6Ol9zMiDh1b30oyoA.jpeg" /><figcaption>Photo by: <a href="https://www.flickr.com/photos/kamshots/">Kamiar Adl</a></figcaption></figure><blockquote>Even before the start of the global lockdowns, we had been working on technologies for tracking physical assets. This includes applications from <strong>contact-less processing of warehouse package deliveries to locating maritime and land vehicles in real-time.</strong></blockquote><p>With the same technology, we’re now building applications to improve post-pandemic supply chain logistics. Using IoT devices in vehicles or attached to cargo, data about the location, storage conditions and when assets arrive at specific locations can be gathered. By validating exactly where and when assets arrive, payments, inventory and other administrative actions are automatically triggered. This enables a supply chain management facility that requires minimum close contact and interaction.</p><p><strong>Community Networks</strong></p><p>So much more of life is now happening online. Curtailed by quarantine, we work, play, study and interact with others largely through the Internet. This happened almost seamlessly for those of us with the right resources. People like us in the tech world joked, “I didn’t realize I was already living in quarantine even before COVID-19.”</p><p>However, the shift towards life online worsens the so-called digital divide — especially in the Philippines, where majority of the population is still not connected to the Internet.</p><blockquote><em>“Where those networks [the Internet] do not exist social distancing is much harder on people, if not outright impossible.” — </em>Electronic Frontier Foundation</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xb-webnPYG1R3RD0Oy_RwQ.jpeg" /></figure><p>Community networks are small telecommunications infrastructures built and maintained by small, private groups of people. A community network provides a sustainable solution for the connectivity gap in urban and remote areas that are too far, sparsely populated, or too poor to afford commercial connectivity.</p><blockquote>With this solution, the community has its own local network that then connects to the Internet and provides basic online services such as email, web, video and voice communication. It also serves as infrastructure for IoT sensor devices that<strong> enables data-driven smart community services grassroots.</strong></blockquote><p>In partnership with local governments and NGOs, <a href="https://metatechlab.io/">MetaTech Lab</a> aims to help communities develop the capacity to build and maintain their own network. This can be as simple as extending the coverage area of a broadband Internet connection to setting up a community-wide wireless mesh network infrastructure using community-owned leased lines to the Internet. We advocate flexible and cost-effective solutions by working with open source software and hardware components.</p><p><a href="https://medium.com/@elacson/a-tech-startups-unlikely-involvement-fighting-covid-19-and-3-things-we-learned-829949250c1a?source=friends_link&amp;sk=384f9152b059099c8c903af040425335">As a startup that began operations just before the pandemic</a>, we’ve had to quickly rethink where we stand in relation to this challenge that both the entire world and we as a small company face. We take comfort in the belief that humans are the most adaptive species in the planet.</p><p>Email me to learn more about <a href="https://metatechlab.io/">MetaTech Lab</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ffa1105f2bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A tech startup’s unlikely involvement fighting COVID-19 and 3 things we learned]]></title>
            <link>https://medium.com/@elacson/a-tech-startups-unlikely-involvement-fighting-covid-19-and-3-things-we-learned-829949250c1a?source=rss-1bc8ac852d3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/829949250c1a</guid>
            <dc:creator><![CDATA[Erik Lacson]]></dc:creator>
            <pubDate>Mon, 06 Apr 2020 07:53:39 GMT</pubDate>
            <atom:updated>2020-04-07T12:38:05.087Z</atom:updated>
            <content:encoded><![CDATA[<p>We couldn’t have chosen a worse time to start a company. Around four weeks after we moved into our brand-new office, news reports circulated about a new virus having infected dozens of people in Asia. This would eventually turn into the global pandemic we now all know as COVID-19. So here we are, a tech startup literally at its infancy trying to hold things together in the midst of a lockdown declared in Metro Manila last March 15.</p><p><a href="http://www.metatechlab.io/">MetaTech Lab</a> is an early-stage research and development team of six people that started last December 2019 in the Philippines. We build Internet of Things solutions founded on our shared belief in “technology for a better world.”</p><p>However, we thought that fighting COVID-19 was way out of our league. So when the lockdown was declared, we did the best thing we thought we could do: stay home. Having been organized around remote collaboration, we were confident that we could continue working during the community quarantine. Although as a company that works on IoT hardware devices, building physical things together virtually was still going to be challenging. On the first workday of the lockdown, I sent out operational guidelines. As a by-the-way, it included a brief note that we should respond to any opportunity to help the community during this time of crisis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*0rZlGOWkFGUDn2HGU4DcSg.jpeg" /><figcaption>A blurry photo of us taken in Bacolod City just three days before the Metro Manila lockdown. We were there to do a test deployment of a smart irrigation system. This was the last time we were all together in person.</figcaption></figure><p>Three days later, I saw a message from a friend in one of the Viber chat groups. It was a link to a <a href="https://www.thingiverse.com/thing:4166543?fbclid=IwAR32UIomBqztjaOC2sdbmETFJ7kstOcBLnwtBdrEX9GJag6Nvk0-yazpHC4">Thingiverse </a>post for a 3D-printed face shield frame that could be used as personal protective equipment (PPE) by medical workers in the frontline. The friend’s partner, an emergency doctor, wanted to know if we could fab the frame. Apparently, there was a supply shortage in the country and hospitals could not provide their personnel with enough PPEs to deal with the pandemic.</p><p><a href="http://metatechlab.io/">MetaTech</a> Lab has 3D printers for enclosing our IoT device prototypes.Fortunately, our design engineer Joseph Villaneuva took these home as part of our continuity plan, so we had access to them. The team decided to produce face shield frames for free, distributed by the Philippine College of Emergency Medicine (where my friend’s ER doctor partner is connected) to various hospitals in Metro Manila. We made a modest commitment to produce around 10 frames per day.</p><p>Four days after lockdown, we posted on Facebook asking for support by sending us spare 3D printing filaments (the “ink” used to fab products), since we didn’t have enough at hand. It was shared 33 times in 24 hours. It’s not a lot but much more than what we expected. The first to respond were people with their own 3D printers who wanted to help us print on their own. One of them was a 16-year-old teen, Marcus Chu, who went viral on Facebook after my wife’s post about him was shared 160 times. In the next 48 hours, his story was picked up by <a href="https://www.esquiremag.ph/long-reads/features/marcus-chu-3d-face-shields-a00204-20200323?fbclid=IwAR1tkCLqyzZ7lCF91-Fk0gMIPTfyM8yTRpiIoQ2X1MXhwQab49veWXhpcFM">Esquire Philippines</a>, <a href="https://twitter.com/cnnphilippines/status/1242335804292083713?fbclid=IwAR2tN_mugjHfuwiYj8rBBRpSAt2-3gpKHWijoGr7vnvt2kTT3-J3Yb-mjXw">CNN Philippines</a>, and ABS-CBN. A few days after this, <a href="https://www.reuters.com/video/watch/idPqtu?now=true&amp;fbclid=IwAR250oK4eXVJ8Fyathc_i-HSUf1scZL6fm_hIJryyZIGo-coAv3kr_PIeHI">Reuters</a> did a wire story on him, which was published by the New York Times, The Telegram, and many other international publications. Even a Mashable journalist got in touch.</p><p>On March 21, 6 days after lockdown, we delivered our first set of face shields to two Metro Manila hospitals. We were touched by the photos of doctors and other hospital staff wearing them on duty, and prompted to find a way to step up our effort.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/528/1*_BPIS2CEVer6oUBMbFwT_w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/528/1*2n8GPxV_6AqPmrSwOB66Sw.jpeg" /></figure><p>We were not the only ones doing this. <a href="https://www.facebook.com/groups/2831079386941950/">3D Printing For A Cause</a>, a community in Facebook, has been producing face shields and distributing them nationwide. Based on their numbers, at the time we started, country demand was around 14,000 units with the supply reaching 3,000 units. (As of this writing, demand has increased to 30,000 units and is still growing). Obviously, our commitment to produce 10 frames a day was not going to significantly improve the collective effort. The pandemic was also getting more personal and less statistical. Casualties were no longer numbers but had names and faces. Several people that we knew were either working at the frontlines, infected, or worse, had died from the disease.</p><p>The effort to scale started with a contact of a contact of a contact (all via social media) who offered to lend us several idle 3D printers. We were all working from home so we needed space. I was introduced online to Mario Carreon, a professor at the University of the Philippines Department of Computer Science who suggested that we could use a space in their campus building. I ended up sending a proposal to Ferdinand Manandeg, dean of the College Engineering. The idea was to have a space where we could host around 15 borrowed 3D printers. MetaTech would get it up and running, and it would be kept operational by volunteers. On the morning of March 23 (8 days after lockdown), Dean Manandeg called me to discuss the details of our proposal. The following day, I received an email from Gerard Denoga, the associate dean for research , informing me it was a GO.</p><blockquote>The 3D Printer Farm became operational on April 3. Before this, we were able to deliver 225 shields to 11 hospitals in Metro Manila and one province in Luzon since we started. With the 3D Printer Farm, we expect to produce 150 face shields per day. We are also looking into producing other essential medical equipment and supplies as more and more people start 3D printing PPEs.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FIgxPIvJHmRo0TIKE0yMSg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XdJFCu5958F4cBbFMjm9EA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CFk-d-fcn3De45mpJq7PjQ.jpeg" /></figure><p>This was a project that we never anticipated doing. It all happened only in a span of two weeks. Our company was still only establishing our foundations. But now, like everyone else, we are facing this threat to our survival — both as a business organization and as human beings. We were not prepared, to say least.</p><p>But our company was formed on the premise that technology would make the world a better place. There’s not a better time for us prove our commitment to our values. Like any pivotal and challenging situation, the last two weeks left us learning three important lessons.</p><p><strong>Lesson 1: Solutions don’t have to be elaborate, they just need to solve the problem immediately.</strong></p><p>We are not a 3D printing company. We take pride in ourselves as a diversely talented research and development team capable of delivering advanced technology solutions. However, the immediate problem was lack of face shields. There were already face shield designs out there being used by other groups. So we took the shortest path and used these templates to start producing right away. Designs were modified only after we got feedback from the health workers using our output. Our goal was to get face shields to the frontline as soon as possible and we didn’t let the design improvement process get in the way of that.</p><blockquote>Often, as people involved with technology, we get stuck with the need to deliver something “cutting-edge.” In the process of trying to deliver the “best” solution, we lose sight of the problem we’re trying to solve or its immediacy. It’s best to focus on delivering the most value in as little time and with as little resources as possible. We can always improve things as we go along.</blockquote><p><strong>Lesson 2: Decentralized and open collaboration works in times of crisis.</strong></p><p>As mentioned earlier, several groups as well individuals with 3D printers also volunteered their time and resources to produce the face shields. We were all doing it independently, but design improvements were shared around the community. Template files were being passed around on a daily basis. Even the 3D printer manufacturers like Creality and Prusa shared new or improved templates. Each group had its own way of delivering to various hospitals. In our case, we work with the Philippine College of Emergency Medicine, which handles distribution to various hospitals. We just focus on producing as many shields as quickly as possible.</p><blockquote>Because we were working in a decentralized and open manner, the local maker community (whether 3D printers or hand-makers) was perhaps among the first to get PPEs to our medical frontline personnel.</blockquote><p><strong>Lesson 3: Social responsibility is not exclusive to big and highly profitable companies.</strong></p><p>We often associate corporate social responsibility with companies that are big enough to spare a bit of its profit to help others. We are just a small, early-stage, 6-person startup working on our first set of projects. We are, honestly, far from profitable. We were just looking for a possible opportunity to help regardless how small. We responded with whatever we had, namely, our 3D printers and our social media network.</p><blockquote>Despite very limited resources, helping in the COVID-19 fight didn’t disrupt our operations nor negatively affect our bottom line. Every business is capable of helping, regardless how small. We just need to start with a sincere intention.</blockquote><p>As we enter the last scheduled week of the lockdown but anticipating an extension, the group at the UP College of Engineering 3D Printer Farm is already looking at producing other essential medical devices and supplies for the frontline.</p><p>Looking beyond the pandemic, MetaTech continues research and development in IoT applications for agriculture and urban management. As people of science and technology, we firmly believe that together we can overcome and win this fight.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=829949250c1a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>