This page is for the IT and security reviewers who approve iDNA Applications before or during an evaluation. It describes what iDNA reads from your HCL Notes and Domino environment, which access it needs for that, and which connections it uses. It applies to every license; the differences on a trial license are in one section at the end. It describes iDNA Applications 3.5.0 and later.

What happens to the data after it has been read (storage, processing, who sees what, and what leaves your network) is described on iDNA Applications Data Flow in Detail.

Overview

iDNA Applications runs on a Linux host in your network (the appliance). It reads from the Domino servers you select, with one Notes ID that you provide: the collection ID.

  • Read-only towards Domino. iDNA creates, changes or deletes no documents, designs or ACLs in your databases and runs no agents. The only console command it sends is show config *, which lists the server's notes.ini settings.
  • Connections start at the appliance: Notes RPC (TCP 1352) to your Domino servers; HTTP or HTTPS to a Domino web server only if web logs are read as text files.
  • From system databases: the Domino Directory, server documents and notes.ini settings, log.nsf, catalog.nsf and domlog.nsf; the DLAU and MarvelClient Analyze databases when those optional packages are used.
  • From application databases: the design and source code of focus applications and templates, the database's record of user activity, profile documents in full, and document metadata. No other document content, and no attachment contents.
  • Personal data: Notes user names, directory data about people and groups, IP addresses and client details from web logs and MarvelClient, mail addresses from the router's log. Stored on the appliance and pseudonymized in the analyses by default.

The Collection ID and the Access It Needs

iDNA reads everything with the collection ID. It needs the following access; the reference list is in System Requirements, Access and Permissions.

AccessWhereUsed for
Access to the server (cross-certified, allowed to access the server)Every Domino server in scopeAny collection from that server
ReaderThe Domino Directory (names.nsf) on one server per domain, and by default the directories configured in Directory AssistanceThe Domino Directory package
Readerlog.nsf and catalog.nsf of every server; domlog.nsf where web logging to it is enabledThe Server Basics, Database Catalog, Notes Client Activity and Web User Activity packages; the optional Domino Event Log and Mail Routing Activity packages
Full Remote Console AdministratorServer document of every server in scopeThe console command show config * and the console part of the server access check
Designer, or Full Access AdministrationDesigner in the ACL of every focus database and template; or Full Access Administration in the server documentDesign analysis. Where the ID has Full Access Administration, iDNA uses it by default. Reader access is the minimum for a database to be opened at all.
ReaderThe DLAU result database; the MarvelClient Analyze databaseThe optional HCL DLAU and MarvelClient Analyze packages
Reader, or Full Access Administration where the ID has itEach database a content scan is started forContent analysis

Connections

From → ToProtocol, portPurposeWhen
Appliance → Domino serversNotes RPC, TCP 1352All collection from DominoAlways
Appliance → Domino web serversHTTP or HTTPS, the port you configureReading web logs as text filesOnly if the Web User Activity package is set up to read text web logs over HTTP
Appliance → your DNS serversDNSResolving the Domino servers' host namesAlways

Your Domino servers open no connection to the appliance. Browser access to iDNA, logins through LDAP, email, AI clients and every connection that leaves your network are described in Data Flow in Detail, Who Sees What and What Leaves Your Network.

What iDNA Reads, by Source

iDNA collects in three ways:

Content Packages

PackageRead fromWhat is readPersonal data
Domino Directorynames.nsf on one server per domain; directories in Directory AssistancePerson documents, group documents (with members and owners), mail-in database documentsNames, organisational data and mail and internet addresses of people; group memberships
Server BasicsEvery server in scopeServer documents, connection documents, notes.ini settings (through show config *), server statistics (hourly)Administrator names in server documents
Database CatalogEvery server in scope; catalog.nsf, log.nsfThe list of databases with their properties (title, file path, replica ID, template, size, dates), catalog entries, the number of ACL entries per access level, database activity countsNone: ACL entries are counted, not stored by name
Notes Client Activitylog.nsfSession records: who opened which database on which server, when, with read and write counts (every 2 hours)Notes user names
Web User Activitydomlog.nsf, or text web logs over HTTP or HTTPSWeb requests: user name, client address and host name, user agent, requested URL, time. Cookies and referrers are not stored.User names, IP addresses, host names
Domino Event Log (optional)log.nsfEvents and security events: time, type, severity, server task and message textNames that appear in event messages
Mail Routing Activity (optional)log.nsfThe router's transfer and delivery events: sender, recipients, size, timeMail addresses
HCL DLAU (optional)The DLAU result databaseIts documents in full, rich text includedUser names and the licensing data DLAU recorded about them
MarvelClient Analyze (optional)The MarvelClient Analyze databaseClient records: Notes user name, home server, Notes and MarvelClient versions, operating system, operating system user name, IP addressAll of these

Design Analysis

Design analysis covers the focus databases (the database types Application and Mail-in, as classified from the catalog; you can adjust the classification with recategorization rules) and one replica of each template. It runs one database at a time and re-reads a design when it has changed, by default weekly on Saturday.

SourceRead fromWhat is readPersonal data
DesignFocus databases and templatesThe full design, exported as DXL: every design element and its code (LotusScript, Formula language, JavaScript, Java, XPages), names, comments, signers, last modifiers and dates; the database properties; the ACL with its entries, roles and log. The export is kept on the appliance as a compressed file. No data documents.Names of signers, modifiers and ACL entries; anything developers wrote into the code, such as names, addresses or credentials
User activity recordFocus databases and templatesThe activity that Notes records in each database: user names, dates, reads and writesNotes user names
Profile documentsFocus databasesEvery profile document in full: all items and their values, its modifiers and revision datesWhatever the application stores in its profile documents; modifier names
Content ageFocus databases (content-age module)The number of documents and their creation and modification dates, stored as counts per month. No item values, no form names.None

More on content age: Content Age and Data Retention Analysis in iDNA Applications.

Content Analysis

An iDNA user starts a content scan for one database at a time; each scan is counted against the license. The scan reads every document's metadata: form name, dates, modifiers, signed and encrypted flags, the names of encryption keys, whether reader and author fields are present, attachment names, sizes and dates, document links, and counts of rich-text elements. iDNA stores aggregates of these (attachments by type and size, modifiers with their counts). It reads no item values and no attachment contents.

Is Document or Mail Content Read?

Personal Data

Personal dataRead from
Notes user namesSession records, web logs, events, the user activity records of databases, ACLs, design signers and modifiers, profile documents, DLAU and MarvelClient records
Data about people and groupsPerson documents and group documents in the Domino Directory
IP addresses and client detailsWeb logs (client address, host name, user agent, requested URL); MarvelClient records (IP address, operating system user name)
Mail addressesThe router's log (Mail Routing Activity); the Domino Directory
Values written by applications or developersProfile documents, event messages, source code

All collected data is stored on the appliance with real names. User names are pseudonymized in the analyses by default. Which analyses show real names on purpose, who sees what, and what the AI components can reach are described on iDNA Applications Data Flow in Detail.

On a Trial License

A trial license uses the same sources, with the same access, as a full license: the content packages, and the design of every focus database and template, exported and kept as described above. The differences:

What a trial shows, and where it masks names, is described on iDNA Applications Trial License.

Related Topics