GETTING STARTED
Kore.ai XO Platform
Virtual Assistants Overview
Natural Language Processing (NLP)
Concepts and Terminology
Quick Start Guide
Accessing the Platform
Navigating the Kore.ai XO Platform
Building a Virtual Assistant
Help & Learning Resources
Release Notes
Current Version
Recent Updates
Previous Versions
Deprecations
Request a Feature
CONCEPTS
Design
Storyboard
Overview
FAQs
Conversation Designer
Overview
Dialog Tasks
Mock Scenes
Dialog Tasks
Overview
Navigate Dialog Tasks
Build Dialog Tasks
Node Types
Overview
Intent Node
Dialog Node
Dynamic Intent Node
GenAI Node
GenAI Prompt
Entity Node
Form Node
Confirmation Node
Message Nodes
Logic Node
Bot Action Node
Service Node
Webhook Node
Script Node
Process Node
Agent Transfer
Node Connections
Node Connections Setup
Sub-Intent Scoping
Entity Types
Entity Rules
User Prompts or Messages
Voice Call Properties
Knowledge AI
Introduction
Knowledge Graph
Introduction
Terminology
Build a Knowledge Graph
Manage FAQs
Knowledge Extraction
Import or Export Knowledge Graph
Prepare Data for Import
Importing Knowledge Graph
Exporting Knowledge Graph
Auto-Generate Knowledge Graph
Knowledge Graph Analysis
Answer from Documents
Alert Tasks
Small Talk
Digital Skills
Overview
Digital Forms
Digital Views
Introduction
Widgets
Panels
Session and Context Variables
Context Object
Intent Discovery
Train
NLP Optimization
ML Engine
Overview
Model Validation
FM Engine
KG Engine
Traits Engine
Ranking and Resolver
Training Validations
NLP Configurations
NLP Guidelines
LLM and Generative AI
Introduction
LLM Integration
Kore.ai XO GPT Module
Prompts & Requests Library
Co-Pilot Features
Dynamic Conversations Features
Intelligence
Introduction
Event Handlers
Contextual Memory
Contextual Intents
Interruption Management
Multi-intent Detection
Amending Entities
Default Conversations
Conversation Driven Dialog Builder
Sentinment Management
Tone Analysis
Default Standard Responses
Ignore Words & Field Memory
Test & Debug
Overview
Talk to Bot
Utterance Testing
Batch Testing
Conversation Testing
Conversation Testing Overview
Create a Test Suite
Test Editor
Test Case Assertion
Test Case Execution Summary
Glossary
Health and Monitoring
NLP Health
Flow Health
Integrations
Actions
Actions Overview
Asana
Configure
Templates
Azure OpenAI
Configure
Templates
BambooHR
Configure
Templates
Bitly
Configure
Templates
Confluence
Configure
Templates
DHL
Configure
Templates
Freshdesk
Configure
Templates
Freshservice
Configure
Templates
Google Maps
Configure
Templates
Here
Configure
Templates
HubSpot
Configure
Templates
JIRA
Configure
Templates
Microsoft Graph
Configure
Templates
Open AI
Configure
Templates
Salesforce
Configure
Templates
ServiceNow
Configure
Templates
Stripe
Configure
Templates
Shopify
Configure
Templates
Twilio
Configure
Templates
Zendesk
Configure
Templates
Agents
Agent Transfer Overview
Custom (BotKit)
Drift
Genesys
Intercom
NiceInContact
NiceInContact(User Hub)
Salesforce
ServiceNow
Configure Tokyo and Lower versions
Configure Utah and Higher versions
Unblu
External NLU Adapters
Overview
Dialogflow Engine
Test and Debug
Deploy
Channels
Publishing
Versioning
Analyze
Introduction
Dashboard Filters
Overview Dashboard
Conversations Dashboard
Users Dashboard
Performance Dashboard
Custom Dashboards
Introduction
Custom Meta Tags
Create Custom Dashboard
Create Custom Dashboard Filters
LLM and Generative AI Logs
NLP Insights
Task Execution Logs
Conversations History
Conversation Flows
Conversation Insights
Feedback Analytics
Usage Metrics
Containment Metrics
Universal Bots
Introduction
Universal Bot Definition
Universal Bot Creation
Training a Universal Bot
Universal Bot Customizations
Enabling Languages
Store
Manage Assistant
Team Collaboration
Plan & Usage
Overview
Usage Plans
Templates
Support Plans
Invoices
Authorization
Conversation Sessions
Multilingual Virtual Assistants
Get Started
Supported Components & Features
Manage Languages
Manage Translation Services
Multiingual Virtual Assistant Behavior
Feedback Survey
Masking PII Details
Variables
Collections
IVR Settings
General Settings
Assistant Management
Manage Namespace
Data
Overview
Data Table
Table Views
App Definitions
Data as Service
HOW TOs
Build a Travel Planning Assistant
Travel Assistant Overview
Create a Travel Virtual Assistant
Design Conversation Skills
Create an ‘Update Booking’ Task
Create a Change Flight Task
Build a Knowledge Graph
Schedule a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Train the Assistant
Use Traits
Use Patterns
Manage Context Switching
Deploy the Assistant
Use Bot Functions
Use Content Variables
Use Global Variables
Use Web SDK
Build a Banking Assistant
Design Conversation Skills
Create a Sample Banking Assistant
Create a Transfer Funds Task
Create a Update Balance Task
Create a Knowledge Graph
Set Up a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Add Data to Data Tables
Update Data in Data Tables
Add Data from Digital Forms
Train the Assistant
Composite Entities
Use Traits
Use Patterns for Intents & Entities
Manage Context Switching
Deploy the Assistant
Configure an Agent Transfer
Use Assistant Functions
Use Content Variables
Use Global Variables
Intent Scoping using Group Node
Analyze the Assistant
Create a Custom Dashboard
Use Custom Meta Tags in Filters
Migrate External Bots
Google Dialogflow Bot
APIs & SDKs
API Reference
API Introduction
Rate Limits
API List
koreUtil Libraries
SDK Reference
SDK Introduction
SDK Security
SDK Registration
Web Socket Connect and RTM
Installing the BotKit SDK
Using the BotKit SDK
SDK Events
SDK Functions
SDK Tutorials
BotKit - Blue Prism
BotKit - Flight Search Sample VA
BotKit - Agent Transfer
Widget SDK Tutorial
Web SDK Tutorial
ADMINISTRATION
Introduction to Admin Console
Administration Dashboard
User Management
Add Users
Manage Groups
Manage Roles
Data Tables and Views
Assistant Management
Enrollment
Invite Users
Send Bulk Invites
Import User Data
Synchronize Users from AD
Security & Control
Using Single-Sign On (SSO)
Two-Factor Authentication (2FA)
Security Settings
Cloud Connector
Analytics
Billing
  1. Home
  2. Docs
  3. Virtual Assistants
  4. Bot Administration
  5. Security & Compliance
  6. Security Settings

Security Settings

Apart from the sign-on, and other security settings (see here for details), you can modify the following default security & control settings for your account:

  • Data retention period
  • Context persistence
  • IP address restriction

Data Retention

The end-user interaction data from Standard accounts/workspaces is removed as per Kore.ai’s retention policy. It is usually 7 years and can be revised at periodic intervals.

The end-user interaction data for Enterprise accounts is retained for 7 years. Enterprises can customize the retention period to suit their policies using the Data Retention Period option.

Steps:

  1. Go to Security & Control -> Settings.
  2. Under Data Retention Period, you have two options:
    • Use the default retention period – 7 years.
    • Use the custom data retention period and set the duration between 1 month to 7 years.

The following data would no longer be available post the data retention period:

  • Conversation History / Messages
  • Usage Information
  • Task Execution and Performance Metrics
  • Session and Message Tags
  • Alert Instances
  • Debug Logs

Note: The custom data retention period cannot be set if your account has a large volume of messages. In such a case, you are requested to reach out to Kore.ai Support for setting Custom Retention Period.

Context Persistence

By default, the XO Platform stores the context of the end-users’ conversations with the assistant. This context information can be used for debugging and analysis purposes.

However, you might not want the Platform to store this information due to the presence of sensitive data about customers or other security-related reasons. You can opt not to store the same using the Context Persistence option.

Steps:

  1. Go to Security & Control -> Settings.
  2. Under Context Persistence, you have two options:
    1. Store end users’ conversation context information and allow authorized developers to view this information – this is the default setting.
    2. Do not store end users’ conversation context information – this will ensure that:
      • the Platform does not store the context information
      • Option to view context information in the XO Platform, like Metrics and any other places, is disabled.

IP Address Restriction

By default, users can access the XO Platform, and the Admin Console from any IP address as long as they have valid credentials.

You can, additionally, restrict the access from a specified range of IP addresses. This restriction applies to developers from your account alone, i.e if a developer belongs to another account also their access to the Platform using that account will not be restricted.

Steps:

  1. Go to Security & Control -> Settings.
  2. Under IP Address Restriction, you have two options:
    1. No restriction – this is the default setting and access is not restricted to any IP address.
    2. Restrict – Here you can specify a range of IP Addresses to which the access is restricted. All other addresses would be blocked from accessing the XO Platform and the Admin Console Platform.
      Note: The IP Address of your (current) system should be part of the allowed IP Addresses list.

Security Settings

Apart from the sign-on, and other security settings (see here for details), you can modify the following default security & control settings for your account:

  • Data retention period
  • Context persistence
  • IP address restriction

Data Retention

The end-user interaction data from Standard accounts/workspaces is removed as per Kore.ai’s retention policy. It is usually 7 years and can be revised at periodic intervals.

The end-user interaction data for Enterprise accounts is retained for 7 years. Enterprises can customize the retention period to suit their policies using the Data Retention Period option.

Steps:

  1. Go to Security & Control -> Settings.
  2. Under Data Retention Period, you have two options:
    • Use the default retention period – 7 years.
    • Use the custom data retention period and set the duration between 1 month to 7 years.

The following data would no longer be available post the data retention period:

  • Conversation History / Messages
  • Usage Information
  • Task Execution and Performance Metrics
  • Session and Message Tags
  • Alert Instances
  • Debug Logs

Note: The custom data retention period cannot be set if your account has a large volume of messages. In such a case, you are requested to reach out to Kore.ai Support for setting Custom Retention Period.

Context Persistence

By default, the XO Platform stores the context of the end-users’ conversations with the assistant. This context information can be used for debugging and analysis purposes.

However, you might not want the Platform to store this information due to the presence of sensitive data about customers or other security-related reasons. You can opt not to store the same using the Context Persistence option.

Steps:

  1. Go to Security & Control -> Settings.
  2. Under Context Persistence, you have two options:
    1. Store end users’ conversation context information and allow authorized developers to view this information – this is the default setting.
    2. Do not store end users’ conversation context information – this will ensure that:
      • the Platform does not store the context information
      • Option to view context information in the XO Platform, like Metrics and any other places, is disabled.

IP Address Restriction

By default, users can access the XO Platform, and the Admin Console from any IP address as long as they have valid credentials.

You can, additionally, restrict the access from a specified range of IP addresses. This restriction applies to developers from your account alone, i.e if a developer belongs to another account also their access to the Platform using that account will not be restricted.

Steps:

  1. Go to Security & Control -> Settings.
  2. Under IP Address Restriction, you have two options:
    1. No restriction – this is the default setting and access is not restricted to any IP address.
    2. Restrict – Here you can specify a range of IP Addresses to which the access is restricted. All other addresses would be blocked from accessing the XO Platform and the Admin Console Platform.
      Note: The IP Address of your (current) system should be part of the allowed IP Addresses list.

Menu