<?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 Juliani Sarah on Medium]]></title>
        <description><![CDATA[Stories by Juliani Sarah on Medium]]></description>
        <link>https://medium.com/@juliani.sarah?source=rss-7c4e07ca1cbc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*IE36Q7isJwd60VBL</url>
            <title>Stories by Juliani Sarah on Medium</title>
            <link>https://medium.com/@juliani.sarah?source=rss-7c4e07ca1cbc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:52:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@juliani.sarah/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[Streamlining IAM Processes: Transitioning from Manual to Automated Efficiency]]></title>
            <link>https://medium.com/fsmk-engineering/streamlining-iam-processes-transitioning-from-manual-to-automated-efficiency-e2f2eb3b8a79?source=rss-7c4e07ca1cbc------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2f2eb3b8a79</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[enterprise-security]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[it-operations]]></category>
            <category><![CDATA[identity-and-access]]></category>
            <dc:creator><![CDATA[Juliani Sarah]]></dc:creator>
            <pubDate>Fri, 17 Jan 2025 02:52:30 GMT</pubDate>
            <atom:updated>2025-01-17T02:52:30.004Z</atom:updated>
            <content:encoded><![CDATA[<p>Identity and Access Management (IAM) is used in IT operations to ensure suitable persons have timely access to resources. However, any IT professional will tell you that manually managing IAM tasks is daunting. This entails managing multiple duties, achieving rigorous deadlines, and ensuring an error-free environment. Automation has become necessary rather than elective, providing a path to more smooth IAM operations.</p><p><strong>Difficulties of Manual IAM Procedures</strong></p><p>1. Huge Task Volume</p><p>IAM management is more than just granting or revoking access. It entails sophisticated operations like as provisioning, deprovisioning, access evaluations, and role assignments. When these duties are managed manually, they can easily accumulate, causing IAM Engineer workers to get overloaded with messages, emails, and ticketing systems.</p><p>2. Operations that are time-critical and high-risk</p><p>Timing is key in IAM. Delays in granting access to new employees can interrupt their onboarding experience, while late de-provisioning might expose the organization to security risks. These obligations are both important and time-consuming, and mistakes can have major implications.</p><p>3. Unnoticed Success and Noticeable Failures.</p><p>Successful IAM operations frequently go unnoticed, yet even a single overlook can have serious consequences, such as compliance violations, security breaches, or dissatisfied users. Manual processes leave too much possibility for human mistakes, with IAM Engineers personnel frequently taking the blame.</p><p>4. Adjusting to Organisational Growth.</p><p>As businesses grow, managing IAM becomes increasingly difficult. Manual techniques become unsustainable as the number of employees, systems, responsibilities, and access requests increases. Without automation, the task becomes unmanageable, placing an unnecessary demand on IAM Engineer workers.</p><p><strong>The necessity of automation.</strong></p><p>Automation transforms IAM processes from a barrier to a streamlined, efficient system. By using tools and scripts for repetitive work, IT teams may maintain consistency, reduce errors, and devote more time to strategic projects. It’s about increasing accuracy, not simply speed.</p><p><strong>Our Journey to Automation</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*REoevCWklcKOhLmpfDiqdw.png" /></figure><p><strong>From Slack to Jira.</strong></p><p>Initially, access requests were manually processed using Slack channels. Employees would request access, and IAM engineers handled the process manually by:</p><ol><li>Logging into JumpCloud.</li><li>Locate the user’s profile.</li><li>Adding the user to the correct group.</li><li>Updating the requester on the status.</li></ol><p>With 50–60 tickets per week, this process took 5–7 minutes per ticket, totaling 5–7 hours weekly. The repetitious nature of these operations constituted a considerable bottleneck.</p><p>Transitioning to Jira improved monitoring and documentation, but granting and revoking access remained manual. Engineers still needed to:</p><ol><li>Open a Jira ticket.</li><li>Determine the requested access.</li><li>Log into JumpCloud.</li><li>Make the necessary access modifications.</li><li>Update the Jira ticket’s status.</li></ol><p><strong>Introducing the ITSM dashboard.</strong></p><p>Recognizing the value of automation, we created an internal ITSM dashboard to centralize and automate access management procedures. The dashboard connects with JumpCloud APIs, allowing for smooth automation.</p><p>This is how it works:</p><ul><li><strong>Mapping system names to group IDs</strong>: The dashboard associates system names in Jira with JumpCloud group IDs. For example, a Jira request for Cloudflare causes the dashboard to fetch the associated Cloudflare user group ID from JumpCloud.</li><li><strong>Automated Access Granting/Revoking</strong>: Once a Jira issue has been authorized by the Line Manager and System Owner, the dashboard uses the JumpCloud API to add/remove the user to/from the appropriate group.</li><li><strong>Real-time updates</strong>: When access is granted/revoked successfully, the automated add a remark to the Jira ticket confirming the action taken.</li></ul><p><strong>Leveraging the JumpCloud API for Line Manager Integration</strong></p><p>We use internal automation to retrieve Line Manager details for Jira tickets, leveraging the JumpCloud API for this. The API allows for more accurate and streamlined integration, improving the whole workflow.</p><p><strong>Expanding Automation to Internal Tools.</strong></p><p>Beyond JumpCloud, we’ve extended Jira automation to handle user provisioning and de-provisioning for internal tools. The process now includes:</p><ol><li>Reading Jira tickets to determine requested roles.</li><li>Searching for team members using the internal tool.</li><li>Assigning or revoking roles as defined.</li><li>Updating the Jira ticket with the status.</li></ol><p>This eliminates the need for manual role assignment, hence increasing efficiency.</p><p><strong>Scalability using SAML 2.0</strong></p><p>We’ve integrated all systems that support SAML 2.0 with JumpCloud. This guarantees that IAM processes are consistent and scalable throughout the enterprise, simplifying access control for both internal and external tools.</p><p><strong>Key Takeaways</strong></p><p>Our transition from manual IAM operations to automation reveals numerous significant benefits:</p><ul><li><strong>Enhanced Precision</strong>: Reduced human error in critical operations.</li><li><strong>Time Efficiency</strong>: Automation saves hours of manual labor, allowing engineers to focus on critical projects.</li><li><strong>Improved security</strong> through timely access revocation and policy compliance.</li><li><strong>Scalability</strong>: The unified ITSM dashboard and JumpCloud connection ensure that the organization can scale as it grows.</li><li><strong>Better User Experience</strong>: Employees receive faster responses to access requests, which increases satisfaction.</li></ul><p><strong>Conclusion</strong></p><p>Having worked with IAM management personally, I appreciate the difficulties of doing everything manually. Transitioning to automated IAM workflows has improved our operations’ efficiency, scalability, and reliability. We built a strong system that satisfies the needs of a growing firm using Jira, JumpCloud, Slack, and our ITSM dashboard.</p><p>Consider starting with simple automated measures if your organization still uses manual IAM operations. As our experience has demonstrated, the time and effort saved are well worth the investment.</p><p>Automation is more than just convenience; it’s also about improving performance.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2f2eb3b8a79" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fsmk-engineering/streamlining-iam-processes-transitioning-from-manual-to-automated-efficiency-e2f2eb3b8a79">Streamlining IAM Processes: Transitioning from Manual to Automated Efficiency</a> was originally published in <a href="https://medium.com/fsmk-engineering">Technology @ Funding Societies | Modalku</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>