# IBM IBM is a company or institution recorded in [[Scanned_20260730-1706|Scanned_20260730-1706]]. In the reconstruction, IBM QRadar uses device support modules (DSMs) to normalize events from specific platforms. ## Historical and Technical Context [[IBM QRadar|IBM QRadar]] uses device support modules (DSMs) to normalize events from specific platforms. IBM's current documentation repeats the notebook wording almost exactly: the Juniper Junos OS DSM accepts syslog, structured-data syslog, or PCAP for SRX Series devices ([IBM QRadar Junos DSM](https://www.ibm.com/docs/nl/dsm?topic=networks-juniper-junos-os)). [[Intel Virtualization Technology for Directed I-O|Intel VT-d]] is Intel's I/O virtualization technology; an [[Input-output memory management unit|IOMMU]] remaps device DMA and is fundamental to secure device assignment into VMs. Intel provides a processor-identification route for checking virtualization features ([Intel virtualization support](https://www.intel.com/content/www/us/en/support/articles/000005486/processors.html)). [[Preboot Execution Environment|PXE]], network boot ROMs, BOOTP, and “PCI-LAN” enable booting an OS or imaging environment from the network. The Hitachi string resembles a 160 GB 2.5-inch hard-drive model. ## Role in Scanned_20260730-1706 The page connects perimeter control to centralized detection: the SRX does not merely enforce ALG policy; it also emits normalized evidence into a SIEM. The page joins two layers needed for a recovery/virtualization workstation: firmware-level network boot and kernel-level device isolation. ## Notebook Evidence - [[Scanned_20260730-1706|Scanned_20260730-1706]], PDF page 28: Junos/QRadar integration. - [[Scanned_20260730-1706|Scanned_20260730-1706]], PDF page 36: Intel VT-d and network-boot firmware notes. **Evidentiary status:** The page occurrence and transcription are notebook evidence. Technical identification follows the source reconstruction’s cited research. Co-occurrence does not by itself prove ownership, deployment, or a direct operational relationship. ## Relationships and Overlays On the cited page or pages, IBM appears with [[IBM QRadar|IBM QRadar]], [[Input-output memory management unit|IOMMU]], [[Intel Virtualization Technology for Directed I-O|Intel VT-d]], [[Preboot Execution Environment|PXE]]. These are page-level or reconstruction-level relationships, not automatic claims of dependency. ## Cross-Notebook Significance This entity expands the collection’s recurring vertical method: begin with a visible product, name, or interface; identify the hidden control layer; then connect it to recovery, authority, evidence, or continuity without assuming a relationship that the page does not prove. ## Missed Signals and Open Leads Determine whether the circular drawing reproduces a site icon, a DSM REDACTED, or a personal mnemonic. Several copied boot-ROM strings are uncertain. The source device and BIOS vendor should be identified before interpreting “RBS,” “Sgii,” “VF,” or “Russia sourceforge.” ## Sources - [[Scanned_20260730-1706|Scanned_20260730-1706]], especially PDF page(s) 28, 36. - `Scanned_20260730-1706.pdf`, cited as a plain archival filename; the PDF is not linked from `wiki-notes`. - External research citations used for identification remain preserved in the source reconstruction. - [IBM QRadar Junos DSM](https://www.ibm.com/docs/nl/dsm?topic=networks-juniper-junos-os) - [Intel virtualization support](https://www.intel.com/content/www/us/en/support/articles/000005486/processors.html) ## Scanned_20260730-1825 overlay PDF page 11 of [[Scanned_20260730-1825]] records `IBM → Bought Redhat` inside an Oracle Autonomous Linux comparison. The acquisition is used as a competitive and support-cost reference point for Oracle's pitch, not as evidence that IBM or Red Hat participated in the notebook author's infrastructure. This overlay adds a [[Corporate Lineage]] edge and a vendor-economics comparison while keeping product capability, ownership, and customer deployment distinct.