ServiceNow’s Identification and Reconciliation Engine solves two separate CMDB problems. Identification asks, “Does this incoming payload describe a CI that already exists?” Reconciliation asks, “If several sources know about the same CI, which source is allowed to update this attribute?” Treating these as one generic deduplication feature hides the architecture that keeps multi-source CMDB data trustworthy. Current ServiceNow Australia documentation still defines IRE as the centralized framework for identification and reconciliation across CMDB and some supported non-CMDB tables. Identification rules, reconciliation rules, data-source rules, dependent relationship rules, de-duplication tasks, reclassification…

Duplicate configuration items are rarely just a cleanup problem. They are evidence that one or more ingestion paths disagree about identity. Two records may represent the same server because Discovery and a connector used different identifiers, a transform bypassed IRE, a hostname changed, a cloud resource was recreated, or an identification rule was too weak. Manually merging the records fixes today’s symptom; fixing the identity architecture stops tomorrow’s duplicates. Current ServiceNow Australia documentation continues to use IRE de-duplication tasks for duplicate CI remediation. When IRE detects duplicate candidates, it can…

ServiceNow Discovery is useful only when the data it collects improves the CMDB instead of creating a second stream of noisy infrastructure records. Discovery can scan IP ranges, use MID Servers and credentials, classify devices, run patterns or probes, identify configuration items, and update the CMDB on a schedule. The engineering challenge is making sure those observations land in the correct classes, match existing CIs, respect source authority, create useful relationships, and age out correctly when the underlying environment changes. Current ServiceNow Australia documentation continues to position Discovery schedules as…

ServiceNow’s Common Service Data Model is a prescriptive model for organizing service-related data so the Now Platform can use the same definitions across products and workflows. CSDM 5 extends that model and clarifies how business capabilities, business applications, services, service offerings, service instances/application services, and infrastructure configuration items relate to one another. It is not a separate product or SKU, and it is not an implementation process that replaces configuration management. In practical terms, CSDM answers a recurring platform question: where should this information live, and how should it connect…

CMDB health should answer whether ServiceNow contains enough accurate, governed, and relationally useful configuration data to support operations. A single “health score” can be convenient, but teams need to understand the components behind that score and which defects actually affect incident, change, service mapping, automation, and reporting. ServiceNow’s current CMDB Health model evaluates three core KPIs—Completeness, Correctness, and Compliance—and also reports relationship health. Completeness looks for missing required or recommended attributes. Correctness includes issues such as duplicates, orphan CIs, and stale CIs. Compliance checks records against defined certification or audit…

CMDB governance fails when everyone can write data but nobody owns the meaning, quality, or lifecycle of what was written. ServiceNow CMDB spans infrastructure, applications, cloud resources, service modeling, ITSM, ITOM, asset management, security, enterprise architecture, and reporting. No single team has enough context to govern all of those domains alone. A workable governance model therefore separates platform stewardship, class and data ownership, source ownership, service ownership, and operational consumers. ServiceNow provides tools such as IRE, CI Class Manager, CMDB Health, Data Manager, relationship governance, certifications/attestation, and workspaces, but the…

A clean ServiceNow CMDB begins with a disciplined data model: configuration items belong in the right classes, each class has a clear purpose and identifiers, authoritative sources are known, duplicate creation is controlled, relationships are consistent, and lifecycle rules remove records that no longer represent the environment. Cleaning data after every import is expensive; designing the model so bad data is harder to create is more scalable. ServiceNow’s current CMDB platform provides a class hierarchy, CI Class Manager, Identification and Reconciliation Engine, CMDB Health, relationship governance, Data Manager, Discovery, Service…

Configuration items become operationally useful when ServiceNow can show how they depend on one another and which services they support. A server record with perfect CPU, owner, and serial-number data can still be almost useless during an outage if nobody knows which application service depends on it. CI relationships turn the CMDB from an inventory into a model that can support impact analysis, change planning, troubleshooting, service health, and automation. ServiceNow’s current CMDB documentation treats relationships as typed links between parent and child CIs, while CSDM provides prescriptive guidance for…

Fortinet security automation is most valuable when it takes a repeatable detection or operational event and executes a known response faster and more consistently than a human can. In the Fortinet Security Fabric, automation stitches can connect triggers—such as security events, compromised hosts, configuration changes, or scheduled conditions—to actions such as quarantine, notification, webhook calls, CLI scripts, FortiExplorer/FortiManager workflows, or integrations with other Fabric products depending on the FortiOS release and platform. The important design question is not “what can we automate?” but “which decisions are predictable enough that automation…

FortiGate SSL inspection creates one of the most important tradeoffs in modern firewall design: security products need visibility into encrypted traffic to inspect malware, applications, and content, while users and applications depend on TLS for confidentiality, identity, privacy, and protocol integrity. Certificate inspection can observe handshake metadata with limited disruption, while deep inspection decrypts and re-encrypts sessions so security profiles can inspect payloads. The stronger visibility comes with higher operational, privacy, certificate, and performance cost. FortiOS 7.6 continues to support certificate inspection and deep inspection profiles, exemption logic, certificate handling,…

FortiGate routing diagnostics should answer one question at a time: where does the appliance believe this packet should go, and why? Routing problems are often misdiagnosed as firewall policy, VPN, or NAT failures because the packet never reaches the expected interface pair. A systematic workflow starts with the routing table and route lookup, then checks policy routes or SD-WAN, dynamic-protocol state, packet flow, session state, and finally the return path. FortiOS 7.6 provides CLI diagnostics for routing tables, protocol databases, policy routes, SD-WAN health, packet sniffing, session tables, and debug…

FortiGate policy order matters because most policy tables are evaluated in a defined sequence and the first appropriate match determines what happens next. Troubleshooting therefore requires more than finding a rule that appears to allow the traffic. Engineers need to know which policy family applies, the incoming and outgoing interfaces, source and destination after the relevant translation stage, schedule, service, user or device context, policy mode, and whether an earlier broader rule captures the session first. In ordinary IPv4 firewall policy, administrators should think in top-down specificity: the first matching…

FortiGate high availability should be designed as a failure system, not as a checkbox that turns two appliances into one. The Fortinet Cluster Protocol synchronizes cluster state and elects a primary member, but the quality of the design depends on heartbeat links, monitored interfaces, session synchronization, device priorities, network topology, management access, upgrade behavior, and what the surrounding switches, routers, and providers do when ownership changes. Fortinet’s current FortiOS 7.6 documentation distinguishes active-passive and active-active FGCP clusters and describes election behavior using device priority, override configuration, uptime, monitored interfaces, and…

FortiGate can perform source NAT in more than one operational style. In the familiar policy-NAT model, SNAT is configured directly on the IPv4 firewall policy by enabling NAT and optionally selecting an IP pool. In central SNAT mode, source translation is moved into the separate central-snat-map table, while the firewall policy continues to decide whether the traffic is allowed. The choice changes where administrators look for translation logic and how finely they can match it. Fortinet’s current FortiOS 7.6 guidance states that central NAT is not enabled by default. When…

Securing enterprise Claude deployments requires several independent boundaries: authenticated user access, workload identity, data eligibility, model/provider controls, network path, tool permissions, memory and retrieval isolation, secret management, logging, and incident containment. The model’s safety behavior matters, but enterprise security must assume a user, document, tool result, or model can eventually behave unexpectedly and ensure that the surrounding system limits consequence. Anthropic’s current Trust Center lists commercial Claude API and Claude Enterprise against major assurance frameworks, and its enterprise guidance covers SSO, SCIM, role-based access, retention, audit, security integrations, and regulated…