<?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 Ashok Sharma on Medium]]></title>
        <description><![CDATA[Stories by Ashok Sharma on Medium]]></description>
        <link>https://medium.com/@ashok.sharma?source=rss-3fa24f172244------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*_7gEbuQEQcB9Snb7.jpg</url>
            <title>Stories by Ashok Sharma on Medium</title>
            <link>https://medium.com/@ashok.sharma?source=rss-3fa24f172244------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:21:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ashok.sharma/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[Why SOC Sovereignty Is No Longer Optional — Global and INDIA perspective]]></title>
            <link>https://medium.com/@ashok.sharma/why-soc-sovereignty-is-no-longer-optional-global-and-india-perspective-48f87e8f129c?source=rss-3fa24f172244------2</link>
            <guid isPermaLink="false">https://medium.com/p/48f87e8f129c</guid>
            <category><![CDATA[cisco-security]]></category>
            <category><![CDATA[splunk]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[digital-sovereignty]]></category>
            <category><![CDATA[sovereign-soc]]></category>
            <dc:creator><![CDATA[Ashok Sharma]]></dc:creator>
            <pubDate>Tue, 13 Jan 2026 08:50:27 GMT</pubDate>
            <atom:updated>2026-01-13T08:50:27.909Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rC8xQgKiGBtR_Q4PxEK7eg.png" /></figure><h3>Why SOC Sovereignty Is No Longer Optional — Global and INDIA perspective</h3><blockquote>For much of the last decade, governments and regulated industries operated under a comforting assumption — <strong>If sensitive security data stayed within national borders, sovereignty was intact.</strong> That assumption no longer survives contact with reality.</blockquote><p><em>A disclaimer; I am technical sales architect with Splunk (part of Cisco) and have repeated discussions on realising sovereignity for customers. The current politcal situations have more than tested and pronounced the need for sovereignity in totality. For nations that seek risk aversion from unilateral foreign regulation mandated changes, this is an inevitable part of strategy.</em></p><p>In my work as a senior sales architect leader, working alongside GSI partners with CISOs, and security directors for modernising SOCs, I’ve watched that belief unravel in real time. The stress is not theoretical.</p><p>In 2025, state-backed actors exploited cloud update channels to disrupt infrastructure across APAC. Regulators demanded explanations. Operators discovered that their “resident” SIEMs depended on outbound telemetry for remote data correlation and operational AI operation insights. This made larger forensics combersome and dependent of multiple factors.</p><p>The realisation on their sovereign story set in —<em> </em><strong><em>Data residency requirements were met but overall control was still lost</em>.</strong> Since the sovereignty narrative itself was shaped through regional proxies of being resident, while the true response authority sat elsewhere.</p><p>The harder truth is this: Sovereignty is not decided by where data sleeps at night. It is decided by who controls analytics, decision-making, and response when systems are already under pressure.</p><p>This shift is not ideological. It is empirical, drawn from repeated incidents where external legal, technical, or commercial dependencies constrained national response at the worst possible moment.</p><p>That is why the global conversation, especially the conversation in India has moved decisively beyond data localisation toward full Security Operations Center (SOC) sovereignty.</p><p><strong>Sovereignty Is a Control Problem, Not a Hosting Problem</strong></p><p>A sovereign SOC, viewed through regulatory and policy lenses, means jurisdictional authority across the entire security lifecycle, not just infrastructure ownership. That lifecycle includes:</p><p>• Telemetry ingestion and normalization<br>• Detection logic and correlation<br>• AI-assisted triage, prioritization, and resolution<br>• Automated and human-directed response<br>• Evidence preservation and forensic replay<br>• Auditability and regulator-facing transparency</p><p>The distinction is no longer subtle. <strong>Post Schrems II regulatory analysis</strong> made it explicit: data location alone does not prevent foreign legal access if control remains external. <strong>European security agencies have echoed the same conclusion — sovereignty depends on technical and organizational control, not hosting geography.</strong></p><p>The implication is uncomfortable but unavoidable — <em>A SOC can be locally hosted and still be non-sovereign</em>. The Triggers Driving Nations Toward Sovereign SOCs</p><p><strong>Trigger 1: Extraterritorial Legal Reach</strong></p><p>Statutes such as the U.S. CLOUD Act explicitly permits lawful access to data under the control of domestic service providers, regardless of where that data is stored. Since 2020, regulators across Europe and Asia have increasingly acknowledged this as a structural risk particularly for government and critical-infrastructure SOCs.</p><p>During breach investigations, this leads to a question that permanently alters trust models:</p><blockquote>Who else could legally compel access to telemetry, metadata, or investigative artifacts?</blockquote><p>Once that question is asked, SOC architecture is no longer a purely technical discussion.</p><p><strong>Trigger 2: Cloud Concentration as Systemic Risk</strong></p><p>More than 60% of public-sector security workloads globally now depend on a very small set of hyperscale providers. That concentration risk extends beyond availability into geopolitics and supply-chain exposure.</p><p>Over the last decade, we’ve seen how these risks materialized:</p><p>• Geopolitical tensions affecting a provider’s ability or willingness to operate in specific regions<br>• Export controls, sanctions, or regulatory conflicts introducing uncertainty into service continuity</p><p>National cyber-risk frameworks increasingly classify this as systemic risk. These are single points of operational failure whether triggered accidentally or deliberately.</p><p><strong>Trigger 3: AI Becomes the De Facto Decision Layer</strong></p><p>Modern SOCs face a structural imbalance that no amount of hiring will fix:</p><p>• Alert volumes growing 20–30% year over year<br>• Analyst headcount growing in low single digits<br>• AI systems increasingly making prioritisation and response decisions</p><p>Security agencies now warn that <strong>opaque or externally governed AI introduces governance, audit, and accountability risks</strong>, especially in regulated environments such as defense and critical infrastructure.</p><p>When AI becomes the decision layer, sovereignty follows control of the model, not the dashboard.</p><p><strong>India’s Sovereign SOC Imperative: Scale, Law, and Accountability</strong></p><p>India’s push toward sovereign SOC architectures is not abstract or ideological. It is driven by scale, law, and consequence.</p><p><strong>Verifiable India-specific realities:</strong></p><p>• 1.39 billion Aadhaar numbers underpinning digital public platforms<br> • ₹14,083 crore in reported digital payment fraud in FY 2022–23<br> • 1.39–1.6 million cybersecurity incidents reported annually<br> • Mandatory 180-day log retention and six-hour incident reporting for critical entities</p><p>At this scale, SOC failure does not remain technical. It escalates directly into regulatory action, financial loss, and political accountability.</p><p><strong>Why SaaS-First SOC Models Struggle Under Indian Conditions</strong></p><p>Regulatory reviews in India consistently surface the same friction points with SaaS-first SOC models:</p><p>• Control planes located outside India<br>• AI logic that cannot be explained or audited locally<br>• Automated response paths dependent on external services<br>• Platform updates that bypass domestic governance processes</p><p>Regulatory accountability does not transfer with outsourcing. Supervisory frameworks place responsibility squarely on the regulated entity making these dependencies operationally dangerous during audits and incident response.</p><p><strong>Why Splunk Aligns with Sovereign SOC Requirements (Architecturally)</strong></p><p>From a sovereignty perspective, Splunk’s relevance is architectural, not rhetorical. It is why it appears repeatedly across public sector, BFSI, and defence, environments operating inside closed data centers.</p><p>Key characteristics documented in its technical design include:</p><p>• Analytics executed where the data resides<br>• Support for fully on-premises and private-cloud deployments<br>• Transparent, inspectable detection logic<br>• Locally governed SOAR execution<br>• Native long-term retention and forensic replay</p><p>….exercised in practice through,</p><p><strong>Deployment Control:</strong> Fully on-premises and disconnected (air-gapped) architectures are supported, with cryptographic controls configurable using FIPS-validated modules.</p><p><strong>Data Control:</strong> Petabyte-scale ingestion across IT, security, and OT environments, with immutability and retention architectures aligned to Indian regulatory mandates.</p><p><strong>Operations Control:</strong> Risk-based alerting, on-prem UEBA, and locally governed SOAR keep analytics, decisions, and response authority inside national and organizational control boundaries.</p><p>….and from an Indian perspective, MeitY compliant and aligned to CERT-In directions on log retention, incident reporting, forensics integrity, strong chain of custody, accountability requirements with continuous audit-ability.</p><p><strong>Strategic Reality Check</strong></p><p>Sovereign SOCs are not <strong>anti-cloud</strong>, they are <strong>anti–uncontrolled dependency</strong>.</p><p>They are not about isolation, they are about deliberately <strong>deciding what may federate</strong> — and <strong>what must remain domestically controlled</strong>.</p><p>For nations operating at India’s digital scale, complete SOC sovereignty is no longer optional. It is the only model that survives legal scrutiny, operational stress, and political accountability at the same time.</p><h3>References</h3><ul><li><a href="https://edpb.europa.eu/our-work-tools/our-documents/recommendations/recommendations-012020-measures-supplement-transfer-tools_en"><strong>EDPB — Recommendations 01/2020 (Final, June 2021)</strong></a></li><li><a href="https://edpb.europa.eu/our-work-tools/our-documents/faq/faq-schrems-ii_en"><strong>EDPB — Schrems II FAQs</strong></a></li><li><a href="https://www.law.cornell.edu/uscode/text/18/2713"><strong>U.S. CLOUD Act — 18 U.S.C. §2713 (Official Statute)</strong></a></li><li><a href="https://www.gartner.com/en/documents/4025177"><strong>Gartner — Top Strategic Technology Trends for Government 2023</strong></a></li><li><a href="https://www.weforum.org/publications/global-cybersecurity-outlook-2024/"><strong>World Economic Forum — Global Cybersecurity Outlook 2024</strong></a></li><li><a href="https://www.nist.gov/itl/ai-risk-management-framework"><strong>NIST — AI Risk Management Framework 1.0 (January 2023)</strong></a></li><li><a href="https://www.bis.org/bcbs/publ/d431.pdf"><strong>Basel Committee on Banking Supervision — Model Risk Management Principles</strong></a></li><li><a href="https://uidai.gov.in/aadhaar_dashboard/"><strong>UIDAI — Aadhaar Dashboard (Live Statistics)</strong></a></li><li><a href="https://www.rbi.org.in/Scripts/AnnualReportPublications.aspx?Id=1365"><strong>RBI — Annual Report 2022–23 (Digital Fraud Data)</strong></a></li><li><a href="https://www.cert-in.org.in/PDF/CERT-In_Directions_70B_28.04.2022.pdf"><strong>CERT-In — Directions dated 28 April 2022 (Log Retention &amp; Reporting)</strong></a></li><li><a href="https://ncrb.gov.in/sites/default/files/CII-2022/CII_2022_Volume%201.pdf"><strong>NCRB — Crime in India 2022 (Cybercrime Statistics)</strong></a></li><li><a href="https://www.ibm.com/reports/data-breach"><strong>IBM Security — Cost of a Data Breach Report 2023</strong></a></li><li><a href="https://www.sans.org/white-papers/sans-2023-soc-survey/"><strong>SANS Institute — SOC Survey 2023</strong></a></li><li><a href="https://attackevals.mitre-engenuity.org/"><strong>MITRE — ATT&amp;CK Evaluations (Defensive Visibility)</strong></a></li><li><a href="https://docs.splunk.com/Documentation/Splunk/latest/Deploy/Deploymentplanning"><strong>Splunk Enterprise Deployment Planning Manual</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48f87e8f129c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The future SIEM]]></title>
            <link>https://medium.com/@ashok.sharma/the-future-siem-4f655149ed62?source=rss-3fa24f172244------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f655149ed62</guid>
            <dc:creator><![CDATA[Ashok Sharma]]></dc:creator>
            <pubDate>Tue, 15 Apr 2025 09:59:16 GMT</pubDate>
            <atom:updated>2025-04-15T10:07:21.241Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*MaAefKCBkKYjoo8FURRuOA.jpeg" /></figure><p>Security Operations are nerve center for safe working of business operations systems by guarding all assets and responding to threats detected. Organizations loose revenue and most important of all — repute in light of data breaches. As per the IBM Ponemon Institute cost of data breach report 2023, the data is exfiltrated in first hour of a successful compromise and costs about USD 4.45 Mn (global average) to the affected organization. Sometimes incidents as such can kill businesses, so overlaps are acceptable but gaps are big NO.</p><p>SIEM forms the center of security operations, automated detections, investigations and response capabilities reducing needed time to detect and remediate threats. This helps to robust security posture with reduction in MTTD and MTTR.</p><p>The evolution of detection and response began with — EDR , a term coined by Anton Chuvakin in 2013, which focused on behavioral anomalies and attack signatures at the endpoint level. This extended to consolidation of events across network, cloud, application for categorical approach to security through XDRs, a term coined by Nir Zuk of Palo Alto Networks in 2018. The journey to such convergence also started off at another end with development of SIEM solutions. XDRs and SIEM find a high overlap with conventional definitions for differentiation, which in reality may not hold water. Also, the non-populist sense on XDRs is as an evolved EDRs. The reality is a nuanced convergence — many modern XDRs are, in effect, SIEMs with tightly integrated response capabilities.</p><p>The Gartner 2024 MQ for SIEM, identifies, leaders in the space such as, Splunk Enterprise Security, Microsoft Sentinel, IBM QRadar, among others with strong contenders coming from Fortinet FortiSIEM and InsightIDR from Rapid7 as challengers and Elastic SIEM and Google’s Chronicle as visionaries that would up the game in TDIR space.</p><p>As the threat landscape changes constantly, the security products need to evolve too. SIEM have been on the evolution trajectory and the salient that will create an edge be :</p><p>Ingestion Architecture : Open architecture that promotes raw data from assets located on-prem or cloud with disparate formats, a schema-on-read operation, although rapidly indexed for instant visibility. 100k EPS rate ingestion capability.</p><p>AI Leverage : AI ML based models will be strong differentiators for tomorrow.</p><p>i. The convergence of obtained event data to be stitched together for understandable insight. Complex multi-stage attacks are discerned to be at post investigations that can stage at IAM systems, infrastructure, EDR data, application or network activity.</p><p>ii. Behavioral baselining and anomaly detection for slow and low APTs for attacks such as C2 framework that get undetected at times today.</p><p>Risk-Analysis : Obtained data must be weighted for priority based on MITRE ATT@CK tactics, asset criticality, and/or business impact. Risk assessment scoring can help sift through valid events must be put to priority based on practical and attack tactics.</p><p>Deployment Model: CISO’s are no fan of critical infrastructure related data stored at multiple places. Hence a cloud based SIEM deployment model is not always accepted. Parity in features for both on-prem and SaaS based deployments is a must.</p><p>Platform-Strategy : This is a 2 fold need — data and feature-extensibility</p><p>i. SIEM success is highly based on the degree of enriched data. Strong analytical platform with ways to accelerate data search&amp;retrieval, is the strategic leverage.</p><p>ii. Customization : Extending and being able to design use-case based feature extensions open doors to innovation. Such ecosystems have been proven to be the best strategy in security and beyond.</p><p>Convergence : SIEMs are usually paired with security response automation tools (SOAR) to reduce TAT for known security challenges. The future holds good for converged, simple and flexible solutions, that enable intimation or action within.</p><p>Evolution Guaranteed : The OEM promise backed solution that have proven track record to accelerate to future needs will find most fans. The ever changing and polymorphic nature of threats, require the policing of different nature.</p><p>Threat hunting is interesting and separates noted events from genuine threats, to misconfigured solutions, or human errors or unidentified business process or anomalous acceptable operation, etc. SIEM is your command center to guard against threats such as polymorphic malware, supply chain threats, insider attacks, LLM abuse, cloud-native attack surface, etc. Though it is lead by humans and powered by AI today, the future will see a strong AI play, increasing native capabilities to take actions for 0 day exploits based attacks, and creating large space for business desired innovation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f655149ed62" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[API Security Primer: Cisco SecureApp for API Protection]]></title>
            <link>https://medium.com/@ashok.sharma/api-security-primer-cisco-secureapp-for-api-protection-53a6e3c5d3fa?source=rss-3fa24f172244------2</link>
            <guid isPermaLink="false">https://medium.com/p/53a6e3c5d3fa</guid>
            <dc:creator><![CDATA[Ashok Sharma]]></dc:creator>
            <pubDate>Mon, 01 Apr 2024 10:55:18 GMT</pubDate>
            <atom:updated>2024-04-01T10:55:18.818Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ayRm69GDEe01vTW-ESZdKA.jpeg" /><figcaption>source:<a href="https://www.freepik.com/">https://www.freepik.com</a></figcaption></figure><p>In today’s interconnected digital world, Application Programming Interfaces (APIs) are indispensable tool that enable software systems to communicate, share data, and extend functionalities seamlessly across different platforms. Any business vertical, such as finance, healthcare, e-commerce or in fact social media, the importance of APIs to enhance the overall user experience is phenomenal. We have examples of Google Maps APIs for location services, payment services APIs from Stripe , and Twitter APIs for extensive social media integration, and many more have become integral to delivering sophisticated digital services and many more, that use protocols such as HTTP/HTTPS, gRPC, SOAP, websockets, or REST styled that use JSON or XML, are now important part of application delivery.</p><blockquote>As per <a href="https://www.marketsandmarkets.com/">Marketsandmarket</a>, the global API management market is projected to soar to $6.2 billion by 2024. This highlights the significant economic implications and the pivotal role APIs play in both consumption and publication.</blockquote><h3>Challenges</h3><p>The widespread adoption of APIs has lead to many challenges in security, leading to many high profile breaches. This emphasizes the potential risks and financial repercussions of insufficient API security measures with APIs. Here are some key security challenges and examples to note</p><ol><li><strong>Authentication and Authorization Failures</strong>: In 2018 Facebook, attackers exploited API vulnerabilities to access the personal data of 50 million users by exploiting the perfectly legitimate function in FB systems. This underscores the dire consequences of inadequate authorization controls. This breach not only compromised user privacy but also attracted a £500,000 fine from UK regulators due to the severe oversight.</li><li><strong>Encryption Shortcomings</strong>: The infamous Equifax data breach in 2017, affecting over 147 million consumers, exemplifies the catastrophic fallout of failing to properly encrypt sensitive data. Hackers gained access through a vulnerable application interface, culminating in a settlement exceeding $575 million.</li><li><strong>API Security Lapses</strong>: In 2019, First American Financial Corp.’s insecure API exposed 885 million sensitive records, demonstrating the grave implications of unsecured APIs. This breach, currently under investigation, may lead to significant fines and settlements.</li><li><strong>Rate Limiting Oversights</strong>: The lack of rate limiting on GitHub’s platform facilitated one of the largest Denial-of-Service (DoS) attacks in history in 2018, with traffic peaking at 1.35 Tbps. Although GitHub managed to mitigate extensive damage quickly, the incident highlights the necessity for stringent rate limiting measures.</li><li><strong>Injection Vulnerabilities</strong>: The British Airways data breach in 2018, caused by a code injection through an insecure API, compromised 380,000 transactions. This security lapse led to a hefty £183 million fine imposed by the ICO, emphasizing the high costs associated with injection flaws.</li><li><strong>Configuration Mistakes</strong>: The 2019 Capital One incident, where a misconfigured web application firewall permitted unauthorized API access, exposed the data of over 100 million customers. This breach resulted in an $80 million fine by US regulators, illustrating the dangers of configuration errors.</li><li><strong>Inadequate Logging and Monitoring</strong>: Uber’s 2016 breach, which remained undisclosed until hackers accessed the personal data of 57 million users, showcases the perils of insufficient logging and monitoring. The company’s failure to promptly disclose the breach led to a $148 million settlement.</li></ol><p>The cybersecurity industry has ways to counter and pre-empt similar incidents. Most common approaches are using API-Gateways, using security protocols such as OAuth and OpenID Connect, encryption using TLS for data in motion (and AES -256 kbit for data at rest) , using NGFW or WAFs such as Imperva, Threat Intelligence tools like Cisco TALOS , API Management solutions such as Microsoft Azure API Management for secure API lifecycle, etc. However these strategies fall short of being business aware. This denies the prospects to understand the negative impact of API attacks on a quantified level. The only hence strategy would be to use a corelated insighful information that create business service context to understanding API security.</p><p>This is where Cisco’s RASP solutions <strong>Cisco Secure Application</strong> delivers an edge that is unparallled and “need-of-today”.</p><h3>Cisco Secure Application : Putting application runtime-security on steroids</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K8OTVDKeZOs657sYThntpQ.png" /><figcaption>Cisco SecureApp : Lays bare security posture, vulnerabilities &amp; attacks info with suggested remediation (MOVE NEXT). Quantifies business risk (BRO) based on Kenna scoring.</figcaption></figure><p><strong>Cisco Secure App</strong> offers a distinctive advantage. By integrating deeply within an organization’s infrastructure, Cisco SecureApp ensures sophisticated threat detection, flaws that affect the API security in relevance to the application and automated responses to security incidents, all while understanding the specific application landscape.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PSLFLUXRYnBus8XBihEL9A.png" /></figure><p>This approach facilitates the implementation of precise, context-aware security policies, guaranteeing API accessibility exclusively to authorized users and systems. Business Risk Scoring helps understand the possible impact on the business functions, scored using the more practical Kenna vulnerability scoring system. The feature also helps extend the fold of observability into Security Operations, and as we see these are not disjointed but overlapped.</p><p>SecOps is as structurally associated with AppOps as are infrastructure considerations. In fact silos of application and infrastructure which are long gone, were contested to be separate similarly. As we turn another month, the security approach needs consolidate real-time view with automated ways to incident remediation. Cisco takes the strategy with strong commitment and the line of acquisitions defines Cisco sense of urgency. Cisco SecureApp is not a deferred to later but a confident must for every Application Runtime Teams.</p><p><em>About Me</em> : I am a senior sales engineer with Cisco AppDynamics and champion security with passion. I am certified with CISSP, IBM Cybersecurity Analyst.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53a6e3c5d3fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is DORA ?]]></title>
            <link>https://medium.com/@ashok.sharma/what-is-dora-1f65045e0e07?source=rss-3fa24f172244------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f65045e0e07</guid>
            <dc:creator><![CDATA[Ashok Sharma]]></dc:creator>
            <pubDate>Mon, 11 Mar 2024 06:06:37 GMT</pubDate>
            <atom:updated>2024-03-11T06:20:13.994Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hlTM3_UQOgShFCww1qpPSQ.png" /></figure><h3><strong>What is DORA ?</strong></h3><p>In the wake of escalating cyber threats targeting the financial sector, the European Union has introduced the Digital Operational Resilience Act (DORA) to fortify the cybersecurity framework across its member states. “<em>DORA explicitly refers to ICT risk and sets rules on ICT risk-management, incident reporting, operational resilience testing and ICT third-party risk monitoring. This Regulation acknowledges that ICT incidents and a lack of operational resilience have the possibility to jeopardise the soundness of the entire financial system, even if there is “adequate” capital for the traditional risk categories.” </em>(source: <a href="https://www.digital-operational-resilience-act.com/)"><em>https://www.digital-operational-resilience-act.com/)</em></a></p><p>This regulation is a direct response to the increasing digitalization of financial services and the subsequent rise in cyber-attacks, which have exposed vulnerabilities in the operational resilience of financial organizations. The Information and Communication Technology (ICT) risks that financial entities within the European Union must manage can be categorized into several key areas, reflecting the diverse nature of digital threats and challenges faced by the financial sector. Some of the primary ICT risks covered by DORA:</p><ol><li><strong>Cybersecurity Risks</strong>: This includes threats from malicious cyber activities such as hacking, malware, ransomware, phishing, and insider threats. Cybersecurity risks pose significant threats to the confidentiality, integrity, and availability of ICT systems and data.</li><li><strong>Data Integrity and Availability Risks</strong>: Risks related to the loss, corruption, or unauthorized modification of data, as well as risks associated with system downtimes and service unavailability. Ensuring data integrity and availability is crucial for the smooth operation of financial services.</li><li><strong>ICT Third-Party Risks</strong>: These risks arise from the dependency on third-party service providers, including cloud services, for critical ICT functions. It encompasses the management of supply chain risks, ensuring third-party service providers meet the required security standards, and managing the complexities of multi-vendor environments.</li><li><strong>Physical Damage</strong>: Risks associated with physical damage to ICT resources, such as data centers, due to natural disasters, accidents, or deliberate acts of destruction. Physical risks can significantly impact the availability and continuity of ICT services.</li><li><strong>System Failures</strong>: Involves risks related to software bugs, hardware failures, and inadequate system maintenance, which can lead to system outages or degraded performance affecting operational resilience.</li><li><strong>Human Error</strong>: Risks stemming from unintentional actions by employees or contractors, such as mistakes in handling data, misconfigurations of ICT systems, or failure to follow security protocols, which can lead to security incidents or data breaches.</li><li><strong>Outsourcing Risks</strong>: Specific concerns related to the outsourcing of ICT functions, including the need to ensure outsourced services are secure, resilient, and do not introduce additional vulnerabilities.</li></ol><h3><strong>Who should implement it and by when ?</strong></h3><p>DORA is designed to ensure that all entities operating within the EU’s financial sector, including banks, insurance companies, investment firms, crypto-asset service providers, and significant ICT third-party service providers like cloud computing services, are equipped with robust digital operational resilience frameworks.</p><p>· <strong>Adopted as a law/regulation</strong>: DORA was formally adopted by the European Council and the European Parliament in November 2022.</p><p>· <strong>Entered into force:</strong> On January 16, 2023.</p><p>· <strong>Effective date for compliance:</strong> January 17, 2025. This means financial entities and third-party ICT service providers have <strong>approximately 11 months</strong> to achieve compliance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lt83W-KvQ6k3WvqVw7jayw.png" /><figcaption>Courtsey: <a href="https://university.appdynamics.com/">https://university.appdynamics.com/</a></figcaption></figure><h3><strong>How Cisco AppDynamics can help ?</strong></h3><p>AppDynamics Application Performance Management (APM) can play a crucial role in helping its customers achieve operational resilience as mandated by the Digital Operational Resilience Act (DORA) in several key ways:</p><ol><li><strong>Real-time Monitoring and Alerting</strong>: AppDynamics APM FSO provides real-time insights into application performance and the health of underlying infrastructures. By continuously monitoring applications and services, it can instantly detect anomalies or performance degradations, allowing for immediate response to potential cybersecurity threats or operational disruptions. This capability aligns with DORA’s requirement for robust ICT risk management.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*GbWYLk6HLvrddqaH0_XP8Q.png" /><figcaption>Deep Visibility : Auto-discovery of IT landscape in real-time</figcaption></figure><p>2. <strong>Business analytics/BiQ: </strong>Track application performance KPIs linked to key business activities, gaining deep insights with AppDynamics business</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*lRa8VZYcxEVgaPt5aqmGBg.png" /></figure><p>transactions analytics.</p><p>3. <strong>Incident Detection and Response</strong>: AppDynamics APM’s advanced AIOps can bolster operational resilience by identifying the root cause of incidents rapidly to minimize the impact of operational disruptions. It facilitates a faster response to incidents, which is essential for maintaining operational resilience and complying with DORA’s incident management and reporting requirements.</p><p>4. <strong>Dynamic Performance Benchmarking / AIOPs </strong>AppDynamics AIOPs capabilities such as Dynamic Baseline helps organizations optimize their digital services. This ensures that systems operate efficiently and remain resilient against disruptions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*_GaVBU3xa0Dn3J5BTAxj-Q.png" /><figcaption>AIOPs : Capture the trends auto baselined with AI</figcaption></figure><p>5. <strong>Third-party Service Monitoring</strong>: With the integration of services from third-party providers being commonplace, AppDynamics APM’s ability to monitor these external services helps in managing and mitigating risks associated with third-party dependencies. This is in line with DORA’s focus on managing ICT third-party risks, ensuring that organizations have visibility into and control over the resilience of their extended digital ecosystem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*1VmJXJBrSCkQyOK6lXTJKA.png" /><figcaption>Vulnerability &amp; remediations. (Disclaimer: Data for representation only, not actuals)</figcaption></figure><p>6. <strong>Vulnerability Identification &amp; Remediation:</strong> Cisco SecureApp help organizations prioritize risks based on business impact and exploitability, streamlining remediation efforts. Integrate with vulnerability management tools for seamless remediation workflows.</p><p>7. <strong>Strategic Resilience Planning</strong>: By providing insights into application and system performance, AppDynamics APM supports strategic planning for digital operational resilience. Organizations can use these insights to identify potential vulnerabilities, plan capacity upgrades, and develop strategies to enhance their overall resilience.</p><p>If organizations fail to comply with the Digital Operational Resilience Act (DORA), they could face significant penalties. While the specific penalties will depend on the nature and severity of the non-compliance, DORA outlines a framework for imposing fines that are designed to enforce compliance and ensure that financial entities take their digital operational resilience obligations seriously. These could include, but not limited to, monetary fines, operational restrictions, reputational damage, license withdrawals, etc.</p><p>AppDynamics FSO can help you not just be compliant to DORA essential ICT risk management needs but navigate the regulatory landscape with confidence while building a truly resilient business, ensuring the safety and stability of your financial operations.</p><p><strong><em>About Me</em></strong><em>: Pre-sales solution architect with Cisco AppDynamics. Love for all things Cybersecurity, AI and FSO. Learn, contribute &amp; repeat.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f65045e0e07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[As the businesses engage to provide a seamless experience to their customers, the IT has become…]]></title>
            <link>https://medium.com/@ashok.sharma/as-the-businesses-engage-to-provide-a-seamless-experience-to-their-customers-the-it-has-become-901a362af8dc?source=rss-3fa24f172244------2</link>
            <guid isPermaLink="false">https://medium.com/p/901a362af8dc</guid>
            <category><![CDATA[ciscosecureapp]]></category>
            <category><![CDATA[secureappepss]]></category>
            <category><![CDATA[appdynamicsfso]]></category>
            <category><![CDATA[ciscokenna]]></category>
            <dc:creator><![CDATA[Ashok Sharma]]></dc:creator>
            <pubDate>Tue, 23 May 2023 05:54:05 GMT</pubDate>
            <atom:updated>2023-05-23T05:54:05.289Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*fct7wS_TYaVvT8bX1h40eA.png" /></figure><p>As the businesses engage to provide a seamless experience to their customers, the IT has become complex with distributed architectures, technically polymorphic, complex cloud modelled environments that may have a mix of monoliths or microservices. This has expanded the attack surface making the IT and hence the businesses, vulnerable.</p><p>Organisations are building robust security strategy to strengthen their security, specifically in application runtime security. Effective vulnerability management is a critical aspect of maintaining the security posture of organisations in today’s evolving threat landscape.</p><p>The challenge is compounded with application operations and security operations still missing an unified approach to runtime security, in most of the organisations. This begs the need for a shared application runtime security platform.</p><p>Kenna scoring system, developed by Kenna Security Inc, uses a variety of scoring algorithms to help organisations prioritise their security efforts. The Kenna Risk Score is used to rank vulnerabilities and to identify the most critical ones that need to be addressed first. It is modelled primarily on :</p><ul><li><strong>Exploit Prediction Scoring System (EPSS):</strong> It is a free, open model that uses 16 variables to predict the likelihood of a vulnerability being exploited in the wild in its first 12 months. The EPSS was designed by a team of IT professionals and data scientists — Micheal Roytman from Kenna Security, Jay Jacobs and Ben Edwards at the Cyentia Institute, Sasha Romanosky at the Rand Corporation, Idris Adjerid at Virginia Tech.</li></ul><p>EPSS was developed in response to shortcomings in CVSS or the Common Vulnerability Scoring System, such as relevance to the deployment, narrow expert/data base, long time for vulnerability scoring post identification and enumeration, being complex and subjective in nature, etc. The EPSS takes care of being relevant to the deployment landscape, platform and technology or service, and provides remediation prioritisation in context to service under consideration.</p><ul><li><strong>The Ground Truth Telemetry Score</strong>: Ground Truth Telemetry Score is a score that is calculated based on real-world data, such as the number of times a vulnerability has been exploited in the wild.</li></ul><p>The vulnerability data is services from 19+ exploit and threat intelligence feeds , 15+ billion security events, and 12.7+ billion managed vulnerabilities. Cisco uses this data to get a complete view of the potential impact and threat criticality relevant to the IT landscape. This is then used to drive the next steps of remedial actions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*CjACs02sPVkwba-4M1bO5w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*yYbtEckcr4-vHgpgqFLb1g.png" /></figure><p><em>Figure source: </em><a href="https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/docs/vmwcb-whitepaper-understanding-the-kenna-security-vulnerability-risk-score.pdf"><em>https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/docs/vmwcb-whitepaper-understanding-the-kenna-security-vulnerability-risk-score.pdf</em></a></p><ul><li><strong>The Asset Criticality Score</strong>: Asset Criticality Score is a score that is calculated based on the importance of an asset to the organisation.</li></ul><p>Kenna scores provide a comprehensive view of business application security posture. The other benefits are:</p><ul><li><strong>Prioritisation : </strong>They can help organisations prioritize their security efforts.</li><li>They can help organisations identify the most critical vulnerabilities.</li><li><strong>Remediation: </strong>They can help organisations track the progress of their security remediation efforts.</li><li><strong>Reporting : </strong>They can help organisations communicate the severity of vulnerabilities to stakeholders.</li><li><strong>Compliance</strong>: Kenna scoring can help organisations comply with security regulations by providing information on the vulnerabilities that need to be fixed.</li></ul><p>Cisco acquired Kenna Security Inc. in June of 2021 and integrated it back into its suit of security products, leveraging the vulnerability scoring feature. The in-house developed Cisco RASP solution <strong>SecureApp</strong>, besides the CVSS scoring model, is integrated with Kenna scoring to arrive at the most relevant vulnerability scoring, prioritised, that can guide the AppOps and AppSec a focussed approach to maintaining sublime customer experience.</p><p>The Kenna scores vulnerabilities on a scale of 100. The categories being -</p><p>0–33 <strong>GREEN. </strong>LOW likelihood + LOW impact. Best deferred to other priorities.</p><p>34–66 A<strong>MBER. </strong>Low likelihood but HIGH impact. Need immediate attention.</p><p>67–100 <strong>RED. </strong>HIGH likelihood and HIGH impact. Need URGENT attention.</p><p>The Cisco SecureApp with Kenna scores provides:</p><ol><li>Full Stack Observability (FSO) — Security : Natively integrated with Cisco’s APM solution — AppDynamics, SecureApp provides deep visibility into security domain for a matured FSO.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*Zbr2T1R1c79R9RalehF-kw.png" /></figure><p>2. A relevant vulnerability scoring to prioritise the fixing for sublime AppOps and SLA fulfilment. It provides twice as efficient score with about one third false positives.</p><p>3. Highest impact remediation guidance for top 3 most affected libraries.</p><p>4. Transparent scoring that reflects — ease of exploitability, active Internet breach, exploit availability and is widely targeted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*VksO8-M9rSY9gOydCm9DzQ.png" /></figure><p>5. According to a some studies conducted, organisations that implemented the Kenna scoring system witnessed a 47% reduction in time to remediation compared to traditional vulnerability management approaches.</p><p>It is evident that the IT AppOps need to adapt to the new dimensions affecting service SLA. The current IT verticals, such as infrastructure, application services, networking , security etc. are well structured to handle core challenges but fail close amalgamation. Security emphasis is mandatory and should cut across the verticals. Cisco understands it very well.</p><p>Full Stack Observability through AppDynamics makes is possible to have a unified pane, a single source of truth for all dimensions of your application (including security). Cisco SecureApp, provides the fourth pillar — SecOps integrated into APM, to provide a holistic deep domain visibility into your application landscape. Kenna scores, add teeth to your capabilities to attack vulnerabilities and handle them through suggested priorities.</p><p>References</p><p><a href="https://www.cisco.com/c/en/us/about/corporate-strategy-office/acquisitions/kenna-security.html">https://www.cisco.com/c/en/us/about/corporate-strategy-office/acquisitions/kenna-security.html</a></p><p><a href="https://www.cisco.com/c/dam/en/us/products/collateral/security/vulnerability-management/how-kenna-works.pdf">https://www.cisco.com/c/dam/en/us/products/collateral/security/vulnerability-management/how-kenna-works.pdf</a></p><p><a href="https://www.helpnetsecurity.com/2019/11/04/kenna-security-exploit-prediction-scoring-system/">https://www.helpnetsecurity.com/2019/11/04/kenna-security-exploit-prediction-scoring-system/</a></p><p><a href="https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/docs/vmwcb-whitepaper-understanding-the-kenna-security-vulnerability-risk-score.pdf">https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/docs/vmwcb-whitepaper-understanding-the-kenna-security-vulnerability-risk-score.pdf</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=901a362af8dc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Instamojo — A Roadmap’ed Success]]></title>
            <link>https://medium.com/@ashok.sharma/instamojo-a-roadmaped-success-4ae6cdb7669e?source=rss-3fa24f172244------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ae6cdb7669e</guid>
            <category><![CDATA[payments]]></category>
            <dc:creator><![CDATA[Ashok Sharma]]></dc:creator>
            <pubDate>Tue, 12 Feb 2019 05:11:34 GMT</pubDate>
            <atom:updated>2019-02-12T05:11:34.290Z</atom:updated>
            <content:encoded><![CDATA[<h3>Instamojo — A Roadmap’ed Success</h3><p>What started off as a quest for three — Sampad, Akash and Aditya to make Internet a trustworthy place and businesses to grow online, resulted in creation of a digital payment platform targeted towards MSMEs. Instamojo was founded in 2012 and offers a link-based payments platform for individuals, micro-merchants, infopreneurs, freelancers, and SMBs to collect payment instantly.</p><p>It currently boasts of having 600,000 Indian businesses from 29 States and 7 Union Territories with 10+ million customers with over 1000 Cr (FY17) as Gross Merchandise Value or GMV. Instamojo Fy19 goals are to expand the seller base to 1 Million, with 100K new active seller and surpass GMV of about 6000 Cr. It intends to leverage the Indian digital payment industry growth story which is pegged to be about $500 Bn by 2020 contributing 15% to India&#39;s GDP.</p><h3>An Introduction</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/755/1*-1qfo0FndYJ7UejB1-KHBA.jpeg" /></figure><p>In Sampad Swain’s own words —</p><blockquote><em>Instamojo.com is a digital payments platform bundled with tons of e-commerce features to enable any business or individual to sell, manage &amp; grow online securely, effortlessly and cost-effectively.</em></blockquote><p>Instamojo.com is a digital payments platform bundled with tons of e-commerce features to enable any business or individual to sell, manage &amp; grow online securely, effortlessly and cost-effectively.</p><p>The offerings in the nascent years were all about simple payment links to help small businesses or individuals sell for digital goods like eBooks, software, music etc. The revenue was from the percentage cut for hosting these assets and enabling transactions.</p><p>Instamojo today stands as a key player in the ecosystem of micro-finance. Coming off an age from being just a payment gateway, it offers diverse value propositions for its customers</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*_SeZZtoCOStKyUKFrcpb9w.png" /></figure><p>Instamojo strategically relied on the past data to keep improving the product and add more features while bucketing their product road-map into 3 buckets: Reach, Revenue and Retention.</p><h3>Instamojo Roadmap 2014–2018</h3><p>Bringing a whole new suite of products in 2014 to gradually augmenting the value streams, Instamojo Roadmaps are shown below. The feature set were designed to enable the businesses to make the most of technological disruption while becoming easier at the same time.</p><p>2014</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*bhV6V4T6aCdGHjzM8KkqLw.png" /></figure><p>2015</p><p>2015 was about enabling businesses utilize online payment APIs alongwith invoice generation. Instamojo gave options to create online webstores.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*iAqB0M7vNy18BQi8lqw4cg.png" /></figure><p>2016</p><p>The focus was on integration of UPI and mobile wallet, to leverage the accelerated use of such. These instruments were supported by the changing rules and regulations and Instamojo was well placed with integration offering extended payment options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*1t0bv58aqkviyD2Y3BeCNQ.png" /></figure><p>2017</p><p>2017 saw a marked focus on enabling and offering more to the sellers aboard the platform. This included advanced analytics, reporting, shopping cart and integrated customer support system. This not only augmented the current ecosystem in sense of features but made easier for MSEM to do business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*X8lN_V8CAZKDZ_2rJ19vpw.png" /></figure><p>2018</p><p>Instamojo objective to widen it’s Seller base to 1 Million and grow it’s business has seen it diversify into new verticals — lending, e-commerce enabling services, compliance, logistics and promotions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*nuWCpf0072T-CCZcCdz5eQ.png" /></figure><h3>The Road Ahead</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/1*balSMT8XLyvjZqtNM9ZOag.png" /></figure><p>The goal of Instamojo for future is to grow it’s business by expanding it’s clients base by 400% and grow it’s business by 4 to 5 fold. The goals as quoted include:</p><ul><li>The launch of a single integrated dashboard across mobile and desktop to start, manage and run your business</li><li>Surpass a GMV run-rate of $ 923.7 Mn (INR 6000 Cr)</li><li>Become the first online transactions platform to surpass 1 Mn seller base</li><li>Add 100k new active sellers to become India’s largest online transactions platform.</li></ul><p>The mojo of Instamojo has been to make it easier for MSME to do business. The feature prioritizsation should be objectivised by their intent to expand but should be governed by the ecosystem — political, technology disruptions, urgency and relevancy. It also needs to focus on</p><ul><li>Improve customer service (There are complaints on-line)</li><li>Impact on revenue and accessibility to new markets</li><li>Leverage technological disruptions against competitions</li><li>Reforms in Indian business and payment industry</li></ul><p>With a fast paced markets and continuously changing landscape, the journey to achieve 2019 goals can at best, only be described as intriguing. Instamojo has been a traveller on such roads since 2014 and it still has long way to go.</p><h4>References</h4><p><a href="https://thoughtfarming.wordpress.com/2017/05/19/the-road-so-far%e2%80%8a-%e2%80%8ainstamojos-roadmap-to-success/">https://thoughtfarming.wordpress.com/2017/05/19/the-road-so-far%e2%80%8a-%e2%80%8ainstamojos-roadmap-to-success/</a></p><p><a href="https://inc42.com/buzz/instamojo-comes-out-as-a-winner-of-fy18-aims-to-cross-revenue-run-rate-of-923-7-mn-in-fy19/">https://inc42.com/buzz/instamojo-comes-out-as-a-winner-of-fy18-aims-to-cross-revenue-run-rate-of-923-7-mn-in-fy19/</a></p><p><a href="https://entrackr.com/2018/04/instamojo-growth-revenue-2019/">https://entrackr.com/2018/04/instamojo-growth-revenue-2019/</a></p><p><a href="https://www.instamojo.com/blog/category/instamojo-product-update-guide/product-updates/page/4/">https://www.instamojo.com/blog/category/instamojo-product-update-guide/product-updates/page/4/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ae6cdb7669e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developing products, the Agile way]]></title>
            <link>https://medium.com/@ashok.sharma/developing-products-the-agile-way-8c1079b386fe?source=rss-3fa24f172244------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c1079b386fe</guid>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Ashok Sharma]]></dc:creator>
            <pubDate>Wed, 16 Jan 2019 17:54:06 GMT</pubDate>
            <atom:updated>2019-01-16T17:54:06.424Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xA8psT5rdCLNI40zqI_5Gw.jpeg" /></figure><p>Agile Methadology is an approach to build software products using incremental and iterative developments in a highly flexible and interactive manner. Working on the Agile Manifesto and the core principles, it exploits to harness the ever changing user needs providing benefits because of its user centric approach. This was hitherto not possible with other existing models of software development.</p><p>The two approaches of the agile are — <strong>I</strong>ncremental development and <strong>I</strong>terative development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/434/1*pW6YdYPxYRH18xATtEfd0Q.png" /><figcaption>Incremental development model</figcaption></figure><p>Incremental development deals with articulated requirements where features or feature set are developed and delivered, each deliver being fully functional and additive to the expected product functionalities.</p><p>An iterative development approach provides a mechanism to develop where the requirements are not articulated well or known in advance, rather they are done over a period of time progressively. With every iteration, the product nears its intended shape.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z8js2vpgq7oEoR8JfgizJg.jpeg" /></figure><p>An Agile Methadology being amalgamation of both provides transparency and avenue for constant user feedback. This is achieved by breaking the overall scope of the product into Epic which are then further disintegrated into User Stories which are unit of software design, development and value delivery. These are then prioritized during the product development over multiple repetitions of SPRINTS to complete the work. This helps rapidly create the product as the user (read customer) intends.</p><p>Lets take an instance of a food delivery application like Zomato and apply the framework for development of features like rate/review restaurant, filters for search and online ordering.</p><p>Any product development would essentially consist of following phases.</p><ol><li>Conception of the Idea</li><li>Market and user research</li></ol><p>3. Product planning</p><p>4. Design</p><p>5. Development</p><p>6. Testing</p><p>7. Deployment</p><p>8. Maintenance</p><p>The last stage of “Maintenance” is essential once the product is developed and deployed and for the reasons of scope shall be excluded from our discussion here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*d_-0VSR1TX636-s0H1FGAA.png" /></figure><p>The approach would involve by splitting the <strong><em>EPICS</em></strong> in to actionable USER STORIES. These would then be need to run through multiple SPRINTS that would provide have a prioritized backlog as SPRINT backlog. In reference to the product development phases mentioned above, the SPRINT shall comprise of Product Planning till Deployment repeated for all the feature development. For the intent to be able to deliver, the SPRINT could be 3 week long SPRINT, where the scheduled task could be broken down as :</p><h4>Week 01</h4><p>Planning for the SPRINT and prioritizing features as per business value</p><p>Designing the features using Design Sprint which could itself run up to 5 day period. The break up of the week could be visualized as :</p><p><strong>Day 01</strong>: Identify and understand the high priority tasks that are ambitious but manageable and plan them in as SPRINT BACKLOG.</p><p><strong>Day 02</strong>: The tasks then shall be deliberated by the whole team for understanding. This leads to creating more focused approach and emphasizes critical thinking to arrive at possible solutions.</p><p>This would also be the day, when target audience for user reviews shall be identified.</p><p><strong>Day 03</strong>: With the deliberation, a stack of possible solutions shall be available. This day shall be utilized in deliberating over the possible solutions and chose the one accepted by the majority. The same shall be converted into a storyboard.</p><p><strong>Day 04</strong>: A high fidelity mock-ups and prototype shall be created that can be tested for user inputs and reviews. Hypothesis and questionnaire shall be prepared in accordance with the prototype developed.</p><p><strong>Day 05</strong>: An existing prototype arrived after due diligence and deliberation by the design team now shall be put to test to user review. User behavior and action shall be observed and recorded to understand the perceptibility of the available design.</p><h4>Week 02</h4><p>Developing the code for the feature set chosen for the chosen SPRINT BACKLOG. It is a tacit understanding that the code shall be developed and tested simultaneously. The EPICs (features to be developed) shall be disintegrated into a more actionable items in SPRINT backlog could be as below</p><p><strong>Rate or Review Restaurant</strong></p><p>Story 01: A user should be able to open up a restaurant description and provide feedback for a restaurant.</p><p>Story 02: A user should be able to rate a restaurant using star ratings from the listing.</p><p><strong>Development of Filters for Search</strong></p><p>Story 01: A user should be able to customize filter criteria and do a search accordingly.</p><p>Story 02: A user should be able to clear the filter criteria for another search using the clear all button.</p><p>Story 03: A user should be able to save the search criteria for future use.</p><p><strong>Online Ordering</strong></p><p>Story 01: A user should be able to place the order by choosing delivery address at the end of purchase.</p><p>Story 02: A user should be able to select the mode of payment while making payment in an online order.</p><h4>Week 03</h4><p>This week shall entail deployment and making available the workable product for the user. The motivation behind the deployment would be understand the use of the product by the users and possible improvements as there can be.</p><p>Data from multiple channels shall be collected against various metrics and using different analytical approaches. The intent here shall be to drive in better engagement with users and augment current feature set of the product.</p><p>The suggestions shall be evaluated and made part of PRODUCT BACKLOG for further development and improvement of products.</p><p>This shall conclude a SPRINT and the entire process shall iterate till the PRODUCT BACKLOG is exhausted.</p><h3>Conclusion</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*xX7AaefU5WbLMgRZfIh9pA.gif" /></figure><p>As understood the overall process shall provide transparency, high visibility, and faster delivery, which are it’s key value proposition. It shall also ensure that the product is developed as per the current need of the business and affects in changes as per changing business needs.</p><p>The product development is done with diligent customer engagement granting higher success in delivery in a rapidly changing requirements landscape.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c1079b386fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mobile Wallet Economy: Adoption, Challenges and Future]]></title>
            <link>https://medium.com/@ashok.sharma/mobile-wallet-economy-adoption-challenges-and-future-f6712ca72b50?source=rss-3fa24f172244------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6712ca72b50</guid>
            <category><![CDATA[wallet-adoption]]></category>
            <category><![CDATA[e-wallet]]></category>
            <category><![CDATA[mobile-wallet-future]]></category>
            <category><![CDATA[wallet-growth-hacks]]></category>
            <category><![CDATA[mobile-wallets]]></category>
            <dc:creator><![CDATA[Ashok Sharma]]></dc:creator>
            <pubDate>Sun, 14 Oct 2018 16:07:23 GMT</pubDate>
            <atom:updated>2018-10-14T16:07:23.135Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine a scenario where you need to purchase groceries and travel back home in a cab but you are out of cash. Assuming the store accepts credit card, you are not worried. You shop to your needs only to find during payment that the cards payment machine is not working at POS terminal, since morning. To compound the problem the nearest ATM is not really nearby and you need an earnest solution.</p><p>When you feel out of options for payment, you find out the grocery accepts payment via one of your mobile wallet. The whole situation seems suddenly, sorted. You pay via your m-wallet and are on a way back home in a cab, which supports payment via the same mobile wallet.</p><h3>Digital Payment Transaction Landscape in India</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*yQBfPBOCL5kjbq0wHz-1ag.png" /><figcaption>Source: <a href="http://cashlessindia.gov.in/">http://cashlessindia.gov.in</a></figcaption></figure><p>The payment transactions in India have always been cash heavy. With rise in smartphone ownership, higher Internet penetration, mobile technology advances in security and privacy, rising disposable income has propelled digital payments industry in India to gain grounds.</p><p>The instruments in the digital payment include but not limited to — debit/credit cards, travel cards, UPI, mobile wallets, Internet banking etc. Of all the available instruments, mobile wallet has gained quite prominence in the last 5 years since it’s’ inception in 2006.</p><h4>What is a Mobile Wallet?</h4><p>Mobile wallet is a mode of digital payment similar to credit/debit cards, online bank transactions, gift cards, etc. and are part of what is called as Pre-Paid Instruments (PPI) which lets the user make online transactions. The first mobile wallet in India was <em>Wallet365.com</em> and was launched by the Times Group in 2006.</p><h4>How does it Work?</h4><p>It is a virtual wallet which resides on your phone as an installed application. The user is required to add the available source of money — a credit/debit cards, a bank account etc. which is then used to load money in the wallet for transactions henceforth. It keeps information of source and track of all transactions virtually. The amount loaded can be used to for online payment of purchases, bill payments, transfer of money (conditional), etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O444iCYh41EMrh8YGDiuug.jpeg" /><figcaption>Source: <a href="https://www.devicebee.com/solutions/mobile-wallet/">https://www.devicebee.com/solutions/mobile-wallet/</a></figcaption></figure><p>Mobile wallets can be categorized into three categories based on who operates the wallet, purpose of the wallet and transaction limit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*eIgKXIcWIbDme2CZg-Et2w.jpeg" /></figure><p><strong>1. Closed Wallet</strong> The purchases through these wallets are exclusive only to the issuing company. The money added to these wallets are locked in the wallets and cannot be used for any product or services outside of the offerings of the issuing company. For e.g. Amazon, Flipkart, etc. No prior authorization but an intimation, is required from RBI to open a closed wallet.</p><p><strong>2. Semi-Closed Wallet</strong> The wallets can be used for the products and service offered by the issuing company, as well as at certain designated locations. For e.g. PayTM, PayU, etc. A prior authorization from RBI is needed to open a semi-closed wallet</p><p><strong>3. Open Wallet </strong>The wallets can, not just be used for products and service, but also withdraw money at the ATMs or banks. These are created in collaboration with banks. For e.g. M-PESA, PayZapp, etc.A prior authorization is needed from RBI to open wallet.</p><h4>M-Wallet Growth</h4><p>The Indian story of the mobile wallet is poised for growth. As per <a href="https://www.globaldata.com/mobile-wallet-gradually-displacing-cash-india-says-globaldata/">GlobalData ( leading data and analytics company)</a> , India is one of the top market in mobile payment adoption and surpasses US, UK, China and Denmark.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/545/1*XEK1QA9ufOnKr0Qkm7klDw.png" /><figcaption>Source: RBI, Deloitte Analysis [2]</figcaption></figure><p>The overall landscape of digital payments has seen explosive growth since FY 13. This can be attributed government and regulatory norms, demonetization in November 2016, cashback and discounts, launching of QR Codes, expansion in rural areas has been significantly pushing the economy into being <em>cashless</em> payment friendly. This coupled with low switching and wide adoption arising of the same, made it easier for small vendors and service providers to jump into the stream of new and emerging payment mode.</p><p>Since FY13, the volume of digital payments transactions has grown at about 19% annually while the value has increased at an annual rate of 12% in the same time period. Though the card payment rules the roost, PPI instruments is the fastest growing segment with about 97% CAGR since FY13 and accounts for about 10% of the overall pie. Mobile wallet is the largest category within the PPI, although it also includes paper vouchers and gift cards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*VdM1iPyo1A9bZiihxpvZ2Q.jpeg" /><figcaption><strong>Transaction value by digital payment mode (percentage share), </strong>Image source: RBI, Deloitte Analysis [2]</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/596/1*BNOnS7WQ3AqMuWZYYHbQhA.jpeg" /><figcaption><strong>Transaction value by digital payment mode (percentage share), </strong>Image source: RBI, Deloitte Analysis [2]</figcaption></figure><p>As per the data available from RBI and Industrial analysis, in the past few years, from FY 13 to FY 17, the mobile wallet segment has seen a CAGR of 120%, with more than doubled rate of growth between FY16 and FY17, primarily because of demonetization. The number of transactions increase from about 55 million transactions in November 2016 to about 130 million transactions in April 2017. A growth of about 136%. Understanding that the adoption has not reached a complete scale, this only seems to be a beginning.</p><h4>M-Wallet Adoption in India</h4><p>To understand the adoption of mobile wallet and understand the current stage today we are in, let us take a look at the ubiquitous bell curve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6b-us9HXRPQ3y-LBfLlxoQ.png" /></figure><p><strong>Innovators</strong> These are quick to adopt new technology and ready to take incumbent risks. These would be 18–30 years old, tech savvy and enthusiasts who would want to lay their hands on anything new in the market. These constitute only 2.5 % of the total potential market.</p><p><strong>Early Adopters</strong> A 13.5 % of the potential market who could be 18–35 year old, living in tier -1 cities of India and adopt based on the popularity of the technology. They could be young professionals, students, entrepreneurs, etc. and would technology friendly if not savvy.</p><p><strong>Early Majority</strong> These comprise of 34% of the total users and typically reflect people who would wait on the feedback of innovators and early adopters, indulge a thorough research before deciding on jumping on the bandwagon. They would fit a persona of 28–40 year old who could be teachers, self-employed, lecturers, etc.</p><p><strong>Late Majority</strong> Reluctant to adopt anything new unless satisfied by reviews and feedbacks from verified resources, these are 34% of the market.</p><p><strong>Laggards</strong> They represent non-tech savvy and ones who shun any new technology. These still love to use cash transaction. These represent about 16% of the market.</p><p>India is a young country with around 1.3 billion people where 60% of its population is below the age of 35 years. It currently has about -400 million smart phone users where users using mobile wallet is about 371 million (FY2016, RBI Data). The mobile wallet transactions amounting to 1630 million transactions with value of 532 billion INR[2] of the total 2295 Billion INR about 25. The current penetration only represents about 20% of the population with about 25% of overall digital payments. This puts us at about the phase of <strong>Early Adopters</strong>, moving beyond the chasm.</p><h3>Influencing Factors</h3><h4>Challenges</h4><p>The mobile wallet industry has been on a steep trajectory riding on the wave of acceptance because of certain reasons. However, it faces challenges few of which are mentioned below.</p><p><strong>1. Inertia</strong> Mobile wallets are still not considered as safe. With India still heavy on cash transactions, an emphasis should be on to answer the concerns of security, transparency of charges and privacy while using mobile wallets. This needs to be through repeated product enrichment and marketing campaigns.</p><p><strong>2. Competition</strong> Mobile wallet competes with debit or credit cards in this landscape. Average ticket size for a mobile wallet transaction in FY 17 was INR 327 versus INR 2,506 for debit/credit cards which speaks volumes on gap in acceptance.</p><p><strong>3. Compatibility</strong> Consumers of mobile wallet are looking towards a convenient form of payment and any incompatibility is bound to be a hindrance. It is required that a seamless compatibility exists across all operating systems.</p><p><strong>4. Industry Consolidation</strong> Limited funding and transactions has forced consolidation with multiple acquisitions and mergers, viz — Flipkart acquiring PhonePe, PayU acquiring Citrus payments, etc. Investors are looking at minimization of cost and this needs to be looked into</p><p><strong>5. Challenge from UPI</strong> NPCI or National Payments Corporation of India introduced UPI or United Payment Gateway Interface in 2016. It has beaten e-wallet hands down since November 2017 in terms of growth.</p><p><strong>6. Government Regulations </strong>Although temporary, the need for KYC norms as</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*ZQU9cGlZO3i8egnOLf6hrQ.jpeg" /></figure><p>set in October 2017 for mobile wallets to be compliant by Feb 2018 had adverse effect on the mobile wallet usage.</p><p><strong>7. Security risk</strong>: The security involved in the cashless payments is of paramount importance. The hacking of Equifax data serves as a good example. The reputational and financial losses could mount for a company in case of any intrusion of e-theft. This another big hurdle in mobile wallet adoption. <strong>Although interestingly this is least important driver of e-wallet usage.</strong></p><h3>Growth Hacks</h3><p>Mobile wallet is the future of digital payments. It is not just in urban areas but rural areas too have had impact of the overall national growth story. Mobile wallet payments are being preferred as they offer ease of business and transparency in transactions.</p><p>India’s leading mobile wallet issuer, <strong>PayTM</strong> doubled its user base in a year, increasing from 140 million in October 2016 to 270 million in November 2017. It expects to onboard about 500 million users by 2020</p><p><strong>1. Favorable rules and regulations</strong> The mandated KYC regulation has an adverse impact albeit limited (stated above). The government needs to put rules and regulations that do not hamper the growth of mobile wallet adoption across segments.</p><p><strong>2. Offer on mobile wallet transactions</strong> Offers and discount could be used to entice and enlarge the user base. As indicated in a distinctive study done by <a href="https://www.regalix.com/">Regalix Research</a> , 19% of the mobile wallet users interviewed on boarded for the discount offers on payments.</p><p><strong>3. Changing innate behavior</strong> Currently mobile wallets are perceived not to offer remarkable benefits over traditional methods like debit/credit card payments. The change in the innate behavior shall require more than the current structure to coax a greater user base. It could be as basic as removal or lessening of associated fee with transactions just to make them more lucrative.</p><p><strong>4. Ease of Use</strong> Mobile wallets are harder to set as compared to their immediate competitor UPI payments. Unlike a simple installation if UPI applications, mobile wallets need to be associated with money source along with KYC compliance details.</p><p><strong>5. Marketing and evangelism</strong> PayTM strategy during the liquid money crunch of November 2016 demonization resulted with almost doubling of the user base. This could be duplicated for the future growth of mobile wallet payments in future and it’s wider acceptance.</p><p>Realizing the full potential of the mobile wallet, evident challenges need to be tackled and perceptions changed. India has always been volume driven economy and the mobile wallet industry would only find success in large adoptions. The solution would range from increasing market penetration to increasing user awareness. One thing for certain is that the mobile wallet needs to touch the everyday life’s if it intends to gain prominence from the traditional payments mode of cash, which is deeply entrenched. The platform however has a bright future as evident from multiple studies and RBI Data. It is only exciting to observe the disruptor for payment transaction and promises it holds in near future for a more transparent, honest and cashless India.</p><h3>Sources</h3><p>[1] <a href="https://en.wikipedia.org/wiki/Prepaid_Payment_Instruments_in_India">https://en.wikipedia.org/wiki/Prepaid_Payment_Instruments_in_India</a></p><p>[2]h<a href="https://www2.deloitte.com/content/dam/Deloitte/in/Documents/strategy/in-strategy-leading-the-cashless-charge-noexp.pdf">ttps://www2.deloitte.com/content/dam/Deloitte/in/Documents/strategy/in-strategy-leading-the-cashless-charge-noexp.pdf</a></p><p>[3] <a href="https://www.financialexpress.com/money/7-key-challenges-indias-mobile-wallet-industry-needs-to-overcome/832911/">https://www.financialexpress.com/money/7-key-challenges-indias-mobile-wallet-industry-needs-to-overcome/832911/</a></p><p>[4] <a href="https://www.emarketer.com/content/five-trends-that-shaped-india-s-financial-sector-in-2017">https://www.emarketer.com/content/five-trends-that-shaped-india-s-financial-sector-in-2017</a></p><p>[5] <a href="https://economictimes.indiatimes.com/tech/internet/paying-on-mobile-phone-is-not-as-safe-as-you-may-think/articleshow/61288314.cms">https://economictimes.indiatimes.com/tech/internet/paying-on-mobile-phone-is-not-as-safe-as-you-may-think/articleshow/61288314.cms</a></p><p>[6] <a href="https://www.researchandmarkets.com/reports/3989824/india-mobile-wallet-market-analysis-forecast-and">https://www.researchandmarkets.com/reports/3989824/india-mobile-wallet-market-analysis-forecast-and</a></p><p>[7] <a href="https://yourstory.com/2015/06/mobile-wallets/">https://yourstory.com/2015/06/mobile-wallets/</a></p><p>[8] 4 reasons why UPI may overtake mobile wallets soon: <a href="https://www.livemint.com/Money/A1bTvyBsfMmZeNu6oSfozJ/4-reasons-why-UPI-may-overtake-mobile-wallets-soon.html">https://www.livemint.com/Money/A1bTvyBsfMmZeNu6oSfozJ/4-reasons-why-UPI-may-overtake-mobile-wallets-soon.html</a></p><p>[9]The state of e-wallets and digital payments in India 2018 <a href="https://www.regalix.com/wp-content/uploads/2018/03/The-state-of-e-wallets-and-digital-payments-in-India-2018.pdf">https://www.regalix.com/wp-content/uploads/2018/03/The-state-of-e-wallets-and-digital-payments-in-India-2018.pdf</a></p><p>[10] <a href="https://www.business-standard.com/article/companies/mobile-wallet-transactions-rise-16-in-may-rbi-s-monthly-bulletin-118071100061_1.html">https://www.business-standard.com/article/companies/mobile-wallet-transactions-rise-16-in-may-rbi-s-monthly-bulletin-118071100061_1.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6712ca72b50" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>