Avari Solutions

Okta API Access Management

Your custom apps are increasingly modern with an API backend. Secure enterprise data and enable developers to focus on the user experience. Control access for any type of user or service in one place. Create, maintain and audit API access policies.

Features

  • 0Auth 2.0 API Authorization
  • Identity Driven Policy Engine
  • Centralized API Administration
  • Configurable Policy
  • Tie to Identity
  • API Flexibility
  • Centralized Authorization

Benefits

  • Single Sign On
  • Lifecycle Management
  • Adaptive MFA
  • API Access Management

Pricing

£1.55 per user per month

Service documents

Framework

G-Cloud 11

Service ID

3 1 1 4 8 7 3 2 8 9 2 3 0 0 0

Contact

Avari Solutions

Ross Garman

08450360040

ross.garman@avari.solutions

Service scope

Software add-on or extension
Yes, but can also be used as a standalone service
What software services is the service an extension to
All Okta Products:

Single Sign On
Universal Directory
API Access Management
Advanced Server Access
Authentication
Authorization
B2B Integration
Cloud deployment model
Public cloud
Service constraints
Support is provided as a remote Managed Service
System requirements
  • A server or VM running Windows Server 2008R2 or later.
  • The server should be a member of the Windows Domain.
  • The server should have access to domain controller.
  • Service account in the Domain Users AD group.
  • A clean installation of Microsoft

User support

Email or online ticketing support
Email or online ticketing
Support response times
15 Minutes
User can manage status and priority of support tickets
Yes
Online ticketing support accessibility
None or don’t know
Phone support
Yes
Phone support availability
24 hours, 7 days a week
Web chat support
No
Onsite support
Yes, at extra cost
Support levels
1st, 2nd and 3rd line support is provided by cloud support engineers and in some cases a technical account manager is assigned. Costs for the service start from £1200 (plus travel & accommodation where required) and will be based on the levels required, response times, resolutions times and hours of availability required. Calls are processed and managed based on standard P1, P2, P3, P4 classifications. Support channels provided include web, phone and email. Service Level Agreement (SLA) is defined and provided to the customer as part of the service design and transition to their live operations environment.
Support available to third parties
Yes

Onboarding and offboarding

Getting started
To get started, check out our Training Resources website (https://support.okta.com/help/oktaDocumentationPage). Visit the Okta Help Center for FAQs and support articles and the Okta Community. Also if you are an App Partner, you’ll also be eligible to join live Okta training sessions.
Service documentation
No
End-of-contract data extraction
Upon request by Customer made prior to the effective date of termination, Okta will make available to Customer, at no cost, for a maximum of thirty (30) days following the end of the Term for download a file of Customer Data (other than personal confidential information such as, but not limited to, User passwords may not be included except in hash format) in comma separated value (.csv) format.
End-of-contract process
After such 30-day period, Okta shall have no obligation to maintain or provide any Customer Data and shall thereafter, unless legally prohibited, be entitled to delete all Customer Data by deletion of Customer’s unique instance of the Service; provided, however, that Okta will not be required to remove copies of the Customer Data from its backup media and servers until such time as the backup copies are scheduled to be deleted in the normal course of business; provided further that in all cases Okta will continue to protect the Customer Data in accordance with this Agreement. Additionally, during the Term, Customer may extract Customer Data from the Service using Okta’s standard web services.

Using the service

Web browser interface
Yes
Supported browsers
  • Internet Explorer 7
  • Internet Explorer 8
  • Internet Explorer 9
  • Internet Explorer 10
  • Internet Explorer 11
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari 9+
  • Opera
Application to install
No
Designed for use on mobile devices
Yes
Differences between the mobile and desktop service
Apple users should download Okta Mobile from iTunes. Android users should download it from the Google Play Store. Once installed, you’ll need to know your company's Okta organization name and your Okta username and password. Once authenticated, Okta Mobile will ask you to create a PIN. Simply enter your PIN again, and you’re ready to access your work apps from anywhere. For desktop service, to access Okta, go to your company's custom Okta URL in any web browser. Your company's custom Okta URL will be "company.okta.com." For example, if your company is called ABC, the URL would be ABC.okta.com.
Service interface
No
API
Yes
What users can and can't do using the API
Okta's API is a REST API based upon CRUD principles (Create, Read, Update and Delete). The CRUD principles using via the API can be used to set up, manage and make changes to the service, including interactions against Users, Applications, Groups, Administration (Managing Admins and Event Information). The API can also be used for authentication and session management. Full Documentation, Developer Instances and Postman templates are also availably publicly via the developer.okta.com website.
API documentation
Yes
API documentation formats
  • HTML
  • PDF
API sandbox or test environment
Yes
Customisation available
Yes
Description of customisation
Modular licensing allows for specific solution creation per user demand. Dashboard and branding can be altered to meet user needs. API allows for further customisation, such as integration to existing applications or websites.

Scaling

Independence of resources
Okta must be available for any other app to be accessed and therefore there’s no good time to be down. As a result we are built for high availability – no planned downtime, no maintenance windows - and we guarantee 99.9% uptime. You can verify our reliability metrics and learn more about the availability of our service at trust.okta.com.

Analytics

Service usage metrics
Yes
Metrics types
Cross-application analytics spanning usage, utilization, and cost that provide IT with the insight needed to optimize its cloud investments and address its compliance need. The Okta Usage report contains data about who has signed into Okta, how many times and the dates of last login for the past 30 days. When you click on the report, it allows you to specify the range.
Reporting types
  • API access
  • Real-time dashboards
  • Regular reports

Resellers

Supplier type
Reseller providing extra features and support
Organisation whose services are being resold
Okta

Staff security

Staff security clearance
Other security clearance
Government security clearance
Up to Developed Vetting (DV)

Asset protection

Knowledge of data storage and processing locations
Yes
Data storage and processing locations
Other locations
User control over data storage and processing locations
No
Datacentre security standards
Complies with a recognised standard (for example CSA CCM version 3.0)
Penetration testing frequency
At least once a year
Penetration testing approach
Another external penetration testing organisation
Protecting data at rest
  • Physical access control, complying with CSA CCM v3.0
  • Physical access control, complying with SSAE-16 / ISAE 3402
  • Other
Other data at rest protection approach
The public/private key pair is used for SAML transactions, while the symmetric key is used to encrypt a customer’s sensitive data (e.g., Facebook password, Okta API tokens, and sensitive attributes) at rest. Both sets of keys are stored in a key store that Okta encrypts with a unique org master key. For example, Org1’s key store is encrypted with Org1’s master key, whereas Org2’s key store is encrypted with Org2’s master key.
Data sanitisation process
Yes
Data sanitisation type
  • Explicit overwriting of storage before reallocation
  • Deleted data can’t be directly accessed
Equipment disposal approach
Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001

Data importing and exporting

Data export approach
Currently, the only way to bulk extract data from Okta is using the Okta API (freely documented). Optional Services can be purchased in order to provide assistance in the data extraction process.
Data export formats
Other
Other data export formats
Via the okta API
Data import formats
  • CSV
  • Other

Data-in-transit protection

Data protection between buyer and supplier networks
Other
Other protection between networks
Multiple investments are made to ensure customer data is secure and reliable. The customer's data and access to it, is isolated at the customer level within Okta’s data layer. Physically, that data is stored using the AWS Elastic Block Storage (EBS) service. To meet Okta’s one-hour recovery point objective, database snapshots of the EBS volumes are taken regularly and stored in AWS’s S3 storage service. Access to S3, even within AWS, must be through SSL, providing additional insurance that the data is also transferred securely.
Data protection within supplier network
Other
Other protection within supplier network
Within Amazon S3, Okta restricts access at both the bucket and object level and only permits authenticated access by the bucket and/or object creator—Okta. Any request to access data must be authenticated using an HMAC-SHA1 signature of the request using the user’s private key. Further, an authenticated user’s permission is controlled by an access control list (ACL) that independently determines read/write permissions at the bucket and object level. All access is logged and audited.

Availability and resilience

Guaranteed availability
Identity is Always On, and so are we. We built the Okta service for high availability and a guaranteed uptime. https://support.okta.com/help/Documentation/Knowledge_Article/Okta-Support-Service-Level-Agreements-by-Customer-Success-Package
Approach to resilience
Since we are aiming for billions of users and authentications, in 2014 we rolled out a new platform architecture that will get us to extreme scale. We call this architecture “cells”. A cell is a self-contained instance of the entire Okta service. Any fault in infrastructure is contained within a cell using a High Availability (HA) architecture, and even in case of an entire datacenter going down, another cell in a different geography takes ownership of the affected accounts within an hour.
Outage reporting
The newly updated Okta Trust Site provides status of Okta’s availability at all times by going to trust.okta.com. All users will also receive email alerts informing them of the problem, estimated outage time and a further email once fully restored.

Identity and authentication

User authentication needed
Yes
User authentication
  • 2-factor authentication
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google Apps)
  • Dedicated link (for example VPN)
  • Username or password
  • Other
Other user authentication
Users can authenticate to Okta with a password in one of two ways:
• Local Okta password
• Delegated authentication
Access restrictions in management interfaces and support channels
For many organizations, AD is the core repository of users and the associated credentials used to govern access to network and application resources. Okta integrates with AD to extend this capability to cloud-based applications and enables:
• Automated import of users from AD to Okta, with adjustable frequency
• Automatic provisioning and de-provisioning of access to applications and Okta, based on changes in AD and security group membership
• Authentication against AD with the user’s AD credentials to grant access to Okta
Access restriction testing frequency
At least once a year
Management access authentication
  • 2-factor authentication
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google Apps)
  • Dedicated link (for example VPN)
  • Username or password

Audit information for users

Access to user activity audit information
Users have access to real-time audit information
How long user audit data is stored for
Between 6 months and 12 months
Access to supplier activity audit information
Users have access to real-time audit information
How long supplier audit data is stored for
Between 6 months and 12 months
How long system logs are stored for
Between 6 months and 12 months

Standards and certifications

ISO/IEC 27001 certification
Yes
Who accredited the ISO/IEC 27001
The Certification Body of Schellman & Company, Inc.
ISO/IEC 27001 accreditation date
08/07/2016
What the ISO/IEC 27001 doesn’t cover
Schellman & Company, LLC examined the description of Okta, Inc.’s (“Okta” or the “service organization”) OnDemand Identity-as-a-Service (“IDaaS”) system for the period May 1, 2015, to May 31, 2016, (the “description”) based on the criteria set forth in paragraph 1.26 of the AICPA Guide Reporting on Controls at a Service Organization Relevant to Security, Availability, Processing Integrity, Confidentiality, or Privacy (SOC 2®) (“description criteria”) and the suitability of the design and operating effectiveness of controls described therein to meet the criteria for the security, availability, and confidentiality principles set forth in TSP section 100, Trust Services Principles and Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy (AICPA, Trust Services Principles and Criteria) (“applicable trust services criteria”), throughout the period May 1, 2015, to May 31, 2016. We have also examined the suitability of design and operating effectiveness of controls to meet the requirements set forth in the Cloud Security Alliance's Cloud Controls Matrix Version 3.0.1 control specifications.
ISO 28000:2007 certification
Yes
Who accredited the ISO 28000:2007
The Certification Body of Schellman & Company, Inc.
ISO 28000:2007 accreditation date
08/07/2017
What the ISO 28000:2007 doesn’t cover
Schellman & Company, LLC examined the description of Okta, Inc.’s (“Okta” or the “service organization”) OnDemand Identity-as-a-Service (“IDaaS”) system for the period May 1, 2015, to May 31, 2016, (the “description”) based on the criteria set forth in paragraph 1.26 of the AICPA Guide Reporting on Controls at a Service Organization Relevant to Security, Availability, Processing Integrity, Confidentiality, or Privacy (SOC 2®) (“description criteria”) and the suitability of the design and operating effectiveness of controls described therein to meet the criteria for the security, availability, and confidentiality principles set forth in TSP section 100, Trust Services Principles and Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy (AICPA, Trust Services Principles and Criteria) (“applicable trust services criteria”), throughout the period May 1, 2015, to May 31, 2016. We have also examined the suitability of design and operating effectiveness of controls to meet the requirements set forth in the Cloud Security Alliance's Cloud Controls Matrix Version 3.0.1 control specifications.
CSA STAR certification
No
PCI certification
No
Other security certifications
Yes
Any other security certifications
  • HIPAA
  • FedRamp
  • SOC2
  • ISO 27001:2013 Certification

Security governance

Named board-level person responsible for service security
Yes
Security governance certified
Yes
Security governance standards
  • ISO/IEC 27001
  • Other
Other security governance standards
SOC 2 Type II Certification
Cloud Security Alliance Security, Trust, & Assurance Registry (CSA STAR)
Information security policies and processes
The Okta team understands the need for its service to be both highly available and secure, and every aspect of the organization reflects this. From its hiring practices to the software it develops and the operational environment in which it runs, Okta understands that it is Always On. Okta enables enterprise administrators to increase security above what is available through traditional on-premises technologies. By offering strong password management capabilities, account management capabilities, easy-to-deploy multifactor authentication, and encrypted attributes, the enterprise is now able to put strong controls on high-value data while balancing the ease-of-access users demand. Okta is a leader in third-party certifications, physical and network security architecture, and reliability, so customers need not worry about putting authentication data in the cloud. Okta is trusted by organizations of all sizes and in all industries.

Operational security

Configuration and change management standard
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Configuration and change management approach
Okta’s change control process is audited and attested to SOC 2 Type II. A weekly meeting is held to determine which enhancements, and/or fixes will be released. The final build is promoted to QA, which is responsible for all security, and regression testing on the build. Once the build passes testing, it is finalized and released to technical operations who perform deployment testing of the final build. After successful deployment testing, the build is deployed to staging where it will bake in for a week, afterwards it is tested once more before going live.
Vulnerability management type
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Vulnerability management approach
Okta conducts continuous internal vulnerability assessment, as well as annual external penetration testing. If a potential vulnerability is identified, it is triaged among the security, engineering, and technical operations teams. Okta's security team employs a risk ranking system for all technical vulnerabilities. The ranking system also accounts for all published risk rankings within the Okta environment. Critical- and high-risk issues are addressed as quickly as possible within the next release cycle or hot patch within the context of business feasibility. Medium-risk issues are addressed within the next four release cycles. Low-risk issues are addressed when possible with feature updates.
Protective monitoring type
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Protective monitoring approach
Okta utilizes a number of monitoring tools with centralized logging and SIEM using our own correlation rules for security monitoring, analysis, and alerting. Okta Support makes every possible effort to respond to support incidents in accordance with the time-frames defined in the Support Service Level Agreement (SLA).
Per the Agreement, initial response times and follow-up response times vary based on the Customer Success Package a customer has purchased and the Customer Support Ticket Severity / Priority Definition
Incident management type
Conforms to a recognised standard, for example, CSA CCM v3.0 or ISO/IEC 27035:2011 or SSAE-16 / ISAE 3402
Incident management approach
Okta has formally documented incident response & disaster recovery standard operating procedures (SOPs) that describe discovery, investigation, escalation, containment, notification, and documentation processes. Customers are provided this SOP document upon request and under NDA.

Secure development

Approach to secure software development best practice
Conforms to a recognised standard, but self-assessed

Public sector networks

Connection to public sector networks
No

Pricing

Price
£1.55 per user per month
Discount for educational organisations
Yes
Free trial available
Yes
Description of free trial
30 Day trial period in which you have full suite access for 10 users limited to 5 applications.
Link to free trial
https://www.okta.com/free-trial/

Service documents

Return to top ↑