Device Management
The Access Manager is an integrated module that provides a secure method to store device access information. The first time DAAT is launched it will prompt for an Access Manager password, this password can also be used to encrypt and decrypt device access files. Each device uses an encrypted access file to optionally store the address, user, password and file path.

When launched from the Workbench, three tabs are displayed; Password, Access and Devices. The Password tab is used to change the Access Manager password and will also update each device access file that uses the same password for encrytpion. Note: All device access files must be decrypted before the Access Manager password can be changed. The Access tab contains default device access information for new devices or global user credentials to override individual device user credentials. The Device tab decrypts all device access files, provides quick acess to your devices and displays access status using the following color codes.

The device access information was successfully decrypted and will be used when executing software and commands.
The device access file exists but doesn't contain remote access information.
The device access file doesn't exist or cannot be decrypted.

The Access Manager is displayed as Device Access when launched from a Device tab because the access information is specific to the device. The device access file encryption password can be changed from the Password tab and the Access tab displays and updates the encrypted device access file information. The device access password can be copied to the system clipboard by clicking on the image next to the password field.

When a device is first accessed, the access file is decrypted and the values can be used when running software and commands. If a device access file cannot be decrypted using the Access Manager password, the user is prompted to supply the correct decryption password. By default the cryptography used is AES (Advanced Encryption Standard) but can be changed to TEA (Tiny Encryption Algorythm).

Accordion device tree nodes use a right-click context menu to update settings, load the Access Manager or provide quick console access.

Software and Command Automation
DAAT is configured with a proven Open Source tool-set that many Systems Administrators use on a daily basis to manage remote devices. These tools are included to provide automated remote console/desktop connections and remote command execution. New software can be added by providing the path (relative, absolute or system path) to the application and configuring the parameters to define how it will be used. Using the system path, the Windows script hosts (cscript and wscript) have been included to support and leverage any existsing (JS and VB) scripts that you may run on a regular basis.

Software that is configured with a remote attribute value can be used to execute software against remote devices. Included are both RemCom for executing remote Windows commands and Plink for executing remote commands via SSH. When a successfull connection is created to a remote Windows device using RemCom, a connection to the device is created that can be leveraged by applications. Connections to remote Windows devices can be managed using the Cache Connection module or created by successfully executing a RemCom command against the remote device.

Commands take advantage of pre-defined software or it can be defined within the command configuration parameters. The arguments to execute the application with are also defined within the command parameters and can include dynamic variables (address, user, password and file) that will be updated with device access information before execution. For example, the following DAAT command will be automatically updated with the device access address before being executed.

compmgmt.msc /computer:#access.address
compmgmt.msc /computer:

All standard output and errors produced by command-line applications is logged and can be reviewed and removed at any time.

Similar to Windows Run... functionality; software and commands can also be executed ad-hoc using the Run... option from the Toolbox Software or Commands menu. When Software is configured with a remote attribute value, the Commands Run... menu is automatically updated with the item.

Custom Module Integration
Created using the Sencha Ext JS 3.3.1 library and XML, DAAT leverages many open source projects including several Sencha community developed extensions and components. In many cases these extensions and components are reusable and can be easily extended or integrated within your own custom module. API documentation for both DAAT and Ext JS is available from the Help -> API Documentation section of the application.

The pre-configured modules are listed below with a brief description.

 Access Manager
 An integrated module that provides a secure method to store device access information.
 Cache Connection
 Using the decrypted device access file, this module will cache or remove cached device access connections.
 Secure Text
 Demonstrates the encryption and decryption used to secure device access files.
 A welcome window that displays a random message and an option to not display at start up.

If you are familiar with Ext JS, creating a new module consists of extending or creating a new component.

Log File Transformations
Extended Ext JS components are used to transform log file data into feature-rich DataGrids, Windows, etc... Incorporate existing xsl transformations within Ext JS components to reduce development and integration time while providing consistent and robust log file presentations. Currently, there are two supported transformation types (DAAT and Nmap) to transform related logs in Text, HTML and XML format. Adding new transformation types can be simple for basic log files and custom Ext JS components can be implemented to fulfill unique presentation and log file requirements.

Log files when added are associated with a transformation group (DAAT or Nmap) and can be accessed from the Toolbox or the Logs accordion panel. Transformation log files are grouped by the type of transformation (txt, htm, xsl and ext) which is defined in the transformation profile. XML log files are added to both the xsl and ext transformation types if they are defined. Transformations can be executed from either the Toolbox or from the Logs tree panel. Shortcuts can be created for individual log files to be accessed from within the Toolbox.

To demonstrate Nmap log file transformations, a sample xml log file has been added. The sample xml log file is available at: Software and command log files generated by DAAT are saved in xml format and can be added to the DAAT transformation profile if desired.

When a transformation log file is removed, the log file is not deleted but removed from the transformation profile.