DOCSLIB.ORG

XECUTE Administration Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
XECUTE Administration Guide ADMINISTRATION GUIDE XECUTE Version: 2.0 March 2019 Legal Information Software Copyright Notice Customer Care Introduction This guide provides details on the installation, upgrade, administration and maintenance of the RPM XECUTE. XECUTE consists of following installations: XECUTE Service l Windows service to be installed on the EPF application server XECUTE Config l Desktop utility to upload and configure XECUTE site data and manage system settings. XECUTE l Desktop application to schedule an XECUTE site. XECUTE+AR (iOS) and XECUTE Mobile (Android) l Mobile companion apps to view an XECUTE site. XECUTE+AR is available on the Apple App Store® for iPhone® and iPad® devices. XECUTE Mobile is available on the Google Play™ store for compatible devices. Please see the Mobile Requirements section for more information. Prerequisites XECUTE is an Enterprise service that has been designed to work in conjunction with EPF. XECUTE 2.0 requires EPF OMI and Model Repository version 2.2 or later. Please refer to the EPF Administration Guide for EPF setup instructions. Client Hardware requirements System requirements for XECUTE and XECUTE Config client applications. 2 | VERSION: 2.0 © 2019 RPMGLOBAL | All Rights Reserved Component Minimum Recommended Operating Windows 7 Professional (64-bit) Windows 10 Professional system SP1 (64-bit) Processor Intel i7 dual core Intel i7 quad physical core or better (PassMark - CPUMark score 13000 or higher) Memory 16 GB 32 GB Screen 1600 x 900 1920 x 1080, True Colour (32 resolution bit), 96dpi Graphics cards NVIDIA Quadro K2000 (1GB Video NVIDIA Quadro K2200 (4GB RAM) or equivalent Video RAM) or better (PassMark - G3D Mark score 3400 or higher) Mobile Requirements XECUTE+AR is a companion mobile app available to Apple iPhone and iPad devices iOS 8.0 or later. XECUTE+AR is designed to connect to the XECUTE Mobile Service to view active sites, or it can be run offline using the demonstration site included with the app. Augmented Reality (AR) functionality requires iOS 11 or later, and is supported on the iPhone SE, iPhone 6s, iPad (2017 model), iPad Pro or later editions of these devices. XECUTE Mobile is the companion mobile app for devices running Android 7.0 or later. XECUTE Mobile offers the same functionality as XECUTE+AR, but does not support augmented reality. Please contact RPMGlobal for more information. XECUTE Server XECUTE supports multiple deployment options, depending on the scale of the deployment and the technological maturity of the site. Options for a single-server deployment and a separate application and database server deployment are described below. The deployment patterns described here are intended for the final production environment. RPM strongly recommends that at least two separate environments are created for the project: l QA: Quality Assurance / Test environment: Used during the project for testing purposes prior to go-live, and after the project for testing of future upgrades, issue analysis and res- olution testing. 3 | VERSION: 2.0 © 2019 RPMGLOBAL | All Rights Reserved l Production: The live production environment commissioned during the final phase of the project. The separation of QA and Production environments involves the use of separate application serv- ers, separate SQL instances and, ideally separate SQL server host machines. Separation of the QA and Production environments ensures that any issues that occur during test- ing and deployment do not affect live production systems. RPM recommends that the QA environment be as similar as possible to the Production envir- onment to ensure that any potential issues are discovered early in the project, allowing adequate time for resolution prior to scheduled “Go-Live” deployment in the Production environment. Single-server deployment The single-server deployment is the simplest XECUTE deployment option. Single-server System Requirements Component Minimum Recommended Operating System Windows Server 2012 R2 Windows Server 2016 Database Microsoft SQL Server 2012 Microsoft SQL Server 2016 Standard SP2 Standard SP2 Processor Intel XEON quad physical Intel XEON Octa Core with core with hyper-threading (8 hyper-threading (16 logical logical cores). 2.2 GHz+ cores). 3 GHz+ Memory 32 GB 64 GB Database Space 2 TB* 2 TB* Note: * Storage space is for databases only. Model Repository requires additional space for storage of model files. Depending on usage, RPM suggests a minimum of 2 terabytes on an enterprise grade SAN. RPM recommends separate partitions for SQL data files, log files and backup. Typical production topology EPF and XECUTE services are not restricted to using a single SQL server. There are multiple options for physical server locations; the specific option is determined during implementation. 4 | VERSION: 2.0 © 2019 RPMGLOBAL | All Rights Reserved Separate Database Server Deployment The separate database server deployment provides for the application and database server infra- structure to be physically separated and independently managed and scaled. This deployment option provides for targeted scalability. XECUTE Application Server System Requirements Component Minimum Recommended Operating System Windows Server 2012 R2 Windows Server 2016 Processor Intel XEON quad core with Intel XEON Octa core with hyper-threading (8 logical hyper-threading (16 logical cores). 2.2 GHz+ cores). 3 GHz+ Application Storage 3 GB 3 GB Memory 32 GB 64 GB 5 | VERSION: 2.0 © 2019 RPMGLOBAL | All Rights Reserved EPF Application Server System Requirements Component Minimum Recommended Operating System Windows Server 2012 R2 Windows Server 2016 Processor Intel i7 dual core CPU with hyper-threading (4 logical cores) Application Storage 3 GB Memory 16 GB Database Server System Requirements Component Minimum Recommended Operating System Windows Server 2012 R2 Windows Server 2016 Database Microsoft SQL Server 2012 Microsoft SQL Server 2016 Standard SP2 Standard SP2 Processor Intel dual core CPU quad physical core or better (PassMark - CPUMark score 9000 or higher) Memory 16 GB Database Space 2 TB* 2 TB* Note: * Storage space is for databases only. Model Repository requires additional space for storage of model files. Depending on usage, RPM suggests a minimum of 2 terabytes (RAID 5 + stripping). RPM recommends separate partitions for SQL data files, log files and backup. 6 | VERSION: 2.0 © 2019 RPMGLOBAL | All Rights Reserved Installation Guide Application Server Pre-Installation Configuration The following must be installed / configured on the application server prior to installing any applic- ation components: 1. Microsoft .NET 4.6.2. 2. Microsoft Distributed Transaction Coordinator service must be running and configured cor- rectly (please see section titled “Microsoft Distributed Transaction Coordinator”). Note: Access to the databases must be provided via Microsoft SQL Server Man- agement Studio. Where remote desktop access to the database server is not per- mitted, RPM recommends that SQL Server Management Studio be installed on the Application Server. Database Server Pre-Installation Configuration Microsoft Distributed Transaction Coordinator service must be running and configured correctly (please see section titled “Microsoft Distributed Transaction Coordinator”). The database server should be configured as shown in the table below: 7 | VERSION: 2.0 © 2019 RPMGLOBAL | All Rights Reserved Configuration Property Setting Server Collation Latin1_General_CI_AS Memory allocation Dependent on available memory and other applications, but at least 2GB Automatic Processor Affinity Mask True Automatic IO Affinity mask True Server Authentication Mixed Mode (SQL Server and Win- dows) Remote Connections True FILESTREAM for Transact-SQL access Must be enabled for EPF Model Repository FILESTREAM for file I/O streaming access Must be enabled for EPF Model Repository. The default setting should be used in the Windows Share Name box. It must not be blank. Allow remote clients access to FILESTREAM Must be enabled for EPF Model data Repository. Installation Account To install the software, a user account must be provided for use by the RPM implementation team during the installation process. The account should conform to the general user account man- agement policy of the client organisation. The installation account must have the following permissions on the application server: l Local administration rights l Permission to install software The installation account must have the following permissions on the database server: l SQL ‘sysadmin’ rights if the databases have not been pre-installed; OR l SQL ‘dbo’ rights on each of the pre-installed databases if this has been done 8 | VERSION: 2.0 © 2019 RPMGLOBAL | All Rights Reserved Ideally, SQL Server Management Studio should be installed and available for use by the install- ation account. This can be on the application server, or on the database server if the installation account is given local user rights on the database server. Service Account A domain service account must be created to be used as the start-up account for the XECUTE service. The account must satisfy the following requirements: l It must be a domain-level account (not a local system account) l Password never expires l Don’t require password change at next logon l Disallow interactive logon (recommended) l Given the Logon as a service right in the local group policy settings on the application server l Given write permissions to the “%programdata%\RungePincockMinarco” and "%programdata%\RPMGlobal" folders (including subfolders and files)
Load more

Recommended publications
  • What Is a Service? a Windows Service Is an Application That Usually
    What is a service? A Windows service is an application that usually provides a basic Windows function such as manage system memory, make and monitor network connections, play sound, provide a file system, control security and authentication, interact with the user and many more. They run in the background and have has no user interface. Services are always running, whether they are needed or not. Think about setting these to Manual • Bluetooth Services (2): If you don't connect Bluetooth devices to your computer • Connected End User Experience and Telemetry: Microsoft Keyboard Logger • Diagnostic Policy Service: If you don't depend on Windows diagnostics • Distributed Link Tracking Client: When was the last time you created a symbolic link to a shared file? • dmwappushsvc: Transmits keyboard logger data to Microsoft. • Downloaded Maps Manager: If you use any other map service than the Maps app. • Fax: Not needed for printer fax machines, or if you don't have a fax. • IP Helper: IPV6 to IPV4 tools • Print Spooler: If you don't have a printer • Remote Access Connection Manager: If you don't use a VPN or access your home system remotely • TCP/IP NetBIOS Helper: If you are not in a workgroup network • Touch Keyboard and Handwriting Panel Service: If you don't need the screen touch keyboard or the handwriting features • Windows Media Player Network Sharing Service: Shares music across the home network • Windows Defender (4): If you use another antivirus program • Windows Image Acquisition: If you don't have a scanner • Windows Update: If you want to control the update process.
    [Show full text]
  • Attacker Antics Illustrations of Ingenuity
    ATTACKER ANTICS ILLUSTRATIONS OF INGENUITY Bart Inglot and Vincent Wong FIRST CONFERENCE 2018 2 Bart Inglot ◆ Principal Consultant at Mandiant ◆ Incident Responder ◆ Rock Climber ◆ Globetrotter ▶ From Poland but live in Singapore ▶ Spent 1 year in Brazil and 8 years in the UK ▶ Learning French… poor effort! ◆ Twitter: @bartinglot ©2018 FireEye | Private & Confidential 3 Vincent Wong ◆ Principal Consultant at Mandiant ◆ Incident Responder ◆ Baby Sitter ◆ 3 years in Singapore ◆ Grew up in Australia ©2018 FireEye | Private & Confidential 4 Disclosure Statement “ Case studies and examples are drawn from our experiences and activities working for a variety of customers, and do not represent our work for any one customer or set of customers. In many cases, facts have been changed to obscure the identity of our customers and individuals associated with our customers. ” ©2018 FireEye | Private & Confidential 5 Today’s Tales 1. AV Server Gone Bad 2. Stealing Secrets From An Air-Gapped Network 3. A Backdoor That Uses DNS for C2 4. Hidden Comment That Can Haunt You 5. A Little Known Persistence Technique 6. Securing Corporate Email is Tricky 7. Hiding in Plain Sight 8. Rewriting Import Table 9. Dastardly Diabolical Evil (aka DDE) ©2018 FireEye | Private & Confidential 6 AV SERVER GONE BAD Cobalt Strike, PowerShell & McAfee ePO (1/9) 7 AV Server Gone Bad – Background ◆ Attackers used Cobalt Strike (along with other malware) ◆ Easily recognisable IOCs when recorded by Windows Event Logs ▶ Random service name – also seen with Metasploit ▶ Base64-encoded script, “%COMSPEC%” and “powershell.exe” ▶ Decoding the script yields additional PowerShell script with a base64-encoded GZIP stream that in turn contained a base64-encoded Cobalt Strike “Beacon” payload.
    [Show full text]
  • Guide to Hardening Windows 10 Technical Guide
    NOVEMBER 2020 Guide to Hardening Windows 10 For Administrators, Developers and Office Workers TABLE OF CONTENTS Introduction .......................................................................................................................... 4 Prerequisites ............................................................................................................................ 4 User roles ................................................................................................................................. 4 EFI (BIOS) Configuration ...................................................................................................... 5 To be enabled: ......................................................................................................................... 5 To be disabled: ......................................................................................................................... 5 Windows Defender Firewall .................................................................................................. 6 Enable logging of dropped packets ............................................................................................. 6 Disable enforcement of local rules and disable notifications .......................................................... 7 Block outbound connections by default ....................................................................................... 8 Secure potentially vulnerable protocols ......................................................................................
    [Show full text]
  • Creating a Windows Service That Uses Microsoft Dynamics Gp Econnect to Integrate Data
    INNOVATE Microsoft Dynamics™ GP Creating a Windows® service that uses Microsoft Dynamics GP eConnect to integrate data Article Create a Windows Service that uses the .NET FileSystemWatcher class to monitor a directory for file operations Date: April, 2008 Table of Contents Introduction ................................................................................................ 3 Overview ..................................................................................................... 3 Start a new application in Visual Basic .NET ................................................ 3 Add References needed by the new application .......................................... 3 Add code to the project ............................................................................... 4 Add Imports statements and set the Service Name .................................................................. 4 Declare a FileSystemWatcher object and add code to the OnStart event ..................................... 4 Add code to the OnStop event .............................................................................................. 5 Add a handler for the xmlWatcher.Created event ..................................................................... 5 Add and configure an installer for the service ............................................. 5 Build, install and test the service ................................................................ 6 2 CREATING A WINDOWS SERVICE THAT USES MICROSOFT DYNAMICS GP ECONNECT TO INTEGRATE DATA Introduction
    [Show full text]
  • Docker Windows Task Scheduler
    Docker Windows Task Scheduler Genealogical Scarface glissading, his karyotype outgone inflicts overflowingly. Rudolph is accessorial and suckers languorously as sociologistic Engelbart bridled sonorously and systematises sigmoidally. Which Cecil merchandises so unbelievably that Cole comedowns her suavity? Simple task runner that runs pending tasks in Redis when Docker container. With Docker Content Trust, see will soon. Windows Tip Run applications in extra background using Task. Cronicle is a multi-server task scheduler and runner with a web based front-end UI It handles both scheduled repeating and on-demand jobs targeting any. Django project that you would only fetch of windows task directory and how we may seem. Docker schedulers and docker compose utility program by learning service on a scheduled time, operators and manage your already interact with. You get a byte array elements followed by the target system privileges, manage such data that? Machine learning service Creatio Academy. JSON list containing all my the jobs. As you note have noticed, development, thank deity for this magazine article. Docker-crontab A docker job scheduler aka crontab for. Careful with your terminology. Sometimes you and docker schedulers for task failed job gets silently redirected to get our task. Here you do want to docker swarm, task scheduler or scheduled background tasks in that. Url into this script in one easy to this was already existing cluster created, it retry a little effort. Works pretty stark deviation from your code is followed by searching for a process so how to be executed automatically set. Now docker for windows service container in most amateur players play to pass as.
    [Show full text]
  • Automated Malware Analysis Report for Spoolsv.Exe
    ID: 160124 Sample Name: spoolsv.exe Cookbook: default.jbs Time: 10:37:44 Date: 05/08/2019 Version: 26.0.0 Aquamarine Table of Contents Table of Contents 2 Analysis Report spoolsv.exe 4 Overview 4 General Information 4 Detection 4 Confidence 4 Classification 5 Analysis Advice 5 Mitre Att&ck Matrix 6 Signature Overview 6 Spreading: 6 System Summary: 6 Data Obfuscation: 7 Boot Survival: 7 Hooking and other Techniques for Hiding and Protection: 7 Malware Analysis System Evasion: 7 Anti Debugging: 7 HIPS / PFW / Operating System Protection Evasion: 7 Language, Device and Operating System Detection: 7 Remote Access Functionality: 7 Behavior Graph 7 Simulations 8 Behavior and APIs 8 Antivirus and Machine Learning Detection 8 Initial Sample 8 Dropped Files 8 Unpacked PE Files 8 Domains 8 URLs 9 Yara Overview 9 Initial Sample 9 PCAP (Network Traffic) 9 Dropped Files 9 Memory Dumps 9 Unpacked PEs 9 Joe Sandbox View / Context 9 IPs 9 Domains 9 ASN 9 JA3 Fingerprints 9 Dropped Files 9 Screenshots 9 Thumbnails 9 Startup 10 Created / dropped Files 10 Domains and IPs 11 Contacted Domains 11 Contacted IPs 11 Static File Info 11 General 11 File Icon 11 Static PE Info 12 General 12 Entrypoint Preview 12 Rich Headers 13 Data Directories 13 Sections 13 Resources 14 Imports 14 Copyright Joe Security LLC 2019 Page 2 of 22 Exports 15 Version Infos 18 Possible Origin 18 Network Behavior 19 Code Manipulations 19 Statistics 19 Behavior 19 System Behavior 19 Analysis Process: cmd.exe PID: 2748 Parent PID: 480 19 General 19 File Activities 20 File Created 20 Analysis
    [Show full text]
  • How to Restart Premisys Services
    PremiSys Services Troubleshooting Introduction There are two services which comprise the PremiSys application server components. These services are: • IDenticard Windows Service • IDenticard Scheduling Service Under normal conditions, both of these services are configured to start automatically when the server starts. Both are also dependent on connection to the PremiSys databases which are hosted by a Microsoft SQL Server. The instance of SQL Server may or may not reside on the same server as the PremiSys application server, depending on the way the system has been designed. IDenticard Windows Service The IDenticard Windows Service is the primary server component of the PremiSys software. It handles the server side code for client logins, licensing, panel communications, transaction processing, etc. When this service is stopped, any running instance of the PremiSys client will receive a message box that indicates “The connection to the {server name} license server has been lost”. When the user acknowledges this message box, the client application will close. If a user attempts to restart the client application while the IDenticard Windows Service is stopped on the Application Server, they will receive a message box which indicates “AddIn Architecture Failed to start – Services unavailable…”. IDenticard Scheduling Service The IDenticard Scheduling Service runs various tasks within a PremiSys system. This includes, but is not limited to user- scheduled tasks for things like backups, transaction archives, reports and door schedules. When this service is stopped, any scheduled tasks will not run on their scheduled execution time. Starting Services Step-By-Step 1. Click on the “Windows Start Menu” Button on the lower-right corner of the Windows Desktop 2.
    [Show full text]
  • Windows Intruder Detection Checklist
    Windows Intruder Detection Checklist http://www.cert.org/tech_tips/test.html CERT® Coordination Center and AusCERT Windows Intruder Detection Checklist This document is being published jointly by the CERT Coordination Center and AusCERT (Australian Computer Emergency Response Team). printable version A. Introduction B. General Advice Pertaining to Intrusion Detection C. Look for Signs that Your System may have been Compromised 1. A Word on Rootkits 2. Examine Log Files 3. Check for Odd User Accounts and Groups 4. Check All Groups for Unexpected User Membership 5. Look for Unauthorized User Rights 6. Check for Unauthorized Applications Starting Automatically 7. Check Your System Binaries for Alterations 8. Check Your Network Configurations for Unauthorized Entries 9. Check for Unauthorized Shares 10. Check for Any Jobs Scheduled to Run 11. Check for Unauthorized Processes 12. Look Throughout the System for Unusual or Hidden Files 13. Check for Altered Permissions on Files or Registry Keys 14. Check for Changes in User or Computer Policies 15. Ensure the System has not been Joined to a Different Domain 16. Audit for Intrusion Detection 17. Additional Information D. Consider Running Intrusion Detection Systems If Possible 1. Freeware/shareware Intrusion Detection Systems 2. Commercial Intrusion Detection Systems E. Review Other AusCERT and CERT Documents 1. Steps for Recovering from a Windows NT Compromise 2. Windows NT Configuration Guidelines 3. NIST Checklists F. Document Revision History A. Introduction This document outlines suggested steps for determining whether your Windows system has been compromised. System administrators can use this information to look for several types of break-ins. We also encourage you to review all sections of this document and modify your systems to address potential weaknesses.
    [Show full text]
  • Security and Compliance
    Security and Compliance Robert Nottoli | Principal Technology Specialist | Microsoft Corporation [email protected] DISCLAIMER FOR DOCUMENTATION REGARDING PRE-RELEASED SOFTWARE This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release, including URL and other Internet Web sites referenced, and is the confidential and proprietary information of Microsoft Corporation. The entire risk of the use or the results from the use of this document remains with the user. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. Therefore, MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
    [Show full text]
  • Installation and Setup Guide for Server
    FUJITSU Software Symfoware Server V12.1.0 Installation and Setup Guide for Server Windows B1WS-1136-03ENZ0(00) December 2014 Preface Purpose of This Document The Symfoware Server database system extends the PostgreSQL features and runs on the Windows platform. This document describes how to install and setup "Symfoware Server". Intended Readers This document is intended for those who install and operate Symfoware Server. Readers of this document are assumed to have general knowledge of: - PostgreSQL - SQL - Windows Structure of This Document This document is structured as follows: Chapter 1 Overview of Installation Describes the installation types and procedures Chapter 2 Operating Environment Describes the operating environment required to use Symfoware Server Chapter 3 Installation Describes how to perform an new installation of Symfoware Server Chapter 4 Setup Describes the setup to be performed after installation Chapter 5 Uninstallation Describes how to uninstall Symfoware Server Appendix A Installation in Silent Mode Provides specifications for installation in silent mode Appendix B Symfoware Server Migration Procedures Describes how to migrate Symfoware Server from an old version/level. Appendix C Using WebAdmin After an Upgrade Describes the required operations for using WebAdmin after an upgrade. Appendix D Recommended WebAdmin Environments Describes the recommended WebAdmin environment. Appendix E Setting Up and Removing WebAdmin Describes how to set up and remove WebAdmin Appendix F Configuring Parameters Describes Symfoware
    [Show full text]
  • Conversion Server User Guide
    www.AutoDWG.com Thank you for using AutoDWG Conversion Server Software AutoDWG Conversion Server With AutoDWG Conversion Server, companies can convert dwg to pdf, dwg to image automatically at high speed in a centrally-managed server. Users upload or drop dwg files into a watched folder, the drawing will be convert into pdf, dwf or image automatcially at once, Users can set up different folders in different output policy to specify output file type, and others setting. Features • Windows Service Program, no AutoCAD required in the server. • Supports dwg to pdf, dwg to jpg, dwg to bmp, dwg to gif, dwg to bmp, dwg to png conversion. • Supports AutoCAD drawing format from R2.5 to the latest version R2008. Email us [email protected] for more information and pricing. Download Free Trial Quick Start: • Install the software, register the DLL files and the acs.exe service o RUN: Regsvr32 “Full path\DWG2PDFX.dll” o RUN: Regsvr32 “Full path\DWG2imageX.dll” o RUN: Regsvr32 “Full path\mfc42.dll” o Set up the PS path, copy the whole folder of “PS” to C:\windows\system32\PS o RUN: acs.exe /service o Start the service from the [Windows control panel\Administrative tools\Services] • Launch AcsCtrl.exe to set up profiles of the watched folders and output file formats o Click menu button “File/New Profile” to create new watched folder o Right click on the existing listed input folder, click “add a profile” to create more out put file formats or copy files without convert • Click on the button “Start Server” to start the conversion service Æ Go to Trouble Shooting and learn more on the installation www.AutoDWG.com User’s manual The AutoDWG Conversion server is enterprise class software, and recommended to installed with a server, the requirements to the server listed as below: Hard ware requirements, CPU: PIII 1GHz or greater, a modern processor is recommended, since the conversion calculation will be kind of heavy loading to the CPU.
    [Show full text]
  • Event Logs What Are Event Logs?
    Event Logs What are event logs? Windows keeps track of almost everything that happens in the operating system Microsoft defines an event as "any significant occurrence in the system or in a program that requires users to be notified or an entry added to a log." Examples of events are log ons, log offs, connections to wireless access points, improper shut downs of the computer, installations of programs, etc Windows Event Logs ● What is actually recorded in the event log is dependent on the applications involved and the system settings ● Security event logging is disabled by default on most freshly installed windows sysstems. ● If they exists, event logs cad be incredibly useful, they would provided both local and network context that is difficult to replicate with other artifacts. Event Log Analysis ● What Happened?: Event ID ->Event Category->Description ● Date/Time?: Time Stamp ● Users involved?: User Account->Description ● Systems Involved?:Hostname->IP Address ● Resources Accessed?: Files->Folders->Printers->Services Event Analysis Cont. ● What Happened? ○ Even logs are designed to provide very specific information about activities that occurred on the system. ○ Items like Event IDs and Event Categories help to find relevant events ○ Event Description can provide more information of its nature ● Date/Time? ○ Timestamps are key in event logs. ○ The provide a temporal context of the events ○ Can also help narrow an investigators focus. Event Log Analysis Cont. ● Users Involved? ○ Everything done within Windows is done using the context of an account ○ We can: ■ Identify references to specific users ■ Information about the Windows OS activities via special accounts like System and NetworkService.
    [Show full text]