Additional User Security Standards

Additional User Security Standards

Opmantek is excited to announce improved security monitoring across our software suite through best-in-class ISO 27001 Access Control.

 

This latest update enables administrators to access three new core functions:

  1. Limit setting on concurrent Opmantek software sessions per user
  2. Set automatic account locking for inactive users
  3. Track user login and access history

 

Take advantage of these new features right now by downloading the latest version of NMIS. 

Technical documentation of this new feature can be found here.

opEvents v3.2.2 New Release

opEvents v3.2.2 New Release

opEvents 2.6.1 has now been officially released.

opEvents has had the ability to perform troubleshooting and remediation scripts when an event occurs; this is quintessential to remediating events without requiring intervention. However, what about when you want to run these scripts on events that have not been remediated?

With the introduction of ‘Programmable Action Buttons’ engineers can now perform these actions ad-hoc and all the resulting information is stored in the event itself. Any script that has been created, including the ones that are supplied by Opmantek, can have an actionable button created to perform it, you can even take this a step further and push tickets into your ticketing system from these events. This further enhances opEvents as an engineer focused support platform.

Download opEvents today and continue your automation journey.

Open-AudIT V4.0.0 New Release

Open-AudIT V4.0.0 New Release

Open-AudIT 4.0.0 is here. For more information about why we have gone to 4.0.0, please see my blog post Open-AudIT 4.0.0.

WARNING – See blog post above about migrating as you cannot upgrade to Open-AudIT 4.0.0 (hint, it’s easy).

A new license will be required if you have a perpetual license. Subscription licenses are unaffected (but may need to be manually copied, see blog post). Contact Opmantek if you require a new license.

Please note (as detailed in the blog post):

  • NMIS9 Syncing has not been implemented for this release.
  • This release is not compatible with older versions of Opmantek products, that were designed for NMIS8.

Open-AudIT Community will (for now) remain at version 3.5.1.

Open-AudIT Professional and Enterprise build on top of Community, so their major version has been increased, as explained in the blog post. So if you install version 4.0.0 and switch to the Community GUI you will see version 3.5.1 there. DON’T PANIC, this is intentional (smile)Linux SHA256: 7e035e6af2260d7fc6a93fdcd6d1ba1193ce09ae7f704031c552daa3c3ff194b

Linux md5sum: 7c5318948aa9c1733396d2f63e27f5ea

There are no major changes for 4.0.0 from a users perspective. The minor changes and fixes are detailed below.

Version Type Collection Description
Professional Bug Tasks Menu link to scheduled reports needed reformatting (user now required to provide quotes when using the IN keyword).
Professional Bug Tasks Add ‘required’ indicator to attributes on tasks_create form.
Professional Bug LDAP Servers Add ‘required’ indicator to ldap_servers::create template for ‘secure’ attribute.
Professional Improvement Attributes Add icons to attributes::read template for devices and locations.
Professional Improvement Users Only show Cloud text to Cloud users on users_read template.
Professional Task Integrations Remove ‘integrations’ from menu for initial ABI4 release.
Professional Task Configuration Change nmis_url in database config to NMIS9 URL.
Professional Improvement Discoveries Add links to individual discovery scan options in help text on discoveries::create template.
Professional Improvement Roles Add roles.ad_group to roles::collection template.
Professional Improvement Users Add error message to auth_log when user in htpasswd, but not OAC.
Professional Improvement Discoveries Add hover text to discoveries_read left side menu.
Professional Improvement NMIS Provide same functionality for OAP/E as per OAC – Import Devices from NMIS8 and NMIS9.
Professional Bug Baselines, Roles Add baselines endpoint to roles::read and roles::create templates.
Community Bug Networks Bad SQL (still worked on Ubuntu 18.04) in networks::collection.
Community Improvement All Allow for URL Encoded HTML Entities in $id when searching to match name -> id.
Community Improvement Configuration Allow for config.json UUID retrieval.
Community Improvement Users Language selector added zh-tw. Merge pull request #6 from jasoncheng7115/patch-2
Community Task NMIS Ensure we can import nodes from NMIS 9 (as well as NMIS 8).

Additional User Security Standards

NMIS 8.7.0G New Release

When an NMIS update comes out, you know there will be a lot of features and upgrades for you to test out and version 8.7.0G meets these requirements.

Some of the highlights of the most recent release include:

  • Installer fixes
  • Model Enhancements
  • Model Improvements
  • Plugin Improvements
  • Collection has been improved
  • Admin Scripts have been amended
  • As well as countless other fixes and improvements

The model enhancement and improvements are always well recieved, they are a key function of NMIS. If you would like to customize any of these, watch this webinar presented by Opmantek CTO Keith Sinclair that covers device modelling.

Full release notes can be found – here!

Open-AudIT V4.0.0 New Release

Open-AudIT V3.3.0 New Release

Hi All,

Release 3.3.0 of Open-AudIT has some amazing new features, read on for the details. The release notes are available as usual, here – Release Notes for Open-AudIT v3.3.0.

Configurable Device Columns

From 3.3.0 onward, when you view the list of devices (Manage → Devices → List Devices), you’ll notice a small additional control on the upper right. Click it and you’ll see a list of available columns you can display. Click a column name and it will appear. Click a bold column name and it will disappear. If you want that set of columns as your default, click “Save as Default” and every time you view the device list, those will be your default columns. You can also click “Reset to Default” (if your columns are different) to reset them. The default list of columns is in the configuration under the name devices_default_display_columns. If you are seeing a n unacceptable slow down viewing the page, you might wish to limit the retrieved (but not displayed) columns. This is also in the configuration under the name devices_default_retrieve_columns. See the screenshot below.

devices collection 01 - 700

Device Components

Also on the Devices list page, you’ll notice a bar at the very top with a drop down arrow on the right. Click the arrow and you’ll see a list of component types. Click one to see a list of all those items. Be aware this list may be very large so we restrict it to the first “database_show_row_limit” (configuration item) entries. Increase that number to see more. At this stage we have not implemented a GUI for paging, but it is available using the API (or adding to the URL), by specifying limit and offset. So a valid URL might be (for instance) http://SERVER/omk/open-audit/devices?sub_resource=software&limit=200&offset=100. See the API documentation for more information – The Open-AudIT API. The following pages allow you to click links to see this specific entries details, all those entries on a device or the device details itself.

devices collection 02 - 700
devices collection 03 - 700

Comparing Your Database Schema

There is a new entry under menu → Admin → Database called Schema Compare. Running that will show you the schema as it is in your running database and compare it to the schema as shipped with Open-AudIT. If there are any differences, just post them to Questions and we can help you out. For supported customers, just log a support request and we’ll assist ASAP.

Change Log Improvements

Time has been spent to minimize false positive Change Logs being generated. As well as that, we have added two buttons on the Device Details screen (under the left side Actions menu) to remove Change Logs and remove Audit Logs. Using these may help improve database performance where these records are not required. Don’t forget you can always clear the entire tables using menu → Admin → Database → List Tables, clicking either table and hitting the Delete button. And don’t forget about our new configuration items for keeping non-current items and creating change logs. More information on these can be found – here.

Deleting Devices

There is now a configuration item named device_auto_delete. If set to ‘y’ (it is set to ‘n’ by default) when you change a device’s status (either individually or using Bulk Edit) you will get a regular warning “Are you sure?” and if you answer yes, the device and all it’s details will be completely removed from the database. Not just flagged with a status of deleted.

New Discovery Process and Improvements

With the coming release of Open-AudIT 3.3.0 we have implemented a new discovery process that scales even better than previously. Even faster discovery times!

The Discovery Queue

With 3.3.0 we have changed to using the discovery queue, not on a per discovery basis as previously, but on a per IP basis. From 3.3.0 onwards, when you click “Execute Discovery”, the following happens behind the scenes:

  • The server starts a script that calls /util/queue and instantly returns to the web user (or the API user). It starts the shell script and does not wait for a response before returning.
  • The user then continues on using the web/API as per normal.
  • The shell script calls util/queue – this endpoint only accepts requests from localhost. The resulting function does the following:
    1. Check the config for the queue limit. If this has been reached, exit. If it has not been reached, continue.
    2. Pop an item from the queue (locking the queue table as it does so). The item is read from the database, then deleted. If no queue items exist, exit.
    3. Spawn another script to request util/queue.
    4. Execute the item – which on the first time is always “run discovery on subnet”.
    5. When finished, return to #1.

There are (currently) two types of queue entries. The overall discovery entry, and an entry for each IP to be scanned. The second entry is created by the first. So we run the initial discovery, and for each IP we need to scan (that responds, if that option is chosen), we create another entry to scan that device.

We no longer use the discover_subnet.sh or discover_subnet.vbs scripts at all. We now call Nmap directly from within the Open-AudIT code, which frees us up to have one and only one routine (versus a bash and vbscript). It also makes it easier to code – PHP has much easier to use text parsing than bash and vbscript (in my opinion).

Because of the above, we have created a new configuration item called “discovery_limit” and set it to 20 by default. This means when a discovery is run, it will spawn up to 20 processing instances in parallel. Because of this parallel processing of target IPs, discovery is $discovery_limit times faster. Well, not quite, but you get what I mean. The old way ran a discovery and for each target, sequentially, started a scan. Several scans were run at once, but it was still waiting for an Nmap scan, before handing off to PHP to complete the rest. The new way completes the initial scan and loads all resulting devices into the queue to be processed in parallel. At the end of the day, it’s just so much faster.

Sudo SSH Key and Password

Previously we only had support for an SSH Key that used a password, but where that password was also used for sudo. That is obviously not optimal, so as at 3.3.0 you can add a specific ssh key password and a sudo password.

Additional Nmap Option

We have also added a new option to discovery scan options – open|filtered. Previously we used the “filtered” column to check for open|filtered. This change aligns the discovery scan options with Nmap return strings.

Auditing Time Reduction When Using sudo

When auditing a device using sudo, we no longer have to wait for the configuration item discovery_ssh_timeout (previously 300 seconds) to timeout. We now check every 2 seconds for our response and when received, proceed. This has made another large difference to audit times when using sudo.

Windows Users Apache Service

As well as this, there has been a change targeted specifically to Windows Open-AudIT Servers. Because of the issue’s we have run into using the default service account, you will now get a big warning stating you should change the service account to a “real” account. This is because by default the service account cannot access network resources. IE – copy the audit script to thew target and run it. The “old” way of running the script on the Open-AudIT server itself and specifying the target still works and is enabled by a config item – discovery_use_vintage_service, which is set to ‘n’ by default. One reason for this is that the discovery script contains sections that do not and can not work remotely. Think starting an executable. That won’t work as WMI can target the remote machine, but running an executable from the audit script would run it where the script is running – the Open-AudIT server.

The Default Network Address

Because of our new way of running discovery, we no longer need to set the Default Network Address. The scripts are run on the target devices and create a file (as opposed to submit_online=y). That file is then copied to the server and processed, rather than submitted using the URL (that was created from the default_network_address). The only reason to set the Default Network Address for Discovery is if you’re using discovery_use_vintage_service. The now normal use of this is only for the “Audit My PC” functionality.

Auto Delete our Audit Script

Now when discovery runs, the audit script deletes itself on the target, hence we leave nothing present on the target device.

No More “New” Devices Where We Have No Information

We have added a new configuration option called match_ip_no_data. If we discover a device and that IP is already in the database and we have no audit data about that device, assume it is the same device, so do not create another (usually duplicate) device.

SNMP Route Retrieval

We now retrieve the first (configuration item discovery_route_retrieve_limit) routes from a device when using SNMP.

And there’s even more improvements. Make sure you read the Release Notes for Open-AudIT v3.3.0 to stay across it all.

Happy Auditing,
Mark.

Open-AudIT V4.0.0 New Release

Open-AudIT v3.2.2 New Release

So, that was a ride… In testing our new Rules feature worked a treat. In practice, not so much. Most servers (ie, not mine) can’t cope with loading the rule set, even if we break it down to smaller chunks, when processing multiple devices. What to do? What to do? Well we’ve taken a small step back. Rules still exist as a feature, and they still work a treat. But instead of inserting 100,000 Rules into the database, we’ve split them up into four distinct files and implemented them as code only. Hence, no loading all 100,000 Rules, decoding JSON and running them against a device. Now we just load the files and run the statements. Much, much faster and more memory efficient. No load on MySQL, and hence the CPU also drops. No populating a massive recordset and hence the memory drops. The not so good thing – these are no longer editable in the GUI. But it’s not the end of the world. You can still make Rules as you see fit and they will be run after the “default” rules (those in code), hence you can override the “default” rules. So we don’t lose much, but we gain a LOT of performance. We also added a few new Rules for Mac Models.

Apologies for any inconvenience this caused anyone.