<?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 Jeevan sunkari on Medium]]></title>
        <description><![CDATA[Stories by Jeevan sunkari on Medium]]></description>
        <link>https://medium.com/@jeevan.consult?source=rss-a30c085c2e71------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*dYD8rGyLwdhnAfSRXI9EQw.png</url>
            <title>Stories by Jeevan sunkari on Medium</title>
            <link>https://medium.com/@jeevan.consult?source=rss-a30c085c2e71------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:59:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jeevan.consult/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[Deploying RPA Securely?]]></title>
            <link>https://medium.com/@jeevan.consult/deploying-rpa-securely-8727611e255c?source=rss-a30c085c2e71------2</link>
            <guid isPermaLink="false">https://medium.com/p/8727611e255c</guid>
            <category><![CDATA[rpa-training]]></category>
            <category><![CDATA[secure-development]]></category>
            <category><![CDATA[role-based-access-control]]></category>
            <category><![CDATA[roboticprocessautomation]]></category>
            <category><![CDATA[rpa-security]]></category>
            <dc:creator><![CDATA[Jeevan sunkari]]></dc:creator>
            <pubDate>Tue, 13 Aug 2019 08:38:46 GMT</pubDate>
            <atom:updated>2019-08-13T10:13:46.027Z</atom:updated>
            <content:encoded><![CDATA[<p>“Average cost of a data breach in 2017 was $3.62 million — or $141 for each compromised record”- <em>by the Ponemon Institute</em></p><p>By: <a href="https://medium.com/u/a30c085c2e71">Jeevan sunkari</a> &amp; <a href="https://medium.com/u/294cfd70081c">R V SIVANANDA REDDY</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*1rLpAzeDzD86PE5Dn4eixw.jpeg" /></figure><h3>Gained Momentum — “In Boom”</h3><p>Enterprise digital farms are enabling bots to perform repetitive swivel chair like tasks by simply logging into various software applications just like humans. This Robotic process automation started with a vision to transform the business process by delivering fast and accurate services to improve customer experiences, quick turnaround times, super-fast resolution, etc. Although automation is not a new phenomenon its slow momentum is gaining pace as enterprises are bringing changes to their operating model through standardisation and Integration. Big domains like banking, insurance, manufacturing, supply- chain are addressing their technological backlog and redefining their technical landscape, especially around enterprise Integrations with the legacy systems which became the key driver for RPA deployments. Organisations like to embrace virtual digital force to perform a range of basic workflow like activities to cognitive processing, natural language processing, etc using Artificial Intelligence capabilities. ROI in the early stages of an RPA deployment lured many business owners however enterprise-wide scaling resulting in challenges and worst outcomes when IT is not from the onset. This article covers such challenges especially around security and risk, the DNA of any RPA Deployment.</p><p>As 50% of the global IT service centers are actively pursuing automation pilots in an estimated size of $4.9B, the prediction from Everest group. It is eminent that enterprises need to rethink their thinking when deploying Robotic Process Automation in scale. Below are some of the Industry grade security essentials that are considerate when deploying RPA.</p><h3>How did we address?</h3><p>Below diagram is the security framework that is a part of RPA’s Centre of Excellence from one our RPA Deployment. This is a conceptual model that is being addressed in one Use Case and may or may not be suitable for every RPA deployment type and size. The aim is to share our thoughts on the criticality and necessity of having a security/risk framework when choosing RPA at scale. Below are the 5 key essentials we observed during our implementation.</p><ul><li>Multi-layer authentication &amp; IAM</li><li>RBAC</li><li>Secure Software Development life cycle</li><li>Data: In transit, at rest and Runtime</li><li>Threat Hunting &amp; Active Monitoring</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*xQ5pvYFfM6Y1eP6D1bQuMw.png" /></figure><h3>Multi-layer authentication and Identity access management</h3><p>Your typical enterprise user authentication may require a rewiring when giving access without prior authorisation to attended and unattended bots. Make sure your RPA vendor solution authentication include AD (Active Directory) either using LDAP or AD using Kerberos or some form of IAM (Identity Access Management) options. Read the support documentation around SAML 2.0 SSO (Single Sign-on) and evaluate the ability to integrate with your own privileged access/creds management.</p><p>Thus, authentication will be the first step in mandating control enforcement by the enterprise security team. <a href="https://www.theguardian.com/business/2017/sep/25/deloitte-hit-by-cyber-attack-revealing-clients-secret-emails">Deloitte, one of the world’s largest accountancy firms with over $38 billion in revenue, has been ranked #1 in cybersecurity consulting by Gartner for 5 years in a row. In 2017 they experienced a major data breach due to poor Identity Access Management. According to sources, Deloitte did not use two-step verification. Once inside, they accessed confidential client emails and documents, including sensitive information of world governments.</a> Keep in mind — “Your Expensive Cybersecurity is Only as Strong as Your Identity Access Management”*. The business should allow the infosec team early in the process to work alongside with Enterprise Architecture to evaluate the multilayer authentication capabilities that RPA vendor is offering.</p><h3>Need for Role-based Access controls (RBAC)</h3><p>We aimed for a fine-grained enhanced role-based access control models to manage access during our RPA deployment. Our mantra is always Least privileges and separation of duties so we identified and evaluated number of roles for DEV (bot creators) Test (Bot Testers) and Build Release Team (Bot promoters, Bot admin) and users (bot operators for attended) when granting accessibility (devise pools, audit logs, schedulers etc), visibility (bot farms, users, dashboards, health checks etc), manageability (licenses, audit log actions, admin user accounts, lockers etc). We applied this principle by separating roles in both data and system functions. When we think of data privileges, we are typically thinking of the ability to view (read) and change (write) as well as deleting and creating files and when we think of system privileges we are generally talking about activities such as logging into computers and networks, hardware and software installation.</p><p>We should be cognizant of the number of threat vectors that are prevalent in this area. For instance, giving an employee with privileges to install software on their company-issued workstation (Attended bot) could easily introduce malware to the network. If there is no legitimate business need for the employee to have such privileges, such risk cannot be justified. Finally, think of Entitlements, transitive trust, non — transitive trust etc and be stringent when the separation of duties requirements to protect the privacy and prevent frauds. If you have complied with SOX, HIPAA, PCI, FISMA &amp; GLBA then your digital farm (bots) should also be.</p><h3>Secure Software Development life cycles</h3><p>Your Software build, test, promote and deploy in a secure environment should be treated no different when thinking of RPA. Multi Environment setup to perform all functions of a software development life cycle with an appropriate naming convention, access controls, security settings etc. For instance, one major RPA vendor use network-based firewalls and local server-based firewalls are used to protect all nodes in a cluster when utilizing a clustered deployment. Network-based firewalls are used to isolate development test and production RPA environments from the corporate network from each other thus enforcing secure development life cycle each zone is logically isolated with different user groups with distinct roles and access controls. Discussions around environments should start as early starting your POC and aligning this with your build release teams is key and to be highlighted in your COE forums &amp; meetings</p><p>RPA infrastructure setup will have three environments where a Dev DB is connected to a Vendor application server and Developers workstation will be connected to that application server. Having at least one Runtime resource and one Interactive control also connected to the application server and this will be replicated against DEV, TEST and PROD environments. If your IT infrastructure and development practises have currently complied with FISMA, Fed Ramp, and PCI DSS then your new RPA initiative follows the same guideline and RPA technology partner should comply with these practices.</p><h3>Data: In transit and at rest &amp; Run time</h3><p>RPA inherently handles and processes confidential business data so end-to-end data protection is key to maintain confidentiality, the integrity of business processes, credentials etc. A credential vault is used by one vendor to provide a set of safeguards to protect the data at rest, transit and while it is in use on an individual system. This credential vault encrypts local credentials and selects runtime data used by bots and provides secure Storage for sensitive configuration parameters and details of the integral version control and email services. Creds authenticating before submission over a TLS/DTLS connection will protect against heart bleed and prevents creds exposed where the outer layer of the TLS connection is terminated at the front-end load balancer. Thus, network services on the client-server can use TLS1.2 and above to assure the data integrity and security during transport between components.</p><p>Distributed credential protection will allow the bots not to store the creds locally on bots. They can be dynamically retrieved from the credential vault for use within automation, retained solely in encrypted format in volatile memory and gets wiped once the associated bot is finishing executing. Check for other configuration options and features that can be used to prevent unauthorised access to confidential information or tampering with bots during run time.</p><h3>Threat hunting by active monitoring:</h3><p>Firewall security: As the environments are isolated it is crucial to place network-based firewalls and server-based firewalls to protect nodes when utilising a clustered deployment to work against adversaries. For attended bots you can permit certain protocols on the nodes from the corporate network and for unattended bots where bot runner client is installed on the corporate workstation is protected by the corporate desktop infrastructure like the PC in your office.</p><p>Intrusion Detection and Prevention Systems (IDPS): Apart from having Anti-Malware/Anti- Virus to protect the client environments, enterprise should extends the usage of IDPS systems for their RPA deployments to monitor unusual traffic flows, such as DDoS attacks, certain forms of malware (e.g. worms, backdoor) and policy violations (e.g., a client system providing unauthorized network services to other systems).</p><p>Commonly you deploy your enterprise IDPS systems at a boundary between networks, such as in the proximity to border firewalls, routers or remote access servers and wireless networks. So, monitoring network traffic, RPA application protocol activity, HIDS (Host-based intrusion and detection) the key to identifying the suspicious behaviours. This IDPS will search for unusual or nefarious activities by examining logs created by the operating system, looking for changes made to the key system files, tracking installed software, and sometimes examining the network connections a host makes. Logs can forward to a SIEM — Security Information and Event management system to monitor bots, identify current high-risk bots, number of offenses generated, critical violations, authentication failures, infected bots, unique IP’s (Source — destination) etc.</p><p>If your organisation has a compliance mandate, such as for PCI DSS, HIPPAA or ISO 27001, then you may require HIDS to demonstrate the file integrity monitoring as well as active threat hunting.</p><h3>Conclusion</h3><p>More security questions and concerns one can investigate and propose solutions while deploying RPA at large. As far as RPA deployments are concerned, we thought the above mentioned are key essentials that business leaders should aware of, Information security teams to work on, Enterprise Architecture teams should embrace.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8727611e255c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Robotic Process Automation (RPA): Applications of RPA and evaluating the need for…]]></title>
            <link>https://medium.com/@jeevan.consult/understanding-robotic-process-automation-rpa-applications-of-rpa-and-evaluating-the-need-for-1ea918c638d9?source=rss-a30c085c2e71------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ea918c638d9</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[cognitive]]></category>
            <category><![CDATA[roboticprocessautomation]]></category>
            <category><![CDATA[robotic-process]]></category>
            <dc:creator><![CDATA[Jeevan sunkari]]></dc:creator>
            <pubDate>Tue, 13 Aug 2019 08:37:26 GMT</pubDate>
            <atom:updated>2019-08-13T08:37:26.812Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Understanding Robotic Process Automation (RPA): Applications of RPA and evaluating the need for transformation towards Cognitive RPA using a case study</strong></h3><p>By: <a href="https://medium.com/u/294cfd70081c">R V SIVANANDA REDDY</a> &amp; <a href="https://medium.com/u/a30c085c2e71">Jeevan sunkari</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*FZddgUKXleVMyKwtgjTI-w.jpeg" /></figure><p><strong>What is RPA and what it does?</strong></p><p>Robotics are beginning to have a profound effect on business. Robotic Process Automation (RPA) takes the robot out of the human. Robots here are software-based rather than electro-mechanical machines and are a technological imitation of a human worker to automate structured tasks in a fast and cost-effective manner. It automates rule-based repetitive processes that involve routine human intervention, for example, executing a routine sequence of steps on a web browser, reading the contents of PDF file into a spreadsheet and loading the data from a spreadsheet into Enterprise Resource Planning (ERP) and Cloud systems.</p><p>To analyze and reveal the benefits of RPA, a case study was carried out on a business process of a Cost Centre (Business process outsourcing) that involves front and back-office activities and during the process, some inferences are made.</p><p>Before the case study, let us briefly identify the reasons behind the hype, its applications, and its successors.</p><p><strong>Who can use it?</strong></p><p>Use Cases of RPA can be applied in the fields of insurance, health care, finance, retail, banking etc. Mostly used in swivel chair operations like activities/processes, for example, Keeping employee records up-to-date, paying health care insurance claims, validating the sale of insurance premiums etc. Below cited comparison/s ignited decision-makers to develop, deploy, scale this technology in their orgs. Some enterprises are progressing vertically to add cognitive abilities to their current bots to deliver exceptional services to their customer base. An effort is to showcase and highlight that ability that takes your digital farm to the whole new level.</p><p><strong>Comparison of RPA with other process management techniques</strong></p><p><strong>RPA vs Business Process Management Systems (BPMS)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*B72rFQzQrGf2vOwErgoKEA.png" /><figcaption>Fig1. Table showing the difference between Robotic Process Automation and Business Process Management</figcaption></figure><p><strong>RPA vs Cognitive Automation</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*oXwF1tpbtuRUuibXqJEDIA.png" /><figcaption>Fig 2. Table showing the difference between RPA and Cognitive Automation</figcaption></figure><p><strong>Requirements for the use of RPA:</strong></p><p>Organizations seeking to address key challenges like cost reduction, operational excellence, and regulatory compliance might look to RPA as a flexible, low-investment, less-complex alternative to traditional solutions like offshoring, outsourcing, process improvement and system transformation. RPA software license can cost between 1/3rd to 1/5th of the price of a Full-Time Employee (FTE). Despite cost savings with RPA, not every business process can be automated. Below are some criteria of business process for RPA.</p><p>· <strong><em>Low cognitive requirements</em></strong>: Task that does not requires subjective judgment, creativity or interpretation skills.</p><p>· <strong><em>High volume</em></strong>: Tasks that are performed frequently.</p><p>· <strong><em>Access to multiple systems</em></strong>: Process that requires access to multiples applications and systems to perform the job.</p><p>· <strong><em>Limited exception handling</em></strong>: Tasks that are highly standardized with limited or no exceptions to handle.</p><p>· <strong><em>Human error</em></strong>: Tasks that are prone to human error.</p><p><strong>Cognitive RPA</strong></p><p>While RPA automates rule-based repetitive work, Cognitive RPA i.e., RPA together with Machine Learning, Artificial Intelligence, Natural Language Processing, Handwritten text recognition, Image processing would enable enterprises to automate judgmental and perceptual based tasks where there is a touch of human intelligence needed.</p><p>The integration of RPA with cognitive technologies could extend the application of automation to new areas and can help enterprises to automate larger percentage of a business process which in turn pave the way for them to maximize the digitalization of business processes. Large RPA providers are partnering with vendors for providing cognitive technologies in their tools. For example, Blue Prism has collaborated with Google to provide Optical Character Recognition (OCR) capabilities through Tesseract API and Blue Prism has also partnered with IBM Watson to bring cognitive capabilities to clients.</p><p>Cognitive RPA helps to automate routine business processes in finance, insurance, travel, healthcare domains such as investment appraisal, preparation of financial statements, etc., Let us examine one use case in the healthcare domain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*zQk2a-GpYVtJYb5SojyN1Q.png" /><figcaption>Fig 3. Business cases spectrum for RPA and CPA</figcaption></figure><p><strong>Use case of Cognitive Process Automation</strong></p><p>The use case chosen is the business process of a Dental Hospital which has been operational for more than three decades. Earlier, before the use of computers for storing the patient records, each patient record is maintained on a paper and eventually, they have digitalized the patient tracking system and all the old records needed to be digitalized. This process of digitalization involves reading the patient name and details written on the chart, adding the patient and uploading the scanned copy of the patient’s chart into the digital systems.</p><p>Figure 5. shows the business process described and implementation of the same using RPA as well as Cognitive RPA. The process starts by scanning the patient chart. Admin needs to login to the application and adds the patient records after searching for the patient. This is the redundant process that can be automated using RPA except for the need for human intelligence to interpret the handwritten text on the chart to find the patient details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/671/1*2EUtKONvPDfWBaIThPWAjw.png" /><figcaption>Fig 5. Uploading the patient’s chart use case</figcaption></figure><p>With cognitive RPA, this entire process can be automated by training the model to interpret handwritten text using image processing and optical character recognition technologies. The blocks in the green represent the steps that are automated in the process. In this use case, cognitive RPA can be used to automate 80% of the business process.</p><p><strong>Conclusion</strong></p><p>The robots in RPA are software-based that replicate the rule-based repetitive tasks. With RPA, business processes can be implemented faster, easier and at a lesser cost and is more flexible than traditional solutions with lesser error rate.</p><p>RPA is more suitable for problem statements that are deterministic rather than probabilistic. RPA is one of the integration tools that need to be soon integrated with artificial intelligence, machine learning, and cognitive automation tools. Future studies are required on how to combine these technologies so watch the space. Finally, we are currently in the process of completing this use case using C-RPA and once completed will be available in GIT Hub and followed by a new article</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ea918c638d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>