HPE MSA 1060/2060/2062 Storage Management Guide
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Offensive-WMI
OFFENSIVE WMI Tim Medin [email protected] redsiege.com/wmi TIM MEDIN Red Siege - Principal IANS Faculty Consultant , Founder Formerly SANS ▸ CounterHack – NetWars, ▸ Principal Instructor Penetration Testing, CyberCity ▸ Co-author 460 Vulnerability Assessment ▸ FishNet (Optiv) – Sr Penetration Tester ▸ Instructor 560 Network Penetration Testing ▸ Financial Institution – Sr Technical Analyst – Security ▸ Instructor 660 Advanced Pen Testing, Exploit Dev ▸ Network Admin, Control Systems Engineer, Robots ▸ MSISE (Master of Engineering) Program Director WTH IS WMI WINDOWS MANAGEMENT INSTRUMENTATION “Infrastructure for management data and operations on Windows-based operating systems” ▸Common data formats – Common Information Model (CIM) ▸Common access methods Allows for management and monitoring the guts of Windows systems ▸Local ▸Remote First included in Windows 2000 WMIC is the command line interface ATTACK USAGE Not for initial access, but for many things after Requires credentials or existing access Used for ▸Recon ▸Lateral Movement ▸Situational Awareness ▸Persistence ▸PrivEsc ▸C&C QUERYING WITH WMI(C) “The WMI Query Language (WQL) is a subset of standard American National Standards Institute Structured Query Language (ANSI SQL) with minor semantic changes to support WMI.” The syntax will make you hate being born! GRAMMAR https://www.sans.org/security-resources/sec560/windows_command_line_sheet_v1.pdf RECONNAISSANCE & SITUATIONAL AWARENESS Get local user accounts with net user Get domain user accounts with net user /domain Both wmic useraccount -
Server Base Manageability Requirements 1.0 Platform Design Document Non-Confidential
Arm® Server Base Manageability Requirements 1.0 Platform Design Document Non-confidential Copyright © 2020 Arm Limited or its affiliates. All rights reserved. Document number: DEN0069B Server Base Manageability Requirements Server Base Manageability Requirements Copyright © 2020 Arm Limited or its affiliates. All rights reserved. Release inormation The Change History table lists the changes made to this document. Table 1-1 Change history Date Issue Confidentiality Change 30 January 2020 A Non-Confidential Initial release, SBMR 1.0 15 June 2020 B Non-Confidential License LES-PRE-21585 Page 2 of 45 Copyright © 2020 Arm Limited or its affiliates. All rights reserved. DEN0069B 1.0 Server Base Manageability Requirements Arm Non-Confidential Document Licence (“Licence”) This Licence is a legal agreement between you and Arm Limited (“Arm”) for the use of the document accompanying this Licence (“Document”). Arm is only willing to license the Document to you on condition that you agree to the terms of this Licence. By using or copying the Document you indicate that you agree to be bound by the terms of this Licence. If you do not agree to the terms of this Licence, Arm is unwilling to license this Document to you and you may not use or copy the Document. “Subsidiary” means any company the majority of whose voting shares is now or hereafter owner or controlled, directly or indirectly, by you. A company shall be a Subsidiary only for the period during which such control exists. This Document is NON-CONFIDENTIAL and any use by you and your Subsidiaries (“Licensee”) is subject to the terms of this Licence between you and Arm. -
Defending Against Out-Of-Band Management BMC Attacks
Defending Against Out-of-Band Management BMC Attacks Lee Fisher April 2019 LinuxFest NorthWest "Imagine trying to secure a computer with a small but powerful parasitic server on its motherboard; a bloodsucking leech that can't be turned off and has no documentation; you can't login, patch, or fix problems on it; server-based defensive, audit, or anti-malware software can’t be used for protection; its design is secret, implementation old, and it can fully control the computer's hardware and software; and it shares passwords with a bunch of other important servers, stores them in clear text for attackers to access. Not to mention it was designed for full control, remote management and monitoring, and it’s pretty damn good at it." --Dan Farmer, 2013 Agenda ● BMC/LOM concepts ● MC/SP (Intel ME/AMT, AMD PSP, Apple T2, ...) ● IPMI ● Intel SMM ● WS-MAN ● SMASH and DASH ● OpenBMC ● Redfish ● “IPMI++” (HP iLO, Dell iDRAC, ….) Credits ● All security guidance in this talk comes from existing BMC security research from: ● Dan Farmer, HD Moore, Matias Soler, Nicolas Waisman, Fabien Périgaud, Alexandre Gazet, Joffrey Czarny, Adrien Guinet, Jesse Michael, Mickey Shkatov, Oleksandr Bazhaniuk, ...and others that I am forgetting (sorry) CPU (and SMM) ● In early systems, the CPU was in charge of everything. Via the CPU, the firmware and OS code talked to the registers, RAM, and I/O busses. The CPU was in charge of system security. – This is the traditional model that attackers use, OS/app-level malware. ● On modern Intel (and AMD) systems, in addition to normal CPU mode, the CPU has a new mode, SMM (Systems Management Mode). -
Integrated Dell Remote Access Controller 9 (Idrac9) Version 3.00.00.00 User's Guide Notes, Cautions, and Warnings
Integrated Dell Remote Access Controller 9 (iDRAC9) Version 3.00.00.00 User's Guide Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2017 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. 2017-08 Rev. A01 Contents 1 Overview.......................................................................................................................................................17 Benefits of using iDRAC with Lifecycle Controller........................................................................................................18 Key features.......................................................................................................................................................................18 New in this release............................................................................................................................................................21 How to use this user's guide........................................................................................................................................... 21 Supported web browsers................................................................................................................................................22 -
Abusing Windows Management Instrumentation (WMI) to Build a Persistent, Asyncronous, and Fileless Backdoor Matt Graeber
Abusing Windows Management Instrumentation (WMI) to Build a Persistent, Asyncronous, and Fileless Backdoor Matt Graeber Black Hat 2015 Introduction As technology is introduced and subsequently deprecated over time in the Windows operating system, one powerful technology that has remained consistent since Windows NT 4.01 and Windows 952 is Windows Management Instrumentation (WMI). Present on all Windows operating systems, WMI is comprised of a powerful set of tools used to manage Windows systems both locally and remotely. While it has been well known and utilized heavily by system administrators since its inception, WMI was likely introduced to the mainstream security community when it was discovered that it was used maliciously as one component in the suite of exploits and implants used by Stuxnet3. Since then, WMI has been gaining popularity amongst attackers for its ability to perform system reconnaissance, AV and VM detection, code execution, lateral movement, persistence, and data theft. As attackers increasingly utilize WMI, it is important for defenders, incident responders, and forensic analysts to have knowledge of WMI and to know how they can wield it to their advantage. This whitepaper will introduce the reader to WMI, actual and proof-of-concept attacks using WMI, how WMI can be used as a rudimentary intrusion detection system (IDS), and how to perform forensics on the WMI repository file format. WMI Architecture 1 https://web.archive.org/web/20050115045451/http://www.microsoft.com/downloads/details.aspx?FamilyID=c17 4cfb1-ef67-471d-9277-4c2b1014a31e&displaylang=en 2 https://web.archive.org/web/20051106010729/http://www.microsoft.com/downloads/details.aspx?FamilyId=98A 4C5BA-337B-4E92-8C18-A63847760EA5&displaylang=en 3 http://poppopret.blogspot.com/2011/09/playing-with-mof-files-on-windows-for.html WMI is the Microsoft implementation of the Web-Based Enterprise Management (WBEM)4 and Common Information Model (CIM)5 standards published by the Distributed Management Task Force (DMTF)6. -
Overview of DMTF Information and Data Models
Overview of DMTF Information and Data Models ETSI NFV m-SDO Workshop, January 13, 2015 Presenter: Hemal Shah, Broadcom Corporation VP of Technology and Senior VP, DMTF Other Contributors: Enrico, John Leung, John Parchem, Bhumip, et al. Agenda • DMTF Technologies • DMTF Common Information Model (CIM) Overview • CIM based models/interfaces: NETMAN, VMAN, SMASH • Open Virtualization Format (OVF) • REST based Interfaces/Models: CIMI, CADF, Redfish • ETSI-NFV Infrastructure Management Mapping • Proposal to Move Forward 2 DMTF Management Technologies Infrastructure Management • Cloud • Virtualization • Data Center Platform Management • Server & Network • Storage (SNIA) • Desktop & Mobile Services Management • Network services DASH SMF • Software Entitlement • Security & audit NETMAN SMASH Protocols & Data Models (SMASH, PMCI, SMBIOS, CDM Redfish • WS-Man/CIM-XML SMF, Redfish) (SMI-S, CDM) (CDM, NETMAN) CIM, WBEM REST • REST/JSON/OData • CIM & Diagnostics • PLDM/MCTP 1/7/2016 DMTF Confidential 3 DMTF Common Information Model (CIM) • Common Information Model • Used by multiple orgs (e.g. SNIA SMI-S models for storage) • Core Specification • “Meta”-model, high level concepts and language definitions • “Core” and “Common” Models • Core Model contains info applicable to all mgmt domains • Common Models address specific domains • Application Applications and Services • Database Application Server • Device • Event Database • Interop Policy • Metrics Operating System/Virtualization Support • Network Systems, Devices/Storage, … Users/Security • Policy -
[MS-WSMV-Diff]: Web Services Management Protocol Extensions for Windows Vista
[MS-WSMV-Diff]: Web Services Management Protocol Extensions for Windows Vista Intellectual Property Rights Notice for Open Specifications Documentation ▪ Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions. ▪ Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation. ▪ No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. ▪ Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected]. -
CIM Query Language Specification
Document Number: DSP0202 Date: 2007-08-13 Version: 1.0.0 CIM Query Language Specification Document Type: Specification Document Status: Final Document Language: E CIM Query Language Specification DSP0202 Copyright notice Copyright © 2007 Distributed Management Task Force, Inc. (DMTF). All rights reserved. DMTF is a not-for-profit association of industry members dedicated to promoting enterprise and systems management and interoperability. Members and non-members may reproduce DMTF specifications and documents for uses consistent with this purpose, provided that correct attribution is given. As DMTF specifications may be revised from time to time, the particular version and release date should always be noted. Implementation of certain elements of this standard or proposed standard may be subject to third party patent rights, including provisional patent rights (herein "patent rights"). DMTF makes no representations to users of the standard as to the existence of such rights, and is not responsible to recognize, disclose, or identify any or all such third party patent right, owners or claimants, nor for any incomplete or inaccurate identification or disclosure of such rights, owners or claimants. DMTF shall have no liability to any party, in any manner or circumstance, under any legal theory whatsoever, for failure to recognize, disclose, or identify any such third party patent rights, or for such party’s reliance on the standard or incorporation thereof in its product, protocols or testing procedures. DMTF shall have no liability to any party implementing such standard, whether such implementation is foreseeable or not, nor to any patent owner or claimant, and shall have no liability or responsibility for costs or losses incurred if a standard is withdrawn or modified after publication, and shall be indemnified and held harmless by any party implementing the standard from any and all claims of infringement by a patent owner for such implementations. -
Windows Management Instrumentation (WMI) Offense, Defense, and Forensics
WHITE PAPER WINDOWS MANAGEMENT INSTRUMENTATION (WMI) OFFENSE, DEFENSE, AND FORENSICS William Ballenthin, Matt Graeber, Claudiu Teodorescu FireEye Labs Advanced Reverse Engineering (FLARE) Team, FireEye, Inc. SECURITY REIMAGINED Windows Management Instrumentation William Ballenthin, Matt Graeber, Claudiu Teodorescu FireEye Labs Advanced Reverse Engineering (FLARE) Team, (WMI) Offense, Defense, and Forensics FireEye, Inc. CONTENTS Introduction 2 Revision History 6 WMI Architecture 7 WMI Classes and Namespaces 8 Querying WMI 10 Instance Queries 10 Event Queries 11 Meta Queries 12 Interacting with WMI 13 PowerShell 13 wmic.exe 13 wbemtest.exe 14 WMI Explorer 15 CIM Studio 16 Windows Script Host (WSH) languages 16 C/C++ via IWbem* COM API 17 .NET System.Management classes 17 winrm.exe 17 wmic and wmis-pth for Linux 17 Remote WMI 17 Distributed Component Object Model (DCOM) 18 Windows Remote Management (WinRM) 18 WMI Eventing 19 Eventing Requirements 19 Event Filters 20 Intrinsic Events 20 Extrinsic Events 21 Event Consumers 21 Malicious WMI Persistence Example 22 WMI Attacks 23 Reconnaissance 23 Anti-Virus/VM Detection 23 2 Windows Management Instrumentation William Ballenthin, Matt Graeber, Claudiu Teodorescu FireEye Labs Advanced Reverse Engineering (FLARE) Team, (WMI) Offense, Defense, and Forensics FireEye, Inc. Code Execution and Lateral Movement 26 Win32_Process Create Method 26 Event consumers 27 Covert Data Storage 28 WMI as a C2 Channel 28 “Push” Attack 29 “Pull” Attack 30 WMI Providers 31 Malicious WMI Providers 32 WMI Defense 32 -
Sccm-2012-What-Is-New-In-Os-Deployment
APPENDIX B IN THIS APPENDIX ▶ General Resources Reference URLs ▶ Microsoft’s Configuration Manager Resources ▶ Other Configuration Manager Resources ▶ Blogs T his appendix includes a number of reference URLs associ- ▶ Public Forums ated with System Center 2012 R2 Configuration Manager ▶ Utilities (ConfigMgr). URLs do change: Although the authors have made every effort to verify the references here as working links, there is no guarantee they will remain current. It is quite possible some will change or be “dead” by the time you read this book. Sometimes the Wayback Machine ( https://www.archive.org/ ) can rescue you from dead or broken links. The Wayback Machine site is an Internet archive, and it takes you back to an archived version of a site...sometimes. These links are also available “live” at Pearson’s InformIT website, at http://www.informit.com/store/system-center- 2012-r2-configuration-manager-unleashed-9780672337154 , under the Downloads tab. Look for Appendix B , “Reference URLs.” General Resources A number of websites provide excellent resources for Configuration Manager. This section lists some of the more general resources available: ▶ http://www.myITforum.com is a community of world- wide Information Technology (IT) professionals and a website established in 1999 by Rod Trent. myITforum includes topics on System Center and IT. The list of blogs and other ConfigMgr-related articles at myITforum.com is enormous. This appendix includes some specific links and pertinent informa- tion, but it does not include everything. 316 APPENDIX B Reference URLs ▶ The Windows IT Pro forums are now at http://myITforum.com/forums. ▶ A great source of information is for all things System Center related, including Configuration Manager, is System Center Central, at http://www.systemcentercentral.com . -
Intel® Rack Scale Design (Intel® RSD) PODM Restful API Specification
Intel® Rack Scale Design (Intel® RSD) POD Manager (PODM) Representational State Transfer (REST) API Specification Software v2.5 July 2019 Revision 001 Document Number: 613320-001 You may not use or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel products described herein. You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted which includes subject matter disclosed herein. No license (express, implied, by estoppel, or otherwise) to any intellectual property rights is granted by this document. All information provided here is subject to change without notice. Contact your Intel representative to obtain the latest Intel product specifications and roadmaps. Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and noninfringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade. Intel technologies' features and benefits depend on system configuration and may require enabled hardware, software, or service activation. Performance varies depending on system configuration. No computer system can be secure. Check with your system manufacturer or retailer or learn more at www.intel.com. All information provided here is subject to change without notice. Contact your Intel representative to obtain the latest Intel product specifications and roadmaps. This document contains information on products, services, and/or processes in development. All information provided here is subject to change without notice. Contact your Intel representative to obtain the latest forecast, schedule, specifications, and roadmaps. The products and services described may contain defects or errors, known as errata, which may cause deviations from published specifications. -
SNMP Vs. WBEM
http://www.wbem.co.uk SNMP vs. WBEM The Future of Systems Management Over the last few months, I’ve been involved with system architects debating the pros and cons of SNMP and WBEM. Through these discussions and my personal experience, I’ve decided to write up my thoughts. The bottom line of this discussion is to explain why I think WBEM is a far superior systems management technology and how it addresses the short comings of SNMP. It should also highlight the major reasons why a rich systems management specification was needed in order to fill the void in present and future complex and large scale systems management environments. Let’s start by examining the abbreviations of SNMP (Simple Network Management Protocol) and WBEM (Web-Based Enterprise Management)… Simple This is one of the reasons why WBEM came about. SNMP can model simple management environments. When SNMP was initially established, it was used to manage routers and other network related equipment. These types of hardware didn’t require a complex management environment. In addition, the processing power of the hardware (usually) limited the scope of what it was able to run and so the management solution had to be lightweight. SNMP fitted perfectly. Routers (and the like) didn’t require a rich management interface and it was also lightweight enough to run in the embedded software. Now, the horizon is very different! Systems are more complex than routers (and network related hardware) and their management interface has stretched far beyond the simple nature of SNMP. Hardware now runs on much more powerful processors with more memory which in turn means the software that runs on them is capable of much more functionality.