- 19 May 2023
- 5 Minutes to read
- Print
- DarkLight
Appendix B Glossary
- Updated on 19 May 2023
- 5 Minutes to read
- Print
- DarkLight
A
Admin (role/permission/user). An Admin role on an Secure Edge Portal account gives the user access to operations involving administrative management of Secure Edge network elements, including adding, deleting, installing, creating). The Admin permission can be specified for types of operations instead of globally. |
Amazon Web Services (AWS). A cloud services platform from Amazon that can be used with Secure Edge software and web service. |
Application network. The network running behind your Virtual iNodes connecting your applications with the IIoT devices behind the Edge iNodes. |
APN. Access Point Name. An APN is a combined network ID and operator ID used in wireless networking to distinguish among connected IP networks (called APN networks). |
Azure. Microsoft Azure is a cloud services platform that can be used with the Secure Edge software and web service. |
C
Child organization. An account created in the Secure Edge Portal to manage a subset of users of a Secure Edge account. It represents a set of users, the child organization, with common management and administrative requirements, such as company subdivisions or locations. With child organizations, you can customize management for these groups of users. |
CIDR. Classless Inter-domain Routing. A network/device identifier. In the CIDR addressing system, the IP address includes notation to indicate the significant bits in the routing or networking portion. |
Command-line interface (CLI). |
CTD. Continuous threat detection |
Custom role. With Admin account permission on an Secure Edge Portal account, you can create custom roles (permission to perform specified types of operations) and assign them to account users. |
E
Edge iNode. A Secure Edge network element (physical hardware) located at the edge of a private network. See also Virtual iNode and Virtual Edge iNode. |
Edge service. See Service. |
H
Hybrid cloud. A cloud computing environment using a combination of two or more on-premise, private cloud, and public cloud services. You can use View Secure Edge in a hybrid cloud environment because the built-in Secure Edge firewall creates a secure perimeter around IoT devices and iNodes enable secure encrypted tunnels for data and communications. |
I
IIoT. Industrial IoT. Industrial Internet of Things. |
iNode. Secure Edge network elements used to connect to your applications and to your IIoT devices through the cloud. Specific types of iNodes are Edge iNodes, Virtual iNodes, and Virtual Edge iNodes. |
iNode at the edge. See Edge iNode or Virtual Edge iNode. |
iNode in the cloud. See Virtual iNode. |
iNode network. Network composed of Secure Edge network elements, providing secure converged infrastructure for IIoT. |
iNode operating system. Secure Edge software used to provide secure converged infrastructure for IIoT. As a managed OS, updates and security patches are automated without need for CLI input. |
iNode command-line interface (CLI). The command-line interface available for Secure Edge users to manage operations on Edge iNodes, including changing IP address and setting uplink interface. |
ioTium. The previous product name for the View Secure Edge. |
J
Jump host. An intermediary host or server used to access and manage devices in a separate security zone. |
L
Labels. Key-value pairs that can be added to Secure Edge objects to specify attributes used to manage them effectively. You specify labels when you add or edit an Secure Edge object, including iNodes, iNode networks, or security policies. |
N
Niagara 4. Niagara 4 is a predefined service in Secure Edge Portal. |
Northbound. The connections on the WAN side of the iNode where traffic flows outbound to the internet. |
O
Orchestrator (also ioTium Orchestrator). The previous product name for the Secure Edge Portal. |
Organization. On Secure Edge, organization represents the company using Secure Edge. |
Organization Admin (role/permission/user). With an Organization Admin role on an Secure Edge Portal account, a user can perform operations involving set up and management of child organizations for the account, including creating a child organization, adding a user and account for a child organization, and assigning hardware serial numbers to a child organization. |
OT-Net, OT-Edge, OT-Access. Secure Edge Operation Technology offerings. |
P
Portal. See Secure Edge Portal. |
Private cloud. When using Secure Edge software and web service, he private cloud is the cloud-based computing environment running the Secure Edge customer's business, test and development, and data analytics applications. Secure Edge Virtual iNodes connect your private cloud through Edge iNodes to your IIoT devices. |
Public cloud. A public cloud is computing environment in which services are offered by third-party providers over public internet. You can use the public cloud as part of Secure Edge because the built-in Secure Edge firewall creates a secure perimeter around IoT devices and iNodes enable secure encrypted tunnels for data and communications. |
R
Read Only (role/permission/user). With a Read Only role on an Secure Edge Portal account, a user can view Secure Edge Portal pages. Read Only permission can be specified for types of operations instead of globally. |
Representational network or subnet. When the CIDR of a local subnet behind an Edge iNode conflicts with a CIDR of another local subnet already connected to a remote iNode, then the conflicting Edge iNode is given a different CIDR, called a representational network, to distinguish it from the first. That CIDR must be added to the cloud routing table. |
Roles. In Secure Edge, user roles define the specific types of operations users are permitted to perform on Secure Edge. See also Admin role, Read Only role, Custom role, and Organization Admin. |
S
Secrets. In the context of Secure Edge services, secrets, also called service secrets, are the secure objects that store sensitive data needed by containers in the service. Examples of such objects are Secure Shell (SSH) keys, passwords, application license keys, and container image pull credentials. |
Secret volume. A volume is a directory containing data needed by all containers in a service. A secret volume is a secure object that stores sensitive data needed by application containers. (See also Secrets.) |
Secure Edge Portal. The web interface for administering your Secure Edge, typically customername.secureedge.view.com |
Secure Shell (SSH). Secure Shell is a protocol used for secure access to a computer over an unsecured network. Using an SSH client and the Secure Edge command-line interface, you ca n access Secure Edge network elements for debugging and some additional operations. |
Service. A representation of an application running on an Edge iNode. It contains application containers and shared networking and storage resources. |
SkySpark. The SkyFoundry SkySpark is a pre-defined service in Secure Edge Portal. |
Southbound. The connections on the LAN and TAN side of the iNode where traffic flows to local devices and networks. |
T
TAN. Thing Area Network, which is typically a small local network (LAN) that is used for IoT devices. You may have more than one in a building based on your network architecture. |
ThingWorx Edge. ThingWorx Edge is a pre-defined service in Secure Edge Portal. |
TPM. Trusted platform module. |
V
Virtual Edge iNode. In a VMware environment only, the Secure Edge network element that is a VMware instance located at the edge of your private network. |
Virtual iNode. The Secure Edge network element located in the cloud that connects to your application network. Virtual iNodes connect your applications through Edge iNodes to your IIoT devices. Sometimes called iNodes in the cloud. |
Virtual machine (VM). Confirm usage instead of Virtual iNode, outside of cloud hosting (VMware, Azure) context. |
VMware. A cloud hosting platform from VMware that can be used with Secure Edge software and web service. |