Clear answers before you connect anything.

AssetObserve is an authorized IT asset discovery, risk and reporting platform. It builds a current inventory, highlights coverage gaps, turns evidence into findings, and produces management, technical and compliance reports from one workspace.

No. Discovery is read-only and must be explicitly scoped. It does not exploit systems, guess or brute-force passwords, or silently change, disable or fix anything.

No. Use only networks you own or are explicitly authorized to assess. Scanner placement, routing, firewall policy and discovery limits stay under the operator's control.

Start with an owned lab or a small approved internal segment. Enroll one scanner, confirm its heartbeat, run a limited discovery, review coverage and evidence, then expand deliberately.

No. One scanner collects authorized network evidence from a reachable position and can document Windows, Linux, macOS, printers, switches, hypervisors and more. Persistent endpoint mode is optional, mainly for roaming or rarely-connected devices.

Depending on the approved configuration: network discovery, optional endpoint inventory, read-only AD LDAPS, SNMPv3, DHCP/DNS HTTPS snapshots, VMware, and cloud collectors for Azure, Microsoft 365/Entra ID, AWS, Google Cloud, OCI and Open Telekom Cloud.

Only where routing, firewall rules and permissions allow it. Coverage shows blind spots so the team knows where another scan point or import path is needed.

Coverage records the expected scope, which source last observed it, freshness and visible gaps. It keeps reachable, unreachable, excluded, credential-failed and unknown outcomes explicit instead of letting a target quietly disappear.

A rule engine generates findings per asset from evidence against configurable thresholds, then weights them by business context. Findings store language-neutral keys, so the same finding renders in English, German or Turkish.

Installed-software evidence is matched against a locally-mirrored NVD corpus, enriched with CISA KEV (known-exploited) and FIRST.org EPSS (exploit probability). Matches are labeled "possible match, not confirmed" so they inform triage rather than overstate certainty.

It prepares you. The NIS2 readiness report and the guided compliance assessment map your evidence to frameworks like NIS2, ISO 27001 and GDPR and show a readiness score with the open questions that remain. It supports preparation and does not replace legal advice.

Yes. An accepted-risk decision documents why a finding is not being fixed now, with a scope (this asset, site or workspace), a business reason and an optional expiry date, and it can be reopened later.

No. The platform is built around a local credential boundary. Scan credentials stay in the customer-controlled agent or server vault and are never written to the database; only normalized evidence is uploaded to your workspace.

Normalized inventory and evidence -- hostnames, IPs, open ports, software, hardware, coverage and findings -- not raw secrets. Credentials remain local, and passwords or tokens should never be placed in tickets, reports or source code.

Agent API requests carry token-derived HMAC signatures over the method, path, timestamp, nonce and body hash, which protects request integrity. Production installer code-signing is a separate release control.

Your workspace runs on the AssetObserve Cloud service; hosting, data-processing and residency specifics are set out in the service agreement. For a specific deployment or a self-managed option, contact us.

Plans differ by asset, agent and monthly-scan limits and by feature access, checked before agents, scans, ingestion and PDF generation. The commercial Enterprise asset limit is 50,000. Current plans and prices are shown on the Billing page.

Yes. You can start on a trial and move to a paid plan from the Billing center. Plan and trial changes are managed there rather than by editing limits directly.

Yes. The partner center creates separated customer workspaces, keeps reports, tickets and billing per customer, and offers a portfolio risk board across tenants -- with customer authorization recorded per workspace.

Billing details drive hosted checkout and German invoice PDFs, and invoices are downloadable per row. Payments and plan changes happen in hosted checkout, not by AssetObserve staff editing your account.

Source observations stay separate from the resolved asset, and stable identifiers (serial number, SMBIOS UUID, managed-device ID, directory GUID, MAC address) are preferred. Ambiguous matches go to review instead of being silently merged.

Yes. Server-side search, filters, cursor pagination, saved views and asynchronous CSV exports mean you never load every asset into one page at once.

Discovery uses durable leases, checkpoints and retry states. Expired work is reassigned safely and signed agent batches can be replayed without creating duplicate evidence.

Check scanner placement, routing, firewall policy and credentials, then the last task outcome. Coverage and Operations show whether it is unreachable scope, failed authentication, stale data or an unassigned scan point.