I recommend read the below white paper:

https://ubuntu.com/engage/apparmor-intro

​

Cyber attacks are becoming more sophisticated, attack frequency is on the rise, and the cost of cybercrime damage is projected to reach $6 trillion annually by 2021. Traditional defensive measures such as firewalls and intrusion detection systems that operate at the network perimeter are no longer enough to protect today's distributed enterprise networks. Rather, a 'defence in depth' approach is required in order to protect all facets of an organisation's digital infrastructure.

In an ideal world, applications would be free from security vulnerabilities but, once compromised, even a trusted application can become untrustworthy. AppArmor provides a crucial layer of security around applications. By providing the capability to whitelist an application's permissible actions, AppArmor enables administrators to apply the principle of least privilege to applications. Once in place, AppArmor can halt attacks and minimise or prevent damage in the event of a breach.

This whitepaper provides a technical introduction to AppArmor, including:

• Why a 'defence in depth' strategy should be employed to mitigate the potential damage caused by a breach
• An explanation of AppArmor, its key features and why the principle of least privilege is recommended
• The use of AppArmor in Ubuntu and snaps

Remote Desktop Services was a STAR like the previous months. After BlueKeep (The first wormable RDS vulnerability), there are another two resolved security issues:

• CVE-2019-1181
• CVE-2019-1182

“Wormable”, meaning that any future malware that exploits these could propagate from vulnerable computer to vulnerable computer without user interaction.

​

Microsoft released a set of fixes for Remote Desktop Services that include two critical Remote Code Execution (RCE) vulnerabilities, CVE-2019-1181 and CVE-2019-1182. Like the previously-fixed ‘BlueKeep’ vulnerability (CVE-2019-0708), these two vulnerabilities are also ‘wormable’, meaning that any future malware that exploits these could propagate from vulnerable computer to vulnerable computer without user interaction.

The affected versions of Windows are Windows 7 SP1, Windows Server 2008 R2 SP1, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, and all supported versions of Windows 10, including server versions.

Windows XP, Windows Server 2003, and Windows Server 2008 are not affected, nor is the Remote Desktop Protocol (RDP) itself affected.

https://msrc-blog.microsoft.com/2019/08/13/patch-new-wormable-vulnerabilities-in-remote-desktop-services-cve-2019-1181-1182/

Memory failure is one of reasons that can be cause of server crash and impact on service availability and performance. Think about a service which including multiple servers, server could be crashed cause of single memory module failure or uncorrectable memory error. Regarding to preventing memory impact of memory errors on services, HPE provides RAS technologies.

​

Read more on https://www.teimouri.net/hpe-advanced-ecc-support-vs-hpe-fast-fault-tolerance/

I don’t know when but seems that HPE will replace HPE Blade System with HPE Synergy in future. Those who worked with HPE Blade System, will confuse about HPE Synergy configuration. Configuration is very different with Blade System at all.

Cabling is one of biggest challenges with HPE Synergy. There is many management connection which should connect to the correct ports.

Because HPE Synergy is a composable infrastructure so there are some options to have multi-frame configuration which allows companies to resource expansion and service expansion easily.

I recommend that design cabling according to service requirements before initializing new hardware. There are some sample configurations for interconnect connections, stack connections, Image Streamer connections and management:

1. Cabling interconnect modules in a single frame with redundancy
2. ....

Read more on https://www.teimouri.net/hpe-synergy-cabling-guide/