Question 1

Do the platform support single sign-on (SSO) and federated authentication?

Accepted Answer

Yes. moneo Cloud supports delegated authentication using open standards such as OAuth 2.0 and OpenID Connect (OIDC). Integration with enterprise identity providers that support OIDC is supported.

Question 2

Does the platform support multi-factor authentication (MFA)?

Accepted Answer

Yes, Multi-factor authentication can be enforced through the customer’s identity provider when federated authentication is used.

Question 3

What password complexity requirements are enforced for local accounts?

Accepted Answer

Passwords must be at least eight characters long and include at least one uppercase letter, one lowercase letter, one number, and one special character.

Question 4

What is the account lockout policy?

Accepted Answer

Accounts are locked after five failed login attempts. Accounts may be unlocked by an administrator.

Question 5

Does the platform support role-based access control (RBAC)?

Accepted Answer

Yes. moneo Cloud supports role-based access control with three permission levels: visitor, user, and administrator.

Question 6

Are inactive user sessions automatically terminated after a defined timeout period?

Accepted Answer

Yes. User sessions automatically expire after a defined period of inactivity to reduce the risk of unauthorized access from unattended sessions.

Question 7

How are APIs authenticated and secured?

Accepted Answer

Platform APIs require authenticated access using secure tokens. API authentication follows the same identity mechanisms used by the platform, and requests must be made over encrypted HTTPS connections.

Question 8

Are API tokens or credentials scoped to specific permissions?

Accepted Answer

Yes. API tokens are permission-scoped and inherit the privileges of the associated user or service identity. This ensures access is limited according to the principle of least privilege.

Question 9

Is moneo compliant with recognized industry standards and regulations?

Accepted Answer

Yes. moneo Cloud complies with ISO 27001, TISAX, and GDPR. Certification documents are available and can be accessed here: ifm Certificates.

Question 10

Who owns the data stored in the platform?

Accepted Answer

Customers retain ownership of all data processed and stored within their tenant environment.

Question 11

How is tenant data segregated?

Accepted Answer

Logical tenant separation is implemented at the application layer using tenant identifiers and separate schemas within databases.

Question 12

Are tenant environments isolated from one another?

Accepted Answer

Yes. Tenant environments are logically isolated using tenant identifiers, access controls, and database schema separation to prevent unauthorized access between tenants.

Question 13

How is data encrypted?

Accepted Answer

Data in transit is protected using TLS encryption. Data stored by the platform is protected using encryption-at-rest mechanisms provided by the underlying cloud infrastructure, including encrypted storage volumes and snapshots using AES-256 encryption.

Question 14

Can customers specify geographic data residency?

Accepted Answer

Yes. Customers select their deployment region during onboarding. Available regions include East US, East Australia, and West Germany.

Question 15

Can customers export their data?

Accepted Answer

Yes. Customers can export their data through supported interfaces and APIs.

Question 16

How long is customer data retained after contract termination?

Accepted Answer

Customer data is retained for six months following contract termination to allow for potential contract renewal. After this period, the data is permanently deleted.

Question 17

Can customers request permanent deletion of their data?

Accepted Answer

Yes. Customers may request deletion of their tenant data. When requested, data is permanently removed from active systems and associated storage according to the platform’s data management procedures.

Question 18

Can tenant-specific data preservation or legal holds be implemented?

Accepted Answer

Yes. Tenant data can be preserved through backup mechanisms when required for compliance or legal processes.

Question 19

How frequently are backups performed?

Accepted Answer

Management data is backed up once per day, and sensor data is backed up multiple times per day.

Question 20

Are backups encrypted?

Accepted Answer

Yes. Backup data is encrypted using the same encryption controls applied to primary storage systems.

Question 21

Are backups stored across multiple locations or availability zones?

Accepted Answer

Yes. Backup and disaster recovery mechanisms leverage multiple availability zones to ensure resilience and data durability.

Question 22

What is the recovery time objective (RTO)?

Accepted Answer

The maximum recovery time objective (RTO) is one day.

Question 23

Does moneo support disaster recovery?

Accepted Answer

Yes. moneo Cloud includes built-in redundancy across availability zones and tested disaster recovery procedures.

Question 24

Are disaster recovery procedures tested?

Accepted Answer

Yes. Disaster recovery procedures are tested quarterly.

Question 25

Can customers request restoration of their data?

Accepted Answer

Yes. Data restoration can be performed by the operations team when required.

Question 26

How is system performance monitored?

Accepted Answer

System performance is monitored continuously, and alerts trigger proactive scaling, tuning, or remediation.

Question 27

Are security events and suspicious activities monitored in real time?

Accepted Answer

Yes. Monitoring and security detection tools are used to identify suspicious activity such as abnormal login behavior, unusual traffic patterns, or operational anomalies.

Question 28

Can incidents be isolated to specific tenants?

Accepted Answer

Yes. Monitoring systems allow operational teams to associate issues with specific tenants.

Question 29

Does the platform maintain audit logs of user activities?

Accepted Answer

Yes. The platform records audit logs for key user actions and system events to support troubleshooting, security investigations, and operational monitoring.

Question 30

Are customers able to access internal system logs?

Accepted Answer

No. Customers do not have direct access to internal operational logs.

Question 31

What availability or uptime targets does the platform provide?

Accepted Answer

The platform is designed for high availability using redundant infrastructure and multiple availability zones. Service availability targets align with standard enterprise cloud reliability expectations.

Question 32

Does the platform support automatic scaling?

Accepted Answer

Yes. The platform can dynamically scale infrastructure resources in response to workload demands to maintain performance and availability.

Question 33

Are web application protections used to protect the platform from external attacks?

Accepted Answer

Yes. Network security controls, including cloud firewall protections and monitoring systems, help protect the platform from common web-based threats.

Question 34

Can the platform access devices within customer networks?

Accepted Answer

No. Moneo Cloud does not access local devices, software, or data within customer environments outside the cloud platform.

Question 35

Are security tests performed on new releases before deployment?

Accepted Answer

Yes. New releases undergo testing in controlled environments prior to production deployment. This process includes functional validation and security-related testing to reduce the risk of introducing vulnerabilities.

Endpoint	Port	IP address	Purpose
mqtt.e-us.moneo.cloud	8883	4.156.27.21	Process data transfer to cloud
mqtt.moon-w-eu.moneo.cloud	8883	72.144.90.228	Device to onboard & connect to cloud
system.update.ifm	443	100.64.1.60	Online update server
ifm-mobileiot-Services-prod.azurewebsites.net	443	20.50.2.16	Access MIOT suite portal
https://ioddfinder.io-link.com	443	5.75.147.253	Load IODD files

Endpoint	Port	IP address	Purpose
rc-c-us-prod-iothub.azure-devices.net	8883	20.44.8.248	Remote connect for device config and onboarding
relay0.remoteconnect-c-us-prod.moneo.ifm	443	20.109.216.120	Remote connect to c-us server
relay1.remoteconnect-c-us-prod.moneo.ifm	443	20.109.216.157	Remote connect to c-us server
stun0.remoteconnect-c-us-prod.moneo.ifm	3478	52.165.157.219	Remote connect to c-us server for direct P2P connection
stun1.remoteconnect-c-us-prod.moneo.ifm	3478	52.165.157.93	Remote connect to c-us server for direct P2P connection
global.azure-devices-provisioning.net	443	20.49.110.144	Remote connect for device config and onboarding
gm01-emea.ifm.com	443	193.242.155.235	Remote connect for remote access for ifm customer support

moneo device security

edgeGateway network architecture

Firewall rules

Device onboarding:

Remote connect:

moneo security FAQs

Authentication & access control

Compliance, standards, & security

Data management & segregation

Backup, recovery, & continuity

Performance & monitoring

Network & local device access

Software development & lifecycle

moneo security certifications