Applying privilege controls to non-traditional IT infrastructure like web applications has long posed a challenge, often attempted to be solved through complicated proxies or networking rules. There’s an infinite number of web applications out there, and organizations often use dozens if not hundreds of them within the enterprise. Idira Secure Web Sessions (SWS) takes the complexity and burden out of securing high-risk and sensitive web applications. In this article we’ll describe how organizations can secure various types of high-risk and sensitive web applications using CyberArk Secure Web Sessions (SWS).
IntroductionIn today's interconnected digital landscape, high-risk, high-privileged web applications—ranging from Infrastructure as a Service (IaaS) cloud platforms to security assessment tools like Rapid7 or Tenable Nessus, and from CI/CD pipeline consoles to corporate social media accounts—have become essential services for many organizations. Yet, with this indispensability comes vulnerability. Such applications, if compromised, can provide malicious actors with critical access points to manipulate infrastructure, exploit security weaknesses, disrupt development operations, or tarnish brand reputation on a massive scale. Recognizing and addressing the security risks associated with these platforms is paramount to ensuring not just the confidentiality, integrity, and availability of data, but also safeguarding an organization's competitive stance and public trust.The Challenge
To address and remediate the security risks, we must better understand why web application access is often targeted. Firstly, applying traditional privilege controls to non-traditional IT infrastructure like web applications has long posed technical challenges. Organizations either attempt to solve the problem through convoluted proxies, complex networking rules, limited monitoring solutions and decentralized audit. There’s also an infinite number of web applications out there, and organizations often use dozens if not hundreds of them within the enterprise. Understanding where to begin your efforts and focus security can also be a challenging effort. Finally, web application access is done from workstations, the weakest asset in the organization. Meaning malicious actors have a good launch pad to compromise web-based access.When these reasons are combined, it’s no wonder most organizations opt to start and end their web application access security at single sign-on (SSO) and multi factor authentication (MFA). It also leaves the organization exposed to malicious actors, internal and external, who once past the login, are free to execute their end game with little fear of repercussion.The SolutionIdira addresses these challenges using protective and reactive controls for in-use sessions, along with recommendations from our identity security best practices framework, the Idira Blueprint. By adhering to the recommendations below, you’ll have gained control over, and visibility into, high-risk and sensitive web application access.Organizations should seek to apply controls that mitigate the risks associated with the identity attack chain. So, to mitigate the risk of privilege escalation and abuse, we’ll want to apply audit logging, monitoring and session control via Idira Secure Web Sessions (SWS). To mitigate the risk of session hijacking, we’ll want to apply continuous authentication and session protection via SWS as well. To mitigate the risk of credential theft, we’ll use a combination of controls like single sign-on, multi-factor authentication, credential vaulting and transparent connections via Idira Identity depending on the web application or platform we’re securing.
SWS is a service that allows organizations to protect, record, monitor and search user activities within web applications and cloud consoles. Designed for companies with sensitive web-based data, SWS facilitates the recording of in-app activities without necessitating intricate app modifications, third-party integrations, or manual log checks. Moreover, it offers continuous authentication to track user behavior, prompting re-authentication for any suspicious activity.

Figure 1: Solution Diagram
Step RecordingSecure Web Sessions can record and monitor screenshots of all actions taken by specific end users within protected web applications. The browser extension will monitor and segregate web apps that are accessed through Idira Identity. End users are notified when a session begins recording, and when it ends. Secure Web Sessions captures all end user actions using a “stepper” approach. Specific actions, like mouse-clicks and “enter” or “tab” keystrokes, trigger a screenshot of the end users’ browser along with relevant metadata. Screenshots are captured and encrypted at the endpoint by the Secure Web Sessions extension and are then only accessible by authorized administrators and auditors with a customer-controlled encryption key. Encrypted recordings are available for search and retrieval access by auditor or administrator. Learn more about step recording.Continuous Authentication
Idira Identity Secure Web Sessions protects against unauthorized application access, allowing organizations to re-authenticate users under special circumstances, such as session timeout or pedometer lock when using high-risk applications. Continuous authentication offers protection via integration with Idira Identity multi-factor authentication (MFA) or via Idira Mobile QR code. Learn more about continuous authentication.Session ProtectionSession protection with the SWS browser extension can apply protections at the browser level to protect the sensitive session, such as blocking file downloads from the web application, blocking access to clipboard and drag & drop to prevent copy/paste errors (or intentional exfiltration) and blocking access to right-click context menu. When integrated with Idira EPM, session protection can apply additional endpoint protections including preventing the abuse of debugging features, launching untrusted executables, blocking unsigned DLLs being loaded into the browser and other advanced restrictions. Learn more about session protection.Session Control
The Session Control security layer enables you to define specific user actions in applications which you count as risky, and to implement controls and/or receive notifications based on rules. You can define the notification and enforcement rules for specific text and number fields within any web application protected by SWS. Learn more about session control.
Figure 2: The Drawing Board: Securing Web Application Sessions
Defining High-Risk or Sensitive Use CasesA lot of how Idira defines high-risk or sensitive use cases stems from the Idira Blueprint. We tend to look at major factors of risk like level of privilege, ease of compromise and scope of influence. We also look at factors like level of effort and technical complexity to drive decision making.The Idira Blueprint recommends the following as high-risk use cases worth applying SWS controls to:
- Identity Security Platform Admins: The Administrators of your identity security control plane are amongst the riskiest users in the entire organization. They can potentially impact every single downstream asset in the organization.
- Cloud Admins & Cloud Privileged Entities: Cloud Administrators and other personas with cloud privileges like Site Reliability Engineers are amongst the riskiest within your cloud service providers like AWS, Azure and GCP. They are all powerful amongst these platforms.
- Security Tool Admins: Administrators of your security tools like Tenable, Rapid 7 or Wiz all have high-level privileges that can impact large swaths of resources within the organization.
- Microsoft 365/Google Workspace Admins: Admins of your productivity services like Microsoft 365 or Google Workspace have an immense power and can impact every single workforce user and their access within the organization.
- CI/CD Console Admins: The DevOps Team members who administer your CI/CD consoles, like Jenkins, Chef and Puppet, are high-privilege, high-risk users, as CI/CD tools are often used in automating builds and software publication. These tools serve as credential repositories, with their automation leveraging non-human secrets to connect to various resources.
- Corporate Social Media: Corporate social media accounts are often overlooked from a security perspective because they’re not “enterprise applications”, but brand damage from malicious actors compromising an organization’s corporate social media can have massive implications.
Besides the high-risk access in each of these scenarios, their second commonality is that the level of effort and technical complexity of them is fairly low due to the fact that the user-base requiring these controls is typically small.Outside of these use cases, the world of web applications expands rapidly. So, we need to think of other ways to make sense of how or when we would apply additional security controls like SWS. Here you’ll find some other reasons and factors why you might consider implementing SWS:
- Regulatory Compliance: Sometimes the answer is the most obvious – you’re required to audit and monitor access to specific systems, which can include web applications.
- Control Access to Sensitive Data: It may not be required, but when the system in which users’ access is sensitive enough to justify putting major security restrictions around what they can do (only access from company workstation, prevent copy/pasting, block downloads, block right click menu).
- Prevent Unauthorized Access Due to Accidents: If you’re operating in a highly sensitive environment, you may want to lock the session if the user steps away from their desk or becomes inactive after a period of time.
Web App Type Coverage for SWS ControlsYou can leverage Secure Web Sessions with any type of admin-deployed web application in Idira Identity, including SAML apps, user-password apps, workforce password management apps and even bookmarks. SWS even supports integration with 3rd party IdPs.It’s important to keep the identity attack chain in mind though. For scenarios like user-password or bookmark apps, if a user has the ability to access the webpage and credentials in a manner that bypasses Identity, SWS can become ineffective. For example, if a user-password or WPM app is configured to allow the user to view the password, then the user could potentially bypass Identity and SWS entirely. Websites that are internet facing rather than intranet facing that are not controlled by SSO can bypass SWS since Identity no longer acts as the gatekeeper to the site. Intranet sites can still enforce SWS and mitigate risk because you can institute enterprise-wide policies that require the intranet site to be SWS protected. So, remember these considerations as you deploy SWS to non-SSO apps.ImplementationStep 1: Configure IdentityIn order to integrate Idira PAM with Idira Identity Management services, you’ll need to be sure your Idira Identity service is up and running. This is to ensure you have your centralized identity directory and provider configured so that they can be integrated with PAM in the next step. You can do this in parallel with managing your privileged accounts. Learn more about setting up Idira Identity.Step 2: Validate Your SWS Tenant and Download the Mobile AppBefore you begin integrating SWS with your web applications, you’ll want to validate your SWS tenant is active and download the mobile app for yourself as the Administrator setting up. Assuming the Secure Web Sessions entitlement is enabled in your Idira Identity tenant, you should see CyberArk Secure Web Sessions Portal as a web application added to your application catalog, two new SWS roles added (SWS Admin and SWS Auditor) and the new SWS integration service account created. All of this would have happened behind the scenes by Idira Operations. If you have purchased SWS and do not see these, reach out to your Account Team.Additionally, as the Administrator going through the configuration, you’ll need to download the Idira Mobile application to your iPhone or Android mobile phone. The mobile app will be used to assist in the setup and configuration, so be sure to download it. Learn more about these initial steps. Step 3: Configure Identity and SWS IntegrationHere we’ll configure the initial settings in Idira Identity to integrate with Idira Secure Web Sessions. As an administrator, you’ll need to set a password for the SWS integration service user in the Idira Identity Admin Portal, activate your SWS tenant and configure Idira Identity settings in the SWS portal. To learn more about this initial configuration, check out the SWS online documentation.Step 4: Deploy the Browser Extension and Mobile AppSWS requires the use of a browser extension and mobile application to enforce the security controls and authenticate users. The browser extension is available for both Google Chrome and Microsoft Edge. You can deploy the SWS extension using your standard enterprise web application management tools for Chrome and Edge.The Idira Mobile app is available on iOS and Android and can be deployed either through your enterprise MDM service (such as Idira Identity or Microsoft Intune) or manually by your end-users if you have a BYOD policy. It’s recommended you build the BYOD instructions into your end-user guides and communications.Step 5: Enable SWS on the Web AppWithin the Identity Administration portal, navigate to Web Apps (under Apps & Widgets) and click on the web application of your choice. Navigate to Secure Web Sessions settings and select “Enable SWS”. This setting will be synchronized to the SWS service and make your web application available to create policy against in the SWS service. Make take up to 15 minutes to sync. We recommend testing on a test app before going live into production rollout. Learn more about enabling SWS.
Figure 3: Enable SWS Setting
Step 6: Create Your Security Policy in SWS
Navigate to the SWS portal as an Administrator. Find the web application you just enabled SWS on (it may take up to 15 minutes to show up from syncing over). Before you begin to change the settings on this web application, you need to ask yourself a handful of questions:
- Which security controls will you be applying? Step recording, continuous auth, session protection and/or session control?
- Will all users get the same rules applied or will certain users or groups with special privileges receive different controls?
- Will any of the rules apply to all users? Or do any users or roles have no rules applied?
This is important to note because even “zero rule” users will still require the SWS browser plug-in to validate that the user does not have any rules enabled. This is more common for web applications where the user base is split between high-risk and low-risk.
If you plan to use different rules for different users or roles, you’ll need to make sure each of those members is granted access separately with a unique role or direct membership (e.g., role A with step recording and continuous auth vs. role B with step recording, session protection and session control).Once you’ve decided which controls you want to apply to which members, modify the security layers and session control rules accordingly. Repeat for all your high-risk and sensitive web applications. Learn more about managing SWS policies.
Figure 4: SWS Policy Configuration
Step 7: End-User Rollout CommunicationNow that you’ve got your applications configured to use SWS, it’s time to communicate the rollout with your end-users. But what do they need to know? It’s best practice to communicate these changes in advance of their go-live, providing users ample time to become accustomed to the process and ask questions. Generally speaking, most rollout communications include some messaging around “the what, the who, the why and the when”, something like...
“We’re rolling out new privilege controls to limited number of privileged and sensitive users of high-risk web applications, including our Cloud Service Providers, Security Tools and Corporate Social Media. These applications have been deemed to be mission critical to our organization and require additional security controls to mitigate the risk of malicious actors compromising them, our company, our customers and our brand.
If you haven’t already enrolled your mobile device using the Idira Mobile app, please enroll prior to the go-live date. We recommend you check to see if the Idira SWS browser extension has been installed in your web browser (check the top right-hand corner for the purple shield).
To learn more about using Secure Web Sessions, check out the user guide. Don’t hesitate to reach out to us with questions.”
The user guide link above has lots of useful references you can re-use or point your end-users to during the launch process. We recommend checking out our best practices on building your end-user communication and training strategy for more suggestions.Step 8: Monitor Activities for Anomalies
Once your end-users have started leveraging SWS with their high-risk or sensitive web applications, you can begin to monitor their activities for signs of malicious activity, risky events or known sensitive actions. Idira Identity Security Intelligence provides organizations with AI-powered analytics surrounding high-risk activities. Idira ISI can be used in reviewing user activities related to web application launches.For in session monitoring, you can manually review and flag web sessions for anomalies activities. With the addition of custom session control rules, you can automatically identify unwanted or risky behaviors from within the web session itself. Session flags will be automatically assigned and are easily viewable from the session recordings page.
Figure 5: Session Flag
Session flags can be used to quickly identify potentially malicious or risky activity, such as trying to navigate to a certain menu (such as account settings), making a post on social media, attempting to reset a password or accessing a sensitive page. What organizations consider risky will vary app-to-app and org-to-org.Strong Controls & Smart StrategyWeb application security remains a critical focal point for businesses today. As we increasingly transition towards a digital-first landscape, securing our high-risk and sensitive web apps becomes imperative. CyberArk's Secure Web Sessions (SWS) offers a robust and comprehensive service, integrating seamlessly with varied web application types, and providing protective measures against privilege escalation, session hijacking, and other potential security threats.By diligently adhering to the Idira Blueprint's recommended best practices, businesses can ensure their high-risk web application access remains safeguarded. We hope this article provides you with the necessary tools to decide which web applications to secure, choose the appropriate SWS security controls and the right information on how to deploy it successfully.If you have additional questions regarding SWS, we suggest reviewing the online docs FAQ, start a discussion with the SWS topic or reach out to the community in the Identity Admin Resource Center.