|
<< Click to Display Table of Contents >> Raynet One > 2026.4 > User Guide Glossary: Decoding Raynet One terminology |
While exploring your IT landscape with the help of Raynet One you might face some direction signs which you do not understand at first glance. In consequence, this glossary serves as a navigation system helping you to see the signs (and also know what they mean). The glossary will be extended over time.
What is it called? |
What does it mean and what is it used for in Raynet One? |
ACL (Access Control List) |
An Access Control List (ACL) in Raynet One is a permission configuration attached to a resource group that explicitly defines which users can view, edit, or delete the assets within that group. When an ACL is applied via a resource group, it restricts asset visibility and permitted actions to users with explicitly granted permissions, replacing the default open-access behavior.
Purpose: Restricting access to grouped assets to authorized users only, enabling fine-grained control over asset visibility and user actions across the platform Reference chapters: Resource groups, Understanding Raynet One Permissions
|
Action Center |
The Action Center is a notification hub in Raynet One accessible via the bell icon in the header. It provides users with an overview of platform events that require user intervention, such as failed discovery or inventory jobs, and enables direct response and batch processing of errors and notifications.
Purpose: Notifying users of required platform interventions and enabling direct management of failure notifications and error resolution within the platform Reference chapters: Action center, Asset Management
|
Active Directory (AD) |
Active Directory (AD) is a directory service developed by Microsoft for Windows domain networks. It’s included in the Windows Server operating systems as a set of processes and services. AD provides centralized authentication and authorization for users and computers within a network, allowing for the enforcement of security policies and the installation or updating of software. Active Directory uses protocols like Lightweight Directory Access Protocol (LDAP) and Kerberos, as well as DNS, to function. Azure AD is the cloud-synchronized variant of it which is able to globally connect local ADs.
Purpose: Discovery scans with Active Directory option activated Reference chapters: Start a discovery run in Active Directory
|
Agreement |
An Agreement in Raynet One is a license agreement document, such as a maintenance renewal or supplemental terms, that is linked to one or more purchases in the License Management workspace. It extends the commercial source of a purchase without replacing it.
Purpose: Tracking additional license documents that relate to existing purchases, so multi-year terms and renewals are represented correctly Reference chapters: Purchases, Agreements
|
AI Chat |
AI Chat is a secure, conversational interface in Raynet One that enables users to access and analyze system and inventory data using natural language. Users can ask questions and receive structured, contextualized results without navigating through multiple views or reports. All operations are executed within the user's role and permission scope, respecting existing access controls and audit requirements.
Purpose: Providing natural-language access to platform data and inventory insights, enabling users to query and analyze information quickly without manual navigation through multiple platform views Reference chapters: AI Chat
|
Average version sprawl |
“Version sprawl” refers to a situation where multiple versions of software applications or components are being used or maintained within an environment. This can lead to increased complexity and challenges in managing the software effectively. It’s similar to “software sprawl”, which occurs when the number of applications or software components within an environment rapidly grow and change, causing traditional software management methods to fail. This often happens in a distributed software architecture where pace and independent development lead to a proliferation of microservices or software versions.
Purpose: Average version sprawl is displayed in the IT Visibility Dashboard Reference chapters: IT Visibility
|
API (Application Programming Interface) |
An API (Application Programming Interface), is a set of rules or protocols that allows software applications to communicate with each other. It enables the exchange of data, features, and functionality between different software systems. API's play a crucial role in modern software development. This is because they allow developers to integrate and leverage functionalities from external services or applications rather than building those functionalities from scratch. API's are used in various contexts, such as web services, operating systems, and hardware interfaces. They are essential for creating scalable and flexible software ecosystems.
Purpose: Relevant values in the context of adding new connections Reference chapters: Connections
|
Automation |
The automation of inventory and discovery tasks simplifies platform routines as it is possible to flexibly schedule time frames when runs shall be triggered. There is also an Automation tab with two views (simple and expert mode) available under Devices. In a nutshell, the automation of platform tasks can fully or partially substitute manually triggered runs, depending on your requirements.
Purpose: Creating a stable inventory and discovery routine via scheduled runs Reference chapters: Devices, Schedule your discovery and inventory jobs
|
Codex |
Codex is a licensing knowledge service, accessed through SAM Cloud, that provides the licensing rules applied during compliance and demand calculations in Raynet One. It determines how software products are measured and licensed, how entitlements are applied to discovered installations, and how version relationships such as downgrade and upgrade rights are evaluated.
Purpose: Providing product-specific licensing rules for automated demand calculation, compliance evaluation, and ELP analysis within the License Management workspace Reference chapters: License compliance calculation, Start your License Management journey
|
Compliance |
In Raynet One, Compliance refers to the product-level result of comparing effective license entitlements against calculated software demand. The Compliance section in the License Management workspace displays whether a product is compliant, over-licensed, or under-licensed, and provides the balance value and financial impact for each managed product.
Purpose: Evaluating whether an organization's license entitlements cover the software installations detected in the managed environment, enabling proactive risk management and license cost optimization Reference chapters: Compliance, License Management
|
CPU |
A CPU, or Central Processing Unit, is the primary component of a computer that processes instructions. It is often referred to as the “brain” of the computer because it executes the operating system and application programs, constantly receiving input from the user or active software programs. The CPU processes data and produces output, which may be stored by an application or displayed on the screen.
Purpose: Parameter in data normalization and enrichment which is relevant for displaying hardware details Reference chapters: Devices
|
Credentials |
User credentials are a set of unique identifiers that enable a user to verify their identity in order to log in to an online account or access a network, application, or web-based platform. They are essential for maintaining security and ensuring that only authorized users can access sensitive information or perform certain actions. Depending on the digital target product, user credentials can include user names, passwords or pass keys, certificates and tokens.
Purpose: Accessing Raynet One configuring runners and starting inventory or discovery runs Reference chapters: Credentials, Add credentials
|
CVE (score and ID) |
A CVE (Common Vulnerabilities and Exposures) is a list of publicly disclosed computer security flaws. When someone refers to a CVE, they are talking about a security flaw that has been assigned a unique CVE ID number. These IDs help IT professionals coordinate their efforts to prioritize and address vulnerabilities to make computer systems more secure. A CVE score, often referred to in the context of the Common Vulnerability Scoring System (CVSS), is a numerical indicator that reflects the severity of a given vulnerability in computer systems. The score is used to prioritize the response and resources based on the threat level of the vulnerability. The CVSS assigns severity scores on a scale from 0 to 10, with 10 being the most severe.
Purpose: Estimating the security status of your IT landscape and assets in order to prevent data damage, security leaks and technical debt Reference chapters: IT Visibility, Vulnerabilities
|
CWE name |
A CWE name refers to an entry in the Common Weakness Enumeration (CWE), which is a list of common software and hardware vulnerability types. This list categorizes security vulnerabilities and provides a standardized language for describing them. Each vulnerability in the CWE list is assigned a unique ID and description, making it easier for developers, security analysts, and IT professionals to identify, discuss, and address these weaknesses. The CWE aims to help organizations prevent and eliminate typical security vulnerabilities in their systems.
Purpose: Helping Raynet One users understand and eliminate vulnerabilities in their IT landscape by providing more detailed vulnerability information Reference chapters: Vulnerabilities, IT Visibility
|
CycloneDX |
CycloneDX is an industry-standard, machine-readable specification for describing software components and their relationships. In Raynet One, SBOM data collected during Docker container inventory scans is captured in CycloneDX JSON format, enabling structured and interoperable representation of container software components.
Purpose: Providing a standardized format for SBOM data collected during Docker container inventory scans, ensuring compatibility with external security and compliance tooling Reference chapters: Docker Container SBOM Scan, Devices
|
Data consistency index (DCI) |
In the context of IT and data management, a Data Consistency Index refers to the measure of uniformity and accuracy of data across a system. Consistent data is crucial because it ensures that all users see the same data values at any given time, regardless of where the data is stored or how it is accessed. To maintain data consistency, IT systems implement various mechanisms such as locking, transaction logs, and replication protocols. These mechanisms help prevent issues like data races, where multiple operations try to modify the same data concurrently, leading to inconsistent states.
Purpose: Data normalization and standardized data display in Raynet One regarding your managed environment Reference chapters: IT Visibility
|
Data collection |
Data collection refers to the systematic approach to gathering and measuring information from various sources to get a complete and accurate picture of an area of interest. It’s a critical component of data analysis, which turns raw data into valuable insights for strategic decision-making. Generally, this field is divided into automated, first-party, second-party and third-party data collection. In a nutshell, data collection is about ensuring that all existent data is relevant, accurate, and can be trusted for analysis. In Raynet One data collection is done automatically by the platform.
Purpose: Core functionality being relevant while discovering and inventorying your managed environment to get the big picture Reference chapters: About Raynet One, Discover your IT landscape, Inventory your IT assets
|
Data enrichment |
Data enrichment is the process of enhancing existing data by incorporating additional information from various sources to provide more context, accuracy, and insights. Practically, in the course of data enrichment. data sources are combined, insights are unlocked and data quality is improved by identifying and filling information gaps. In Raynet One data enrichment is done both by the platform and via additional manual data entries.
Purpose: Core functionality of Raynet One, e.g. applied in enriched data views and in the Details view Reference chapters: Software, Hardware, Details view
|
Data Hub |
The Data Hub is a Raynet product that stores and processes external enterprise data. When integrated with Raynet One, it enables the AI Chat feature to retrieve supported external data — such as Microsoft 365 or ServiceNow data — in response to user queries. The integration is configured through the Integrations section in Raynet One.
Purpose: Extending the capabilities of AI Chat in Raynet One by providing access to supported external enterprise data stored and processed in the Data Hub platform Reference chapters: Data Hub Connection, Connections
|
Data normalization |
Data normalization is the process of organizing data in a database to reduce redundancy and improve data integrity. The primary goal of data normalization is to divide large tables into smaller, more manageable pieces with minimal redundancy. The process involves applying a series of rules, or normal forms, to a database to ensure that it is structured correctly. In Raynet One, data normalization is done automatically by the platform.
Purpose: Core functionality of Raynet One, e.g. viewable in all list views and in the Details view Reference chapters: About Raynet One, Discover your IT landscape, Inventory your IT assets
|
Demand |
In the License Management workspace of Raynet One, Demand is the calculated quantity of software licenses required based on discovered software installations and applicable licensing rules. It is derived from inventory data and represents the total usage that must be covered by valid entitlements for a product to be considered compliant.
Purpose: Quantifying the number of licenses needed based on actual software installations in the managed environment, forming the usage side of the compliance calculation alongside entitlements Reference chapters: License compliance calculation, Compliance
|
Discovery |
During discovery, the runner collects data, compares and measures data sources. Then it automatically organizes found raw data in smaller, manageable units in order to eliminate redundancies and ensures data quality. Then, the data in the underlying database is restructured according to standardized rules and forms. In a nutshell, discovery serves to create a liable and functioning, complete and reliable data basis for inventory jobs.
Purpose: Assembling, structuring and optimizing raw data for inventory Reference chapters: Discover your IT landscape, Discovery Settings, Networks, Databases, Devices
|
Docker |
Docker is a virtual online platform and tool for building, distributing, and running Docker containers. It serves to package applications with their dependencies and environments into a container, which can then be run on any Linux server or Windows server that supports Docker. These containers are isolated from each other and the host system, but they share the same operating system kernel. All in all, Docker is popular among developers for its efficiency, portability, environment consistency, scalability and version control.
Purpose: Docker-compatible environment as a prerequisite for using Raynet One Reference chapters: OS prerequisites and requirements, Runners
|
Downgrade Rights |
Downgrade Rights is a mechanism in Raynet One's License Management that allows entitlements for a newer version of a product to cover the demand for older versions within the same product family. When a newer-version entitlement has a surplus and an older version has a deficit, the platform automatically transfers the available quantity to satisfy the older version's demand, provided the license model and metric match.
Purpose: Automatically applying entitlement surpluses from newer product versions to cover compliance deficits in older versions of the same product family during compliance calculations Reference chapters: Downgrade and upgrade rights, Compliance
|
Dynamic Inventory |
Dynamic Inventory is a feature in Raynet One that automatically targets devices for inventory collection based on how recently their last inventory was performed, or whether a device has ever been inventoried. It acts as a filter across all devices to identify those that need to be inventoried, helping maintain an up-to-date view of the IT landscape.
Purpose: Ensuring that all devices in the managed environment receive regular inventory collection, complementing manually triggered and newly enrolled device inventory jobs Reference chapters: Dynamic inventory, Devices
|
ELP (Effective License Position) |
The Effective License Position (ELP) is the calculated balance between available license entitlements and the demand for those licenses as determined by Raynet One's License Management. A negative ELP indicates under-licensing. A zero ELP, or a positive ELP up to the configured compliance threshold, indicates a compliant state. A positive ELP above the compliance threshold indicates over-licensing. It is the primary output of the compliance calculation and provides the foundation for license optimization recommendations.
Purpose: Providing a clear, quantified view of the license compliance status for each managed product, enabling organizations to identify compliance risks and cost optimization opportunities Reference chapters: Compliance, License compliance calculation
|
End of Life (EoL) |
Attribute of products which were available for acquisition through the global market but are not anymore. They may still receive support through community efforts or the publishing parties.
Purpose: Marking products which have turned deprecated or are in a conflicting state. Eventually, they turn into candidates for replacement. Reference chapters: About Raynet One, Vulnerabilities
|
End of Support (EoS) |
Attribute of products which are not available for purchase and they are not supported by the publishing parties anymore. Development on the product has ceased. If there are known security vulnerabilities, they will likely remain in the product forever, not being security patched. Commonly, old products which have reached end of support are a security threat to businesses.
Purpose: Marking products which should not be used by professional businesses anymore. Reference chapters: About Raynet One, Vulnerabilities
|
Enrollment token |
An enrollment token is typically used in the context of IT and software systems for the purpose of registering or adding new devices or users to a management system. Basically, it acts as a unique identifier that allows a device or user to be associated with a specific service or network. When setting up a new device or user account, the enrollment token is entered to authenticate the enrollment process. This ensures that only authorized devices or users are added to the system.
Purpose: Authentication during Windows runner installation, for Non-Windows users: automatically included in Docker file template Reference chapters: Add a Windows runner via Runners
|
Entitlement |
An Entitlement in Raynet One is the operational record of purchased license rights for a specific product. It defines the product, license model, license metric, quantity, and validity period used for allocation, compliance calculation, and ELP analysis. Entitlements are typically generated from purchases but can also be created manually.
Purpose: Providing the structured, machine-readable representation of license rights that drives automated reconciliation, ELP calculation, and compliance reporting in the License Management workspace Reference chapters: Entitlements, Purchases
|
License compliance calculation |
License compliance calculation is the system-guided process in Raynet One that connects purchases, entitlement records, discovered software usage, demand calculation, compliance evaluation, and Effective License Position (ELP) results into a unified workflow. It ensures that license rights derived from purchases are accurately applied to calculated software demand so that compliance status and ELP results are reliable.
Purpose: Structuring the end-to-end License Management workflow from purchase capture through entitlement derivation, demand calculation, and compliance reporting to ensure consistent and accurate license position results Reference chapters: License compliance calculation, License Management
|
GPU |
A GPU, or Graphics Processing Unit, is a specialized electronic circuit designed to rapidly manipulate and alter memory to accelerate the creation of images in a frame buffer intended for output to a display device1. Originally, GPUs were used primarily for rendering graphics in video games, but their capabilities have expanded significantly. So, GPUs have become essential in fields that require heavy computational power and are a cornerstone of modern computing for both personal and professional use.
Purpose: Parameter in data normalization and enrichment which is relevant for displaying hardware details Reference chapters: Devices
|
Hypervisor |
A hypervisor, also known as a Virtual Machine Monitor (VMM), is software that allows multiple operating systems to run concurrently on a single physical host computer. Generally, The hypervisor creates a virtual environment that abstracts the physical resources of the host computer, such as CPU, memory, and storage, and allocates them to virtual machines (VM's). Thereby, each VM is isolated from the host system and other VM's. There are two basic types of hypervisors, "Bare Metal" and "Hosted".
Purpose: Detection and inspection of virtual environments and devices during discovery and inventory runs and in the Details view Reference chapters: Asset Management
|
Instrument |
Generally, in an IT context, an instrument refers to the tools and techniques used to monitor, measure, and analyze the performance of a software product. This can include adding code to a program to track its behavior during execution, such as logging events, measuring operation durations, or diagnosing errors. Instrumentation is essential for understanding how software performs in real-world scenarios and can help developers optimize and debug their applications effectively.
Purpose: Scanning instruments ensuring correct data collection, normalization and enrichment during discovery and inventory, while skipped instruments are hints for errors detected during platform operations
Reference chapters: Keep track of plugins, Understand job details, Take action on your jobs in the Action center, Devices
|
Inventory |
Inventory usually follows discovery. This means that collected and restructured data serves as a basis for further transformation, enrichment and reporting. In fact, this is what the runner does after discovery and during inventory. Through complete or targeted inventory runs, it is possible to get an overview on your managed environment, but also can inspect details on all individual IT assets.
Purpose: Enabling the user to access available IT assets in a managed environment and to take a deep-dive into asset details Reference chapters: Asset Management, Inventory your IT assets, Inventory Settings
|
Inventory script
|
In IT, an inventory script is a tool used to manage and track resources in a dynamic environment. It’s often used in configuration management and automation tools. This script can enforce dynamic solutions, retrieve data from multiple sources (e.g. API, LDAP and DMDB) and create connections with dynamic inventory sources.
Purpose: Triggering and processing customized inventory jobs based on your requirements Reference chapters: Inventory Scripts, Add an inventory script
|
IP range definition |
An IP range, short for Internet Protocol range, refers to a set of consecutive IP addresses grouped together based on specific criteria. It allows for the identification and communication of devices within a certain network. Each IP address consists of four numbers separated by periods, such as 192.168.0.1. By defining IP ranges, network administrators can efficiently organize and control access to their networks, making it easier to manage devices and apply security measures. For example, an IP range could encompass all IP addresses between 192.168.0.1 and 192.168.0.255, allowing for the grouping and management of devices within that range.
Purpose: Optional function in Raynet One which simplifies the automated discovery and inventory of targeted device groups within your managed environment Reference chapters: Discover your IT landscape, Inventory your IT assets, Become a troubleshooter, Control your credentials
|
IT assets |
Generally, IT assets encompass a wide range of items, including hardware, software, databases, networks and cloud services. They contribute to an IT landscape's life cycle management, strategic value and ITAM processes. Besides, ITAM is part of IT service management (ITSM) and is often guided by frameworks such as ITIL (Information Technology Infrastructure Library) and standardized by ISO/IEC 19770.
Purpose: Ensuring that both physical and logical assets in a defined environment are managed and monitored through their entire life cycle Reference chapters: Asset Management
|
IT landscape |
An IT landscape refers to the entirety of interconnected application systems within a company. It includes all components necessary to support IT services and processes, e. g. application architecture, data and information architecture, technology and security architecture. It is an essential part of the enterprise architecture and plays a crucial role in the digitalization and automation of business processes.
Purpose: Representing the technological framework and thus changing or determining business processes Reference chapters: About Raynet One
|
Job Graph |
The Job Graph is a visual component in Raynet One that displays the operations performed during a platform job in detail, differentiating between successful and failed operations and showing the live execution path. It is designed to promote operational transparency and helps users trace job execution, diagnose failures, and build confidence in platform workflows.
Purpose: Providing a detailed, visual representation of job execution for troubleshooting and operational transparency, enabling users to identify errors and understand the impact of inventory and discovery jobs Reference chapters: Working with the Job Graph, Asset Management
|
Keycloak |
Keycloak is the user authentication software used by Raynet One to manage identity and access. It supports multiple authentication providers including Google, Microsoft, and GitHub, and manages secure session tokens using JWT bearer authentication over TLS. Platform administrators can configure roles and user groups through the Keycloak administration console.
Purpose: Providing identity management, authentication, and session management for all users accessing the Raynet One platform, supporting role-based access and integration with external identity providers Reference chapters: Keycloak, Users
|
License Metric |
A License Metric in Raynet One defines how license usage is measured for a specific product — for example on a per-core, per-device, or per-user basis. Together with the License Model, it determines how entitlement quantities are formed and compared against calculated demand during compliance calculations. An incorrect metric assignment can affect allocation, ELP results, and compliance evaluations. The metric Custom is used for licensing terms that cannot be calculated automatically yet; its demand and compliance values are maintained manually.
Purpose: Defining the unit of measurement for license consumption and entitlement quantities, which is critical for accurate demand calculation and compliance reporting in the License Management workspace Reference chapters: Entitlements, Compliance
|
License Model |
A License Model in Raynet One defines the type or structure of a software license — such as Perpetual, Subscription, or Maintenance. It is assigned to an entitlement and determines how the license rights are processed, allocated, and compared against demand during compliance calculations. Together with the License Metric, it forms the identity of an entitlement and influences downstream processing.
Purpose: Classifying license types to ensure that entitlements are processed, linked, and compared with demand in the correct way during compliance and ELP calculations in the License Management workspace Reference chapters: Entitlements, Compliance
|
Managed environment |
In the context of Raynet One, a managed environment sets the framework for all operations processed and administered on the platform. Generally in IT context, a managed environment enables to securely manage a defined IT environment on a high quality level while minimizing unnecessary administration efforts.
Purpose: Detection and inspection of virtual environments and devices during discovery and inventory runs and in the Details view Reference chapters: Asset Management
|
Manual Override |
Manual Override is a setting in Raynet One's License Management that allows users to manually define the downgrade and upgrade adjustment values for a compliance record, bypassing the platform's automated calculation. When Manual Override is enabled, all adjustment values must be maintained manually. It should be used only when automatic calculation or version relationship handling cannot be applied reliably.
Purpose: Allowing manual adjustment of compliance calculation inputs in cases where automated demand and version relationship logic does not produce the correct result for a specific product or licensing scenario Reference chapters: License compliance calculation, Compliance
|
Oracle |
Oracle databases are powerful relational database management systems (RDBMS) that provide a robust and scalable platform for storing and managing data. They are popular for being versatile and inclusive when it comes to functionality. Oracle plugins, particularly for Oracle APEX (Application Express), enhance the functionality of Oracle databases by adding custom features or improving existing ones. All in all, Oracle databases and plugins together offer a comprehensive ecosystem for developing, deploying, and managing data-driven applications.
Purpose: Oracle databases as a target for inventory and discovery, pre-installed Oracle plugins Reference chapters: Databases, Plugins, Inventory Settings, Discovery Settings
|
Organization unit |
Normally, an organization unit (OU) serves as a logical administrative grouping container for various AD objects. These objects can include other containers, groups, users, and computer accounts. OUs are then organized into a hierarchy that reflects either the functional (business structure) or physical divisions within an organization.
Purpose: Assigning assets and jobs to different device or user groups, which might be a familiar concept for users of other Raynet products Reference chapters: Organization units, Credentials, Discover your IT landscape, Inventory your IT assets, Structure your IT landscape
|
Permission Context |
The Permission Context in Raynet One is a computed model that defines the exact permissions a user has over all available entities in the system. It is determined exclusively by the Access Control Lists (ACLs) assigned to the user's groups and reflects which entities a user can see and what actions — such as View, Edit, or Delete — they are permitted to perform.
Purpose: Providing a clear, computed view of user access rights derived from ACL assignments, enabling consistent and auditable enforcement of access control across all platform entities Reference chapters: Understanding Raynet One Permissions, Resource groups
|
Public Key Infrastructure (PKI) |
This is the link between cryptographical technologies with proven strong secrecy and the trust into network identities. Cryptographical certificates are created using a combination of genuine identity details (company name, machine hostname) and mathematical values (random secret numbers, difficult problems of calculation). The certificates are divided into use for either connection or signing. The Public Key Infrastructure is a hierarchy of signing certificates, each higher certificate providing trust for subsequent lower ones. Encrypted connections are deemed insecure if the associated certificate is not trusted or invalid.
Install the necessary root certificates on connecting machines to enable secure connections.
Purpose: Providing network connection security Reference chapters: OS prerequisites and requirements, Import devices from MECM, Start a discovery run in Active Directory
|
Plugin |
A plugin, sometimes called plugin, is a software extension component that enhances the capabilities of an existing application. It allows users to customize and optimize programs according to their specific needs and preferences. Generally, it is a tool that attaches to a program and provides extra features and abilities without altering the application’s core code. Plugins allow users to add different functionality to their software by enhancing performance, providing specialized tools and enhancing security and privacy.
Purpose: Automatically installed plugins supporting the platform's functionality during inventory and discovery runs and all other jobs so users save time and effort Reference chapters: Plugins , Keep track of plugins
|
Port probing
|
Port probing is a technique used to identify open ports on a networked computer or server. In general, ports are the docking points for the flow of information from a program or the internet to a device or another computer in the network and vice versa. Port numbers, ranging from 0 to 65,536, are used for consistency in programming and by internet service providers to fulfill requests. In essence, port probing is a diagnostic tool to help maintain the security and integrity of a network by identifying open ports that could potentially allow unauthorized access.
Purpose: Configuration of discovery settings in order to securely access relevant devices Reference chapters: Inventory Settings, Discovery Settings
|
Purchase |
A Purchase in Raynet One is the digital record of a commercial software purchase — such as an invoice, quote, or purchase order — captured in the License Management workspace. It serves as the commercial source from which entitlements are derived. Accurate purchase data is essential for reliable automated reconciliation, ELP calculation, and compliance reporting.
Purpose: Centralizing the capture and management of all software purchases, providing the commercial foundation from which entitlements, lifecycle events, and compliance data are generated Reference chapters: Purchases, License Management
|
Raynée |
Raynée is the AI assistant in Raynet One, presented as the user-facing identity for the AI Chat feature. It provides a conversational interface that allows users to ask questions about their IT landscape and license data in natural language, receiving structured answers based on the platform's inventory and system data. Raynée operates strictly within the user's role and permission scope.
Purpose: Providing users with an accessible, AI-powered conversational interface for interacting with Raynet One's data, reducing the need to navigate complex platform views or run manual queries Reference chapters: AI Chat, Data Hub Connection
|
Resource Group |
A Resource Group in Raynet One is a hierarchical grouping of assets such as credentials, runners, devices, networks, and databases, organized in a parent-child tree structure. Resource groups are used to apply Access Control Lists (ACLs) that restrict access to the grouped assets, allowing organizations to control asset visibility and permitted actions for specific users.
Purpose: Organizing platform assets into hierarchical groups for access control and management purposes, enabling fine-grained permission assignments through ACLs at the group level Reference chapters: Resource groups, Understanding Raynet One Permissions
|
RVIA Data Service |
The RVIA Data Service is an optional component in Raynet One that can be enabled for deployed runners to support legacy inventory data from RayVentory Inventory Agent (RVIA) clients. It converts the RVIA inventory format into modern device inventory objects compatible with Raynet One, providing HTTP upload and download endpoints for inventory file transfer.
Purpose: Enabling legacy RVIA inventory data to be ingested and processed by Raynet One, extending IT visibility to environments that still use the legacy RayVentory Inventory Agent Reference chapters: RVIA Data Service, Runners
|
RegEx definition |
A regular expression, often abbreviated as regex or regexp, is a string that describes a set of strings according to certain syntactic rules. In theoretical computer science, regular expressions are used to describe regular languages, which are the simplest class of languages in the Chomsky hierarchy and are generated by regular grammars. Regular expressions are implemented in many programming languages and are commonly used in text editors for “search and replace” functions. They enable pattern matching, where text is matched against the pattern of the regular expression to find, for example, all words that start and end with a specific letter without having to specify the intervening letters or their number. Regular expressions are formatted in a specific grammar, for example Perl or .NET (used by Raynet One).
Purpose: Optional function in Raynet One which simplifies and standardizes the automated search for data during inventory and discovery runs, provides powerful name-based filtering for extra granularity Reference chapters: Discover your IT landscape, Inventory your IT assets, Become a troubleshooter, Control your credentials
|
Runner |
Runners are mandatory instruments to discover and inventory your IT assets and landscape. They serve to find new devices in the managed environment (discovery run) and to explore data content and structures within selected devices (inventory run). In the SaaS platform setting, they help automating the collection, normalization, enrichment and display of data within your managed environment. For users of other Raynet products, they fulfill a similar function as agents do in local, isolated or device-based environments.
Purpose: Core instrument of Raynet One, executing and coordinating inventory and discovery runs Reference chapters: Runners, Add a new runner
|
SAM AI |
SAM AI is the AI-powered document intelligence in License Management. It is delivered through the SAM Cloud integration, mainly by the Contract Analyzer, and extracts structured purchase and agreement data from uploaded documents. For details, see SAM Cloud Connection.
Purpose: Automating the extraction of structured purchase information from documents, reducing manual data entry and improving the accuracy of purchase and entitlement data in the License Management workspace Reference chapters: Purchases, License compliance calculation
|
SAM Cloud |
SAM Cloud is a service provided and operated by Raynet for License Management and is connected to Raynet One through a connection in the Connections area. Its components are the Contract Analyzer, which parses purchases, agreements and related documents and extracts structured license information used for purchase capture and entitlement generation, the generation of rule expressions for calculation rules, and the communication with Codex.
Purpose: Enhancing the quality and speed of purchase processing and calculation rules in Raynet One by providing AI-powered document parsing, rule expression generation and access to Codex for License Management workflows Reference chapters: SAM Cloud Connection, Connection Type Overview, License Management
|
SBOM (Software Bill of Materials) |
A Software Bill of Materials (SBOM) in Raynet One is a formal, machine-readable inventory of all software packages contained within a Docker container image. Raynet One automatically performs SBOM scans during Docker container inventory in CycloneDX JSON format, providing full visibility into the software components of containerized environments.
Purpose: Providing a complete inventory of software components in Docker container images during container inventory scans, supporting security assessments and vulnerability management for containerized environments Reference chapters: Docker Container SBOM Scan, Devices
|
Scheduled job/ task |
When creating a scheduled job (or task), you set a precise time frame for selected triggers for routine jobs executed on the Raynet One platform. This is a best practice routine because automated inventory and discovery runs make data management easier and less prone to errors. There are several ways to create scheduled jobs. Probably, users of other Raynet products are already familiar with the concept and purposes of scheduled jobs.
Purpose: Automating recurring platform tasks like inventory and discovery runs for a stable routine Reference chapters: Schedule your discovery and inventory jobs, Devices
|
Microsoft Endpoint Configuration Manager (MECM) |
Configuration Manager (configmgr, MCM), also known as Microsoft Endpoint Configuration Manager (MECM), previously known as System Center Configuration Manager (SCCM), is Microsoft's comprehensive IT network system management solution. It is used to remotely deploy operating systems or to service packages to registered systems, be it update or application. Devices are registered in hierarchies of sites. All kinds of Windows configuration options are provided to you in this program.
Raynet One is capable of discovering the devices registered inside of Microsoft Endpoint Configuration Manager.
Purpose: Maintaining complex IT networks of Windows devices Reference chapters: Self-service portal, Import devices from MECM
|
Self-service portal (SSP) |
Usually, a self-service portal is supposed to enable users to take initiative and start actions independently. It also offers them orientation and helps them navigate through a website, cloud or service platform. In the case of Raynet One, the self-service portal offers an overview on common user scenarios and leads first-time users through their first runner installation. However, you can only visit the portal once in the beginning as a new user unless there's a reset of the underlying database.
Purpose: Enabling first-time users to get an overview of common user scenarios, to learn about the functionality of Raynet One and to create their first runner more easily Reference chapters: Self-service portal, Add a Windows runner in the self-service portal
|
Session credentials |
Session credentials refer to the authentication information used to establish and manage user sessions within the Windows operating system. These credentials play a crucial role in managing user access, security, and resource interactions within the Windows environment. For example, administrators can query active user sessions using the query session command to see which users are currently logged in and their session types. Additionally, PowerShell allows running processes with specific credentials using the -Credential parameter.
Purpose: Inventory and discovery runs with individual user session credentials Reference chapters: Discover or inventory Windows assets with one-session credentials, Discover your IT landscape, Inventory your IT assets
|
Scope |
A scope represents a deduplication boundary within your IT environment. Scopes define logical groupings of IT assets where discovery and inventory operations are performed and where asset deduplication occurs. When assets are discovered by runners assigned to a specific scope, they are compared with other assets within the same scope for potential duplicates. Assets in different scopes remain separate and are not compared for deduplication. This allows you to manage complex IT landscapes with multiple locations, network segments, or organizational boundaries while maintaining control over how assets are identified and consolidated.
Purpose: Managing deduplication boundaries and organizing discovery operations across different locations, network segments, or organizational units in your IT landscape Reference chapters: Scopes, Discover your IT landscape, Inventory your IT assets
|
Sites |
Sites in Raynet One represent distinct physical or organizational locations within a managed IT environment. They are used to group and allocate networks and assets according to their geographical or organizational placement. Raynet One includes a default site called Default Site, and additional sites can be added to reflect multi-site IT environments.
Purpose: Enabling precise allocation of networks and assets to specific locations, supporting structured management of multi-site IT environments Reference chapters: Sites, Organize your IT landscape
|
SSH ports |
Basically, SSH ports are network ports used specifically for Secure Shell (SSH) connections, which provide a secure method of accessing a remote computer or server. They serve as numerical identifiers on a computer or server that are opened to accept incoming SSH traffic. Each port corresponds to a particular service or application. The standard SSH port is Port 22. For security reasons, alternative ports like Port 2222 or Port 8022 may be used to make automated attacks more difficult.
Purpose: Optional configurations in discovery settings Reference chapters: Discovery Settings
|
Staging/ Staged results |
Data staging is a pivotal step in data management where raw data undergoes transformation and preparation before being loaded into a data analytic system. So data staging bridges the gap between raw data and its final destination in a data analytic system. It ensures that data is well-prepared, reliable, and ready for analysis. There are basically two possible staging locations, internal and external staging. Finally, staged results is the data displayed after the staging process has been finished.
Purpose: Enhancing data quality and consistency through transformation Reference chapters: Discovery Settings
|
Technology Catalog |
The Technology Catalog is an external connection in Raynet One that provides structured, normalized, and enriched product and technology metadata. It supports product normalization, product matching, version information, EoL and EoS lifecycle data, and vulnerability-related metadata. During inventory scans, raw data is matched against the catalog for normalization and enrichment.
Purpose: Improving the quality, consistency, and depth of software and product data in Raynet One by providing authoritative product metadata for normalization, enrichment, and vulnerability assessment Reference chapters: Connections, Keep your IT landscape safe and healthy
|
Time stamp |
A timestamp is a sequence of characters or encoded information identifying when a certain event occurred, usually giving date and time of day, sometimes accurate to a small fraction of a second1. In computer systems, timestamps are used for a variety of reasons, e.g. logging, synchronization, versioning, and security.
Purpose: Tracking inventory and discovery runs in the most precise way possible for the user to follow up, especially with failed operations Reference chapters: Take action on your jobs in the Action center, Understand job details
|
Ungoverned Software |
Ungoverned Software in Raynet One refers to commercial software products discovered in the managed environment that have no corresponding purchase or entitlement recorded in the License Management workspace. These products are listed in the Ungoverned tab of the Entitlements view and represent potential compliance risks that require purchase capture or entitlement creation.
Purpose: Identifying software installations that are not yet covered by any license entitlement, enabling organizations to address potential compliance gaps and bring discovered software under license governance Reference chapters: Entitlements, License Management
|
Upgrade Rights |
Upgrade Rights is a mechanism in Raynet One's License Management that allows entitlements for an older version of a product to cover the demand for newer versions within the same product family. When an older-version entitlement has a surplus, the platform automatically transfers the available quantity to satisfy the demand of a newer version, provided the license model and metric match.
Purpose: Automatically applying entitlement surpluses from older product versions to cover compliance deficits in newer versions of the same product family during compliance calculations Reference chapters: Downgrade and upgrade rights, Compliance
|
Virtual machine (VM) |
A virtual machine (VM) is a software emulation of a physical computer. Imagine a VM as a computer that exists within another computer. It has its own CPU, memory, and storage for files, and it can connect to the internet if needed. While the components that make up a physical computer are tangible, VM's are often considered virtual computers or software-defined computers that exist only as code within physical servers. Hereby, the virtual machine is isolated from the rest of the system, meaning that the software within a VM cannot interfere with the host computer’s primary operating system.
Purpose: Development, application testing, security backups. parallel use of different operating systems Reference chapters: Hardware, Hypervisors
|
WMI (Windows Management Instrumentation) |
Windows Management Instrumentation (WMI) is a Microsoft framework that provides a standardized interface for accessing management information on Windows systems. In Raynet One, WMI is used during Windows inventory scans to query hardware, software, and system configuration data from Windows devices. Custom WMI queries can be configured to collect additional device-specific information.
Purpose: Enabling detailed hardware and software data collection from Windows devices during inventory runs, with the option to define custom queries for additional information gathering Reference chapters: Devices, Plugins
|
Zero Touch |
Zero Touch is Raynet One's agentless inventory method for collecting device data from Windows and Unix endpoints without installing a persistent agent on the target. It uses remote connectivity — WMI for Windows and SSH for Unix — to perform data collection directly from the platform, and is the primary inventory method for supported operating systems.
Purpose: Enabling agentless, non-intrusive inventory data collection from Windows and Unix devices, reducing deployment overhead and ensuring broad device coverage without requiring installed agents on target systems Reference chapters: Agentless Inventory Methods: Windows Zero Touch, Agentless Inventory Methods: Unix Zero Touch
|