Skip to content

Commit e104945

Browse files
Merge pull request #280805 from MicrosoftDocs/main
Publish to live, Sunday 4pm PST, 7/14
2 parents 55beaf8 + 8d594ca commit e104945

File tree

54 files changed

+680
-256
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

54 files changed

+680
-256
lines changed
4.36 KB
Loading

articles/azure-vmware/azure-security-integration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -159,7 +159,7 @@ After connecting data sources to Microsoft Sentinel, you can create rules to gen
159159
160160
6. On the **Incident settings** tab, enable **Create incidents from alerts triggered by this analytics rule** and select **Next: Automated response**.
161161
162-
:::image type="content" source="../sentinel/media/detect-threats-custom/general-tab.png" alt-text="Screenshot showing the Analytic rule wizard for creating a new rule in Microsoft Sentinel.":::
162+
:::image type="content" source="../sentinel/media/create-analytics-rules/general-tab.png" alt-text="Screenshot showing the Analytic rule wizard for creating a new rule in Microsoft Sentinel.":::
163163
164164
7. Select **Next: Review**.
165165

articles/defender-for-iot/organizations/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -369,6 +369,8 @@
369369
href: appliance-catalog/hpe-proliant-dl20-gen-11.md
370370
- name: Dell Edge 5200 (Rugged MIL-STD-810G)
371371
href: appliance-catalog/dell-edge-5200.md
372+
- name: Dell PowerEdge R360
373+
href: appliance-catalog/dell-poweredge-r360-e1800.md
372374
- name: Dell PowerEdge R350
373375
href: appliance-catalog/dell-poweredge-r350-e1800.md
374376
- name: Production line
Lines changed: 212 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,212 @@
1+
---
2+
title: Dell PowerEdge R360 for operational technology (OT) monitoring - Microsoft Defender for IoT
3+
description: Learn about the Dell PowerEdge R360 appliance's configuration when used for OT monitoring with Microsoft Defender for IoT in enterprise deployments.
4+
ms.date: 03/14/2024
5+
ms.topic: reference
6+
---
7+
8+
# Dell PowerEdge R360
9+
10+
This article describes the Dell PowerEdge R360 appliance, supported for operational technology (OT) sensors in an enterprise deployment.
11+
The Dell PowerEdge R360 is also available for the on-premises management console.
12+
13+
|Appliance characteristic | Description|
14+
|---------|---------|
15+
|**Hardware profile** | E1800|
16+
|**Performance** | Max bandwidth: 1 Gbps<br>Max devices: 10,000 |
17+
|**Physical Specifications** | Mounting: 1U with rail kit<br>Ports: 6x RJ45 1 GbE|
18+
|**Status** | Supported, available as a preconfigured appliance|
19+
20+
The following image shows a view of the Dell PowerEdge R360 front panel:
21+
<!-- look up images -->
22+
:::image type="content" source="../media/tutorial-install-components/r360-front.png" alt-text="Picture of the Dell PowerEdge R360 front panel." border="false":::
23+
24+
The following image shows a view of the Dell PowerEdge R360 back panel:
25+
<!-- look up images -->
26+
:::image type="content" source="../media/tutorial-install-components/r360-rear.png" alt-text="Picture of the Dell PowerEdge R360 back panel." border="false":::
27+
28+
## Specifications
29+
30+
|Component| Technical specifications|
31+
|:----|:----|
32+
|Chassis| 1U rack server|
33+
|Dimensions| Height: 1.68 in / 42.8 mm <br>Width: 18.97 in / 482.0 cm<br>Depth: 23.04 in / 585.3 mm (without bezel) 23.57 in / 598.9 mm (with bezel)|
34+
|Processor| Intel Xeon E-2434 3.4 GHz <br>8M Cache<br> 4C/8T, Turbo, HT (55 W) DDR5-4800|
35+
|Memory|32 GB |
36+
|Storage| 2.4 TB Hard Drive |
37+
|Network controller| - PowerEdge R360 Motherboard with with Broadcom 5720 Dual Port 1Gb On-Board LOM, <br>- PCIe Blank Filler, Low Profile. <br>- Intel Ethernet i350 Quad Port 1GbE BASE-T Adapter, PCIe Low Profile, V2|
38+
|Management|iDRAC Group Manager, Disabled|
39+
|Rack support| ReadyRails Sliding Rails With Cable Management Arm|
40+
41+
## Dell PowerEdge R360 - Bill of Materials
42+
43+
|Quantity|PN|Description|
44+
|----|---|----|
45+
|1| 210-BJTR | Base PowerEdge R360 Server|
46+
|1| 461-AAIG | Trusted Platform Module 2.0 V3 |
47+
|1| 321-BKHP | 2.5" Chassis with up to 8 Hot Plug Hard Drives, Front PERC |
48+
|1| 338-CMRB | Intel Xeon E-2434 3.4G, 4C/8T, 8M Cache, Turbo, HT (55 W) DDR5-4800 |
49+
|1| 412-BBHK | Heatsink |
50+
|1| 370-AAIP | Performance Optimized |
51+
|1| 370-BBKS | 4800 MT/s UDIMMs |
52+
|2| 370-BBKF | 16 GB UDIMM, 4800 MT/s ECC |
53+
|1| 780-BCDQ | RAID 10 |
54+
|1| 405-ABCQ | PERC H355 Controller Card |
55+
|1| 750-ACFR | Front PERC Mechanical Parts, front load |
56+
|4| 400-BEFU | 1.2 TB Hard Drive SAS 12 Gbps 10k 512n 2.5in Hot Plug |
57+
|1| 384-BBBH | Power Saving BIOS Settings |
58+
|1| 387-BBEY | No Energy Star |
59+
|1| 384-BDML | Standard Fan |
60+
|1| 528-CTIC | iDRAC9, Enterprise 16G |
61+
|2| 450-AADY | C13 to C14, PDU Style, 10 AMP, 6.5 Feet (2m), Power Cord |
62+
|1| 330-BCMK | Riser Config 2, Butterfly Gen4 Riser (x8/x8) |
63+
|1| 329-BJTH | PowerEdge R360 Motherboard with with Broadcom 5720 Dual Port 1Gb On-Board LOM |
64+
|1| 414-BBJB | PCIe Blank Filler, Low Profile |
65+
|1| 540-BDII | Intel Ethernet i350 Quad Port 1GbE BASE-T Adapter, PCIe Low Profile, V2, FIRMWARE RESTRICTIONS APPLY |
66+
|1| 379-BCRG | iDRAC, Factory Generated Password, No OMQR |
67+
|1| 379-BCQX | iDRAC Service Module (ISM), NOT Installed |
68+
|1| 325-BEVH | PowerEdge 1U Standard Bezel |
69+
|1| 350-BCTP | Dell Luggage Tag R360 |
70+
|1| 379-BCQY | iDRAC Group Manager, Disabled |
71+
|1| 470-AFBU | BOSS Blank |
72+
|1| 770-BCWN | ReadyRails Sliding Rails With Cable Management Arm |
73+
74+
## Install Defender for IoT software on the DELL R360
75+
76+
This procedure describes how to install Defender for IoT software on the Dell R360.
77+
78+
The installation process takes about 20 minutes. During the installation, the system restarts several times.
79+
80+
To install Defender for IoT software:
81+
82+
1. Connect the screen and keyboard to the appliance, and then connect to the CLI.
83+
84+
1. Connect an external CD or disk-on-key that contains the software you downloaded from the Azure portal.
85+
86+
1. Start the appliance.
87+
88+
1. Continue with the generic procedure for installing Defender for IoT software. For more information, see [Defender for IoT software installation](../how-to-install-software.md).
89+
90+
<!--
91+
## Dell PowerEdge R350 installation
92+
93+
This section describes how to install Defender for IoT software on the Dell PowerEdge R350 appliance.
94+
95+
Before installing the software on the Dell appliance, you need to adjust the appliance's BIOS configuration.
96+
97+
> [!NOTE]
98+
> Installation procedures are only relevant if you need to re-install software on a pre-configured device, or if you buy your own hardware and configure the appliance yourself.
99+
>
100+
101+
### Prerequisites
102+
103+
To install the Dell PowerEdge R350 appliance, you need:
104+
105+
- An Enterprise license for Dell Remote Access Controller (iDrac)
106+
107+
- A BIOS configuration XML
108+
109+
### Set up the BIOS and RAID array
110+
111+
This procedure describes how to configure the BIOS configuration for an unconfigured sensor appliance.
112+
If any of the steps below are missing in the BIOS, make sure that the hardware matches the specifications above.
113+
114+
Dell BIOS iDRAC is a system management software designed to give administrators control of Dell hardware remotely. It allows administrators to monitor system performance, configure settings, and troubleshoot hardware issues from a web browser. It can also be used to update system BIOS and firmware. The BIOS can be set up locally or remotely. To set up the BIOS remotely from a management computer, you need to define the iDRAC IP address and the management computer's IP address on the same subnet.
115+
116+
**To configure the iDRAC IP address**:
117+
118+
1. Power up the sensor.
119+
120+
1. If the OS is already installed, select the F2 key to enter the BIOS configuration.
121+
122+
1. Select **iDRAC Settings**.
123+
124+
1. Select **Network**.
125+
126+
> [!NOTE]
127+
> During the installation, you must configure the default iDRAC IP address and password mentioned in the following steps. After the installation, you change these definitions.
128+
129+
1. Change the static IPv4 address to **10.100.100.250**.
130+
131+
1. Change the static subnet mask to **255.255.255.0**.
132+
133+
:::image type="content" source="../media/tutorial-install-components/idrac-network-settings-screen-v2.png" alt-text="Screenshot that shows the static subnet mask in iDRAC settings.":::
134+
135+
1. Select **Back** > **Finish**.
136+
137+
**To configure the Dell BIOS**:
138+
139+
This procedure describes how to update the Dell PowerEdge R350 configuration for your OT deployment.
140+
141+
Configure the appliance BIOS only if you didn't purchase your appliance from Arrow, or if you have an appliance, but don't have access to the XML configuration file.
142+
143+
1. Access the appliance's BIOS directly by using a keyboard and screen, or use iDRAC.
144+
145+
- If the appliance isn't a Defender for IoT appliance, open a browser and go to the IP address configured beforehand. Sign in with the Dell default administrator privileges. Use **root** for the username and **calvin** for the password.
146+
147+
- If the appliance is a Defender for IoT appliance, sign in by using **XXX** for the username and **XXX** for the password.
148+
149+
1. After you access the BIOS, go to **Device Settings**.
150+
151+
1. Choose the RAID-controlled configuration by selecting **Integrated RAID controller 1: Dell PERC\<PERC H755 Adapter\> Configuration Utility**.
152+
153+
1. Select **Configuration Management**.
154+
155+
1. Select **Create Virtual Disk**.
156+
157+
1. In the **Select RAID Level** field, select **RAID10**. In the **Virtual Disk Name** field, enter **ROOT** and select **Physical Disks**.
158+
159+
1. Select **Check All** and then select **Apply Changes**
160+
161+
1. Select **Ok**.
162+
163+
1. Scroll down and select **Create Virtual Disk**.
164+
165+
1. Select the **Confirm** check box and select **Yes**.
166+
167+
1. Select **OK**.
168+
169+
1. Return to the main screen and select **System BIOS**.
170+
171+
1. Select **Boot Settings**.
172+
173+
1. For the **Boot Mode** option, select **UEFI**.
174+
175+
1. Select **Back**, and then select **Finish** to exit the BIOS settings.
176+
177+
### Install Defender for IoT software on the Dell PowerEdge R350
178+
179+
This procedure describes how to install Defender for IoT software on the Dell PowerEdge R350.
180+
181+
The installation process takes about 20 minutes. After the installation, the system restarts several times.
182+
183+
**To install the software**:
184+
185+
1. Verify that the version media is mounted to the appliance in one of the following ways:
186+
187+
- Connect an external CD or disk-on-key that contains the sensor software you downloaded from the Azure portal.
188+
189+
- Mount the ISO image by using iDRAC. After signing in to iDRAC, select the virtual console, and then select **Virtual Media**.
190+
191+
1. In the **Map CD/DVD** section, select **Choose File**.
192+
193+
1. Choose the version ISO image file for this version from the dialog box that opens.
194+
195+
1. Select the **Map Device** button.
196+
197+
:::image type="content" source="../media/tutorial-install-components/mapped-device-on-virtual-media-screen-v2.png" alt-text="Screenshot that shows a mapped device.":::
198+
199+
1. The media is mounted. Select **Close**.
200+
201+
1. Start the appliance. When you're using iDRAC, you can restart the servers by selecting the **Console Control** button. Then, on the **Keyboard Macros**, select the **Apply** button, which starts the Ctrl+Alt+Delete sequence.
202+
203+
1. Continue by installing OT sensor or on-premises management software. For more information, see [Defender for IoT software installation](../how-to-install-software.md).
204+
-->
205+
## Next steps
206+
207+
Continue learning about the system requirements for physical or virtual appliances. For more information, see [Which appliances do I need?](../ot-appliance-sizing.md).
208+
209+
Then, use any of the following procedures to continue:
210+
211+
- [Download software for an OT sensor](../ot-deploy/install-software-ot-sensor.md#download-software-files-from-the-azure-portal)
212+
- [Download software files for an on-premises management console](../legacy-central-management/install-software-on-premises-management-console.md#download-software-files-from-the-azure-portal)

articles/defender-for-iot/organizations/appliance-catalog/index.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,8 @@ landingContent:
3232
url: hpe-proliant-dl20-gen-11.md
3333
- text: Dell Edge 5200 (Rugged MIL-STD-810G)
3434
url: dell-edge-5200.md
35+
- text: Dell PowerEdge R360
36+
url: dell-poweredge-r360-e1800.md
3537
- text: Dell PowerEdge R350
3638
url: dell-poweredge-r350-e1800.md
3739

51.4 KB
Loading
1.27 MB
Loading

articles/sentinel/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -952,6 +952,8 @@
952952
href: threat-detection.md
953953
- name: Scheduled analytics rules
954954
items:
955+
- name: Overview
956+
href: scheduled-rules-overview.md
955957
- name: Create a scheduled rule from a template
956958
href: create-analytics-rule-from-template.md
957959
- name: Create a scheduled rule from scratch

articles/sentinel/automate-incident-handling-with-automation-rules.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ Automation rules are made up of several components:
5252

5353
### Triggers
5454

55-
Automation rules are triggered **when an incident is created or updated** or **when an alert is created**. Recall that incidents include alerts, and that both alerts and incidents can be created by analytics rules, of which there are several types, as explained in [Detect threats with built-in analytics rules in Microsoft Sentinel](detect-threats-built-in.md).
55+
Automation rules are triggered **when an incident is created or updated** or **when an alert is created**. Recall that incidents include alerts, and that both alerts and incidents can be created by analytics rules, of which there are several types, as explained in [Threat detection in Microsoft Sentinel](threat-detection.md).
5656

5757
The following table shows the different possible scenarios that will cause an automation rule to run.
5858

@@ -85,7 +85,7 @@ Even without being onboarded to the unified portal, you might anyway decide to u
8585
- A playbook can be triggered by an alert and send the alert to an external ticketing system for incident creation and management, creating a new ticket for each alert.
8686

8787
> [!NOTE]
88-
> - Alert-triggered automation is available only for alerts created by [**Scheduled**, **NRT**, and **Microsoft security** analytics rules](detect-threats-built-in.md).
88+
> - Alert-triggered automation is available only for alerts created by [**Scheduled**, **NRT**, and **Microsoft security** analytics rules](threat-detection.md).
8989
>
9090
> - Alert-triggered automation for alerts created by Microsoft Defender XDR is not available in the unified security operations platform. For more information, see [Automation with the unified security operations platform](automation.md#automation-with-the-unified-security-operations-platform).
9191

0 commit comments

Comments
 (0)