Self Serve Access Flows

Self serve access flows grant access to a resource based on a user request for a defined time period.

This access flow type is best used for sensitive or highly regulated resources, such as access to production. It also suits just-in-time (JIT) or break-glass access cases.

To create a self serve access flow, you must define the permitted requestors, available resources, and approvers.

Create Access Flow page

---

Prerequisites

Item	Description
Cloud resources	One or more resources in a cloud platform that has been integrated with Apono If you have not already, integrate Apono with a cloud platform to control access to its resources: AWS integrations Azure integrations GCP integrations Kubernetes integrations
Apono identities	One or more identity sources in the Apono system There are various ways to add identities to Apono: Integrate an identity provider Invite a user manually

---

Define permitted requestors

Defining permitted requestors

Follow these steps to define the permitted requestors:

1. On the Access Flows page, click Create Access Flow. The Create Access Flow page appears.
2. Click Self Serve. The Self Serve fields appear below.

3. Enter an alphanumeric, user-friendly Access Flow Name.

4. Click When. A settings window appears to set the access period.

5. Set the access period.

   Period	Description
   Always	(Default) Applies to the requester conditions at all times Follow this step to set this period: Select Always.
   Only on	Applies to the requester conditions during a specific time frame Follow these steps to set a specific period: In the settings window, select Only on. Select one or more days of the week. In the From field, select a start time from the dropdown menu. In the to field, select an end time from the dropdown menu. Select a timezone from the dropdown menu.

6. Click Select attribute to select an IdP attribute, such as User or Group.

7. (Optional) Click is to select conditional logic from the menu options.

Other operators include the following:

• Is not

• Contains

• Does not contain

• Starts with

1. Click Select value to select one or multiple users or groups from the menu options. This selection determines who is permitted to request access.

2. (Optional) Add another condition.

   1. Under the last listed requestor, click +. A new row appears.

   2. Repeat steps 6-8.

   3. Select the conditional logic for the multiple requestors.

      Condition	Description
      AND	(Default) Allows the user to request access if they meet all the attributes of the user group
      OR	Allows the user to request access if they meet any of the attributes of the user group

---

Define the resource

Defining integration, access scope, and bundle resources

You can define access to specific resources in an Apono integration, bundle, or access scope.

Integrations

Follow these steps to define access to specific resources:

1. Under Request access to, click Select target > Integrations.

2. Select an integration. The Select resource type panel appears.

3. Select the resource type.

4. Click Done. The panel closes.

5. Click permissions. The Permissions menu appears.

6. Select one or more permissions to grant the requester.

7. (Optional) Refine the available resources:

   1. Click in the populated to field. A list of resources appears.

   2. Select one or several resources.

By default, the user has access to Any resources. However, the following options allow you to define access more granularly:

• Any resources except specific

• Select by name

• Select by tags

1. (Optional) Add another target:

   1. Click + at the end of the row. A new target row appears.

   2. Repeat steps 1-7 or add a bundle or access scope.

Bundles

To ensure you do not exceed the AWS inline policy character limit, read AWS Limitations when adding bundles with AWS resources.

Follow these steps to define access to a specific bundle:

1. Under Request access to, click Select target > Bundles.

2. Select a bundle.

3. (Optional) To add another bundle, click +. A new target row appears.

4. Repeat steps 1-2 or add an integration or access scope.

Access Scope

Follow these steps to define access to a specific access scope:

1. Under Request access to, click Select target > Access Scope. The Select access scope menu appears.

You may enter keywords into the search bar to locate an access scope.

1. (Optional) Click (eye icon) to preview the contents of the access scope in a popup window.
2. Select an access scope.

You can also click + Create New Access Scope if none of the existing access scopes meet your needs. The Inventory page appears. You can create and use the new access scope.

1. (Optional) To add another access scope, click +. A new target row appears.

2. Repeat steps 1-3 or add an integration or bundle.

---

Set access duration and approval process

Access duration and approval process

Follow these steps to define the duration of access:

1. Click in the populated Grant for field. The granting period settings appear.

   Period	Description
   Custom	(Default) Grants the requester access for a custom period The default granting period is set to 1 hour. Follow these steps to grant access for a custom period: Select the first radio button. From the right dropdown menu, select a time unit. In the first field, enter a numerical value for the time unit. In the second field, select a time unit from the dropdown menu.
   Indefinite	Grants the requester access indefinitely Follow this step to set this period: Click Indefinite.

2. Click Automatic to select the approval type.

   Period	Description
   Automatic	Automatically grants the requester access for the specified period Automatic approval is the default setting.
   Approval of	Grants the requester access for the specified period upon the approval of certain parties For more information, learn how to set up custom approval.

3. Click Create Access Flow.

Set up custom approval

Custom approval flow

Approval of provides in-depth options to customize the approval flow. This approval type is ideal for production environments and highly sensitive resources.

Follow these steps to set up Approval of:

1. Click the populated with field. The approval type menu appears.

2. Click Approval of. The Approval of fields appear.

3. Click Select attribute to select an IdP attribute, such as User, Group, or Owner.

If you have connected an incident response integration with Apono, the attribute can also be an on-call shift.

1. (Optional) Click is to select conditional logic from the menu options.

Other operators include the following:

• Is not

• Contains

• Does not contain

• Starts with

1. Click Select value to select one or multiple users or groups from the menu options. This selection determines who is permitted to approve access.

2. (Optional) Add another approver condition.

   1. Immediately beneath the last list approver, click +. A new row appears.

   2. Repeat steps 3-5 to add another approver to the group.

   3. Select the conditional logic for the multiple approvers.

      Condition	Description
      AND	(Default) If you have multiple attributes in the approval group, AND requires the approver to meet all the attributes.
      OR	If you have multiple attributes in the approval group, OR requires the approver to meet only one of the attributes.

3. (Optional) Add another approver group.

   1. Beneath the last approver group, click +. A new approval group appears.

   2. Repeat steps 3-5 to add another approver to the group.

   3. Select the conditional logic for the multiple groups of approvers.

      Condition	Description
      ANY OF	If you have multiple approval groups, ANY OF only requires one approver belonging to any group to approve access.
      ALL OF	If you have multiple approval groups, ALL OF requires one approver per group to approve access.

---

Enable settings

Apono allows administrators to apply various settings to enhance the security of access flows.

All admin settings are optional.

Access flow settings

Follow these steps to configure settings:

1. In the Access flow labels, enter a value and press Enter OR select an existing label.

A label identifies an access flow for streamlined organization and use. When assigned to an access flow, labels appear in the access flow tiles on the Access Flows page.

1. Click the toggle to enable any of the following settings. When enabled, the toggle turns green.

Setting	Description
Require MFA	Requires grantees to complete multi-factor authentication to complete a request We strongly recommend enabling MFA for access requests to sensitive resources. The grantee will need to enable multi-factor authentication.
Require justification	Requires grantees to enter a justification for their request
Require Approve Reason	Requires approvers to provide a reason (limited to 124 characters) when approving or rejecting a request. If disabled, providing a reason is optional. Requester Experience Requesters see only the rejection reason. The reason can be reviewed in two locations: On the Closed Requests tab, click the request to open the Access Request panel. The Approver Reason appears under Approvals. On the Closed Requests tab, hover over Rejected in the STATUS column of the request. Admin Experience Admins can view both approval and rejection reasons. The reason be viewed in two locations: On the Activity page, click the request to open the Access request details panel. The Approver Reason appears on the Timeline tab. In a report, the approver reason appears in the APPROVER_REASON column.
Requester cannot approve their own request	Prevents users from approving their own access requests If the user is a member of an approval group, they will not receive a notification to approve the request.

\