ACCESS-DEF CyberArk Defender Access (ACC-DEF) Questions and Answers

The CyberArk Identity Connector provides a secure, mutually authenticated, inbound communication channel with the CyberArk Identity SaaS. This feature is essential for ensuring that the communication between CyberArk Identity’s cloud services and the internal network is secure and authenticated, preventing unauthorized access and potential security breaches.

References: The information is based on the official CyberArk documentation which describes the installation and deployment of the CyberArk Identity Connector, highlighting its role in enabling secure communication between CyberArk Identity and other services on the internal network12. It is also supported by the content found in the CyberArk Identity release notes and product announcements3.

When the “Challenge Pass-Through Duration” is set to “No Pass Through”, it ensures that users are presented with an authentication challenge every time they attempt to access the portal or applications. This setting is crucial for maintaining strict security protocols and ensuring that user identities are verified at each access attempt, preventing unauthorized access and enhancing overall security posture.

 In the context of CyberArk Identity, when dealing with websites that do not require user authentication, the appropriate connector to use is typically a Bookmark. This type of connector acts as a simple link to the website without the need for any authentication process. It’s used for quick access to web resources that are publicly available and do not require a login.

References: The information is based on general knowledge of web application connectors and their purposes. For the most accurate and detailed information, please refer to the latest CyberArk Defender Access (ACC-DEF) course materials and documents. Specific details about the use of connectors for different types of applications can be found in the CyberArk documentation12.

The “Land and Catch” feature is supported by browsers that are compatible with the CyberArk Identity Browser Extension. This feature allows users to add applications to their User Portal by recognizing when users enter credentials and offering to store the user’s credentials. The supported browsers for this feature are Google Chrome, Firefox, and Microsoft Edge12.

References: The information about supported browsers for the “Land and Catch” feature can be found in the CyberArk public documentation and the CyberArk training resources123. It’s important to note that the Browser Extension for Internet Explorer and Safari is deprecated, which means these browsers are no longer supported for new features like "Land and Catch"2.

 In UBA systems, events are typically associated with user accounts, which are identified by usernames. Therefore, to find all events related to a specific user, you would filter by the username associated with that user’s account. The filter user_name ='ivan.helen@acme' would be used to retrieve all events where the username ‘ivan.helen@acme’ is involved.

References: This guidance is based on standard practices for querying event data in UBA systems. For the most accurate and detailed explanation, please refer to the official CyberArk Defender Access (ACC-DEF) study guide and course documentation, which can be found through the CyberArk training portal1.

The CyberArk Identity mobile app is available for download through official app distribution platforms such as the Apple App Store for iOS devices and Google Play Store for Android devices. These platforms are the standard sources for obtaining mobile applications securely. The Admin Portal is typically used for managing CyberArk solutions and does not distribute mobile apps, the support portal is used for documentation and troubleshooting, and mobile apps are generally not distributed via email attachments due to security risks.

When users are unable to enroll into the system using the enrollment code, it could be due to limitations on the number of endpoints that can join or lack of clarity in the enrollment process. By setting the maximum number of joinable endpoints to “unlimited”, you remove any restrictions on the number of devices that can be enrolled with the same code. Adding a description within the enrollment code can provide users with additional context or instructions, which may help them during the enrollment process.

References: The information is based on general best practices for managing endpoint authentication and enrollment processes. For the most accurate and detailed information, please refer to the latest CyberArk Defender Access (ACC-DEF) course materials and documents. Specific details about managing authentication certificates and enrollment can be found in the CyberArk documentation12.

C:\Users\Waqas Shahid\Desktop\Mudassir\Untitled.jpg

Within the CyberArk Admin Portal under User Security Policies, the Account Unlock options allow administrators to set policies for how users can unlock their accounts:

• The option to allow for Active Directory users provides the capability for users who utilize Active Directory as their directory service to unlock their own accounts, often necessary after an account has been locked due to multiple failed login attempts.
• The restriction to only allow browsers with an identity cookie helps enhance security by ensuring that account unlock requests come from a browser that has already been recognized by the system, indicating a previous successful login, and thus a lower risk of fraudulent unlock attempts.
• Showing a message to users on the desktop login UI that their account is locked is a direct way to inform users who are attempting to log in from their desktops that their account is currently inaccessible and action may be needed on their part.
• The message explaining the account unlock experience is a user-friendly notification that informs users who have gone through the unlock process that their sign-in experience was different due to the account having been locked and subsequently unlocked, which can be a reminder of the security processes in place and the importance of maintaining secure login credentials.

 In the event that a Chief Executive Officer (or any user) loses their phone and cannot perform Multi-Factor Authentication (MFA) to log in to work, the immediate action to enable access without delay is to use the MFA Unlock feature through the Admin Portal (D). This feature allows an administrator to bypass the MFA requirement temporarily for a user, ensuring that they can access their work without significant interruption.

References: The MFA Unlock action is a part of the administrative capabilities within CyberArk Defender Access, which provides various options for managing user access and authentication. This feature is specifically designed to address situations where users are unable to perform MFA due to reasons such as losing their phone1.

The Infinite Apps feature is part of the CyberArk Identity Browser Extension. It simplifies the process of adding SaaS user-password applications that are not listed in the CyberArk Identity App Catalog. The feature includes the App Capture utility, which automatically discovers the username and password fields on a web application’s login page. Once discovered, it adds the application to the portal’s Apps page, allowing it to be deployed with single sign-on capabilities to user portals and devices. If the App Capture utility cannot automatically discover the fields, it provides the option to select them manually. Additionally, users can add applications to their user portal Apps pageand devices using the browser extension, subject to configuration settings managed by the “Allow users to add personal apps” policy.

References: This information can be found in the CyberArk documentation for adding web applications using CyberArk Identity Infinite Apps1.

Enabling “Workflow” within an app connector in CyberArk allows for the creation and management of approval workflows. This means that when a user requests access to an application, an approval process can be initiated where one or more designated approvers can grant or deny access. This feature is crucial for maintaining control over who has access to sensitive applications and data, ensuring that only authorized users can gain entry.

References: The information is based on the official CyberArk documentation which provides an overview of the App Gateway workflow and the actions that can be taken when “Workflow” is enabled within an app connector12. It is also supported by the content found in the CyberArk Identity documentation related to managing application access requests2.

The Self-Service Password Reset (SSPR) in CyberArk Defender Access allows users with Active Directory accounts who have forgotten their password to reset it themselves (A). It also provides security measures such as setting a maximum number of times a user can reset their password within a specific timeframe (D), and requiring users to respond to a CAPTCHA before resetting their password (E), to prevent abuse of the password reset feature.

References: The information is based on the CyberArk documentation which outlines the configuration of self-service options for users, including the ability to enable SSPR for Active Directory users, the option to limit password resets within a timeframe, and the requirement for CAPTCHA responses for added security12.

The authentication mechanism that falls under the category of “Something you know” typically refers to knowledge factors, which are based on information that the user must be able to recall and provide upon request. In the context of CyberArk Defender Access, a security question is an example of a knowledge factor because it requires the user to answer a question that only they should know the answer to. This contrasts with other mechanisms like a phone call or text message, which are considered “Something you have” because they rely on the user possessing a specific device to receive the call or message. FIDO2 Authenticators, on the other hand, are categorized as “Something you are” or “Something you have,” depending on the specific type of authenticator used, as they can include biometric factors or a physical security key1. References: CyberArk’s definition of MFA

The error message “Not Authorized. You do not have permission to access this feature” typically indicates that a user has attempted to access a feature or area within CyberArk Defender Access for which they do not have the necessary permissions or rights. This is most commonly associated with a non-administrative user trying to access an administrative feature. Administrative rights and permissions in CyberArk are tightly controlled and are assigned based on the role and scope of the user’s responsibilities. Users are only able to perform actions for which they have been explicitly granted permission, and attempting to access features beyond their permission level will result in such an error1.

References: CyberArk’s documentation on permissions

Cindy’s role in the IT Audit Department suggests that she requires access to features and information pertinent to auditing within CyberArk Identity. The “Everybody” role is a default role that typically includes basic user permissions. Adding the “Auditor” role would grant her the specific administrative rights needed to perform audit-related tasks, which align with her job responsibilities in the IT Audit Department. This combination ensures that she has the necessary permissions to access and manage audit functions without granting unnecessary administrative privileges that come with the “IT Admin” role1.

References: CyberArk’s documentation on administrative rights

C:\Users\Waqas Shahid\Desktop\Mudassir\Untitled.jpg

To automatically create user accounts in Salesforce with varying licenses via CyberArk Identity, one must follow a sequential process starting with the verification of provisioning credentials. This is the foundation for ensuring that the provisioning process has the necessary permissions and access to make changes in Salesforce. Once verified, provisioning must be enabled on the Salesforce application within CyberArk Identity, which allows the two systems to communicate and transfer data.

Following this, roles need to be created within CyberArk Identity that corresponds to different Salesforce licenses or entitlements. Roles in CyberArk Identity define the access level and permissions that a user account will have when provisioned into Salesforce.

After roles are established, role mappings are added. Role mappings are associations between the CyberArk roles and Salesforce licenses. This tells CyberArk Identity which Salesforce license to assign when it creates a new user account based on the role that has been assigned to the user in CyberArk.

Finally, the synchronization step is initiated. During synchronization, CyberArk Identity communicates with Salesforce to create user accounts with the appropriate licenses as defined by the role mappings. Synchronization ensures that the user accounts in both systems are up-to-date and that any changes in roles or permissions are reflected accurately in Salesforce.