Symtrex Inc.

Cyber Security Specialist

Call - 866-431-8972 | Send an Email | Request a Quote
Visit Us On FacebookVisit Us On TwitterVisit Us On Linkedin

Profile

 [metaslider id=2951] … Read More

  • Home
  • Profile
    • Contact Us
    • Security News
    • White Papers
  • Services
    • Compliance Regulations
      • PCI DSS Suite of Products
      • HIPAA/Hitech
      • SOX – Sarbanes Oxley
      • DCID 6/3/NISPOM Chapter 8/JAFAN DoD
      • NERC/FERC
    • Industry Consulting and Implementation
      • Banking and Financial
      • Energy/Utilities
      • Healthcare
      • Retail/Hospitality
    • Security Assessment
  • Security Solutions
    • Sophos
    • Endpoint Security Solutions
      • Bitdefender Business Solutions
      • Sophos Endpoint Protection
    • Forensic Solution – Threat Hunter
    • Network Access Control
      • NetShield
        • NetShield
    • NGFW – UTM – Perimeter Security
      • Sophos Network Protection
    • Security Awareness Training
      • KnowBe4 – Security Awareness Training
      • Sophos Phish Threat
  • White Papers
    • Sophos Webinar Series
  • Security News
    • Blog
    • Sophos Webinar Series
  • Free Security Tools

Average cost of a data breach up 12.5 percent among Canadian Firms

2016/07/05 by admin

IT World Canada – Howard Solomon

Canadian CISOs who want more hard data to convince the C-suite and boards to devote more resources to cybersecurity have a new report to show.

If a study of 24 Canadian organizations is accurate, the total cost over a recent 12 month period of a breach of over 1,000 records went up 12.5 per cent compared to 2014 to just over $6 million.

Another way of looking at it is the average cost per record stolen or lost went up 10.6 per cent to $278 compared to the same period the year before.

These numbers come from a study released last week by the Ponemon Institute that was funded by IBM. The costs were based upon estimates provided by participating victim organizations.

The report is part of an annual global study of breaches in 13 countries (United States, United Kingdom, Germany, Australia, France, Brazil, Japan, Italy, India, the United Arab Emirates, Saudi Arabia, Canada and, for the first time, South Africa), which last year covered 383 organizations. The average cost of a breach across all those firms was US$4 million.

Importantly, the study included the cost of losing customers: Of the Canadian companies studied, for those that lost less than one per cent of their existing customers the average total cost of a breach was $4.77 million, well below the global averae of $6.03 million. When companies had a churn rate of greater than 4 per cent, the average cost was $7.88 million.

There are two cautions: First, Ponemon admits that 24 firms is a small sample for this country, and second, only organizations that suffered a breach of between 1,000 and 100,000 lost or stolen records in 2015 were counted – meaning Ashley Madison isn’t there. That way catastrophic incidents don’t skew the results.

The number of Canadian breached records per incident in the study period ranged from 4,800 to 70,998 and the average number of breached records was 21,200.
“Over the many years studying the data breach experience of more than 2,000 organizations in every industry, we see that data breaches are now a consistent ‘cost of doing business’ in the cybercrime era,” said institute head Larry Ponemon. “The evidence shows that this is a permanent cost organizations need to be prepared to deal with and incorporate in their data protection strategies.”

The report has other interesting numbers:

–It took more than five months to detect that an incident occurred and almost two months to contain the incident;

–54 per cent of the Canadian data breaches studied were caused by malicious or criminal attacks, 25 per cent were caused by human error and 21 per cent by system glitches. Companies that experienced malicious attacks had a per capita data breach cost of $304, which is above the average for all organizations studied. In contrast, companies that experienced system glitches ($250) or employee negligence ($246) had per capita costs below the mean value;

–The more records lost, the higher the cost of the data breach. The cost ranged from $3.59 million for data breaches involving 10,000 or fewer lost or stolen records to $6.88 million for the loss or theft of more than 50,000 records;

–Notification costs increased. These costs include IT activities associated with creation of contract databases, determination of all regulatory requirements, engagement of outside experts, postal expenditures and inbound communication set-up. The average cost increased from $0.12 million in 2015 to $0.18 million in 2016;

–Lost business costs increased. This cost category typically includes the abnormal turnover of customers, increased customer acquisition activities, reputation losses and diminished goodwill. Among all the 383 companies studied these costs increased from an average US$1.99 million in 2015 to US$2.24 million in 2016 — that’s of the overall $4 million average cost.

“The biggest financial consequence to organizations that experienced a data breach is lost business,” says the report.

Both direct and indirect per capita costs increased significantly. The indirect cost of data breach includes costs related to the amount of time, effort and other organizational resources spent to resolve the breach. In contrast, direct costs are the actual expense incurred to accomplish a given activity such as purchasing technology or hiring a consultant.

Direct expenses include engaging forensic experts, outsourcing hotline support and providing free credit monitoring subscriptions and discounts for future products and services. Indirect costs include in-house investigations and communication, as well as the extrapolated value of customer loss resulting from turnover or diminished customer acquisition rates.

 

 

Filed Under: Advanced Persistent Threat, antivirus, compliance, CyberThreats, endpoint, industry, Log Management, LogRhythm, Malware, Network Access Control, Network Monitoring, PCI, Products, Security News, Snare, SolarWinds, Sophos

Snare Enterprise Agent Update

2016/07/04 by admin

Intersect Alliance has released the following updates to their Enterprise Snare Agents, plus a new MSI package:

Enterprise Windows Agent V 4.3.6 – This release dealt with the following issues (download complete release notes):

  • Snare Unable to handle network destination starting with numeric value – There was an issue how a network destination is checked for IP address or DNS name. Due to the issue a DNS name starting with a numeric value can be treated as an IP address. Due to this issue, the network destination wont get used correctly to send the logs. This issue only affected sites where the destination address included a DNS name starting with a numeric value. This issue is fixed in this release and now the agent properly distinguishes between a full IP address and DNS name that begins with a numeric value.
  • Fixed same expression comparison – The agent was not correctly processing the 4739 “Account Administration” and the 4707 “A trust to a domain was removed” events internal expression matching via the objective radio buttons. If individual  matching was configured under the any event option then it would still be collected. This patch resolves the collection of these events.
  • Potential memory allocation error in Debug Msg – There was an issue with the memory allocation handling while sending the heartbeat. The issue is more prevalent on machines low on virtual memory. This issue can cause the agent to enter in an infinite heartbeat sending loop and consequently can cause denial of service attack on log collector destination(s). This issue is fixed in this release and now memory allocation error is correctly handled.
  • Potential SnareCore Crash Issue – There was an internal issue with the event log source name checking. Due to this issue the  Snarecore.exe process can crash when event log source name is is set to a null value from the event data which was unexpected from the Windows API. This issue is fixed in this release and now Snare properly handles the issue; logs the warning if event log source name is set to a null value. As a compensating process, as Snare internally knows the name of the event log source name from where it is pulling the events it will use that name as the log source if the Windows API replies with a NULL value.

Enterprise Epilog for Windows V 1.8.6 (download complete release notes) and Enterprise Agent for MS SQL V 1.4.7 (download complete release notes)

  • Snare Unable to handle network destination starting with numeric value – There was an issue how a network destination is checked for IP address or DNS name. Due to the issue a DNS name starting with a numeric value can be treated as an IP address. Due to this issue, the network destination wont get used correctly to send the logs. This issue only affected sites where the destination address included a DNS name starting with a numeric value. This issue is fixed in this release and now the agent properly distinguishes between a full IP address and DNS name that begins with a numeric value.

Enterprise Agent for Linus V 4.1.9 – New Feature was added (download complete release notes)

  • A user should be able to create their own audit.rules file and the Linux Agent should be able to monitor any events it generates – Added the ability to specify a single rule objective with an ‘Any Event’ objective type and use a wildcard (‘*’) which indicates the agent will process all events coming from the audit subsystem. This is useful if the user wishes to use the agent but use a custom audit.rules file.

These updates are now available within your client area.  If you have difficulty accessing please contact our office with your maintenance number.

 

Filed Under: Log Management, Products, Security News, Snare, Snare Agents

Snare Product Suite Updates – Agents and Server

2016/02/22 by admin

Snare LogoUpdates to the Snare Agents have been released and are available for our clients.  The updates include a patch for a vulnerability that was discovered in the Open Source Snare For Windows Agent, and also exists in the Enterprise Agent for Windows.  This vulnerability can trigger the agents to display the Cross Site Scripting (XSS) attack from the agents latest events screen.  The exploit uses smbclient from a Unix machine to generate a false userid that contains JavaScript and does not require any authentication to generate the event.  For more information on this exploit please click here.

The vulnerable products include the Enterprise Agent for Windows, MS SQL and the open Sourced Agent for Windows.  At this time there is no patch for the open sourced Windows agent.

Also released is the Snare Server Version 7.1.0, which also provides for a patch of the latest libc DNS vulnerability.

All release notes are available within the client areas or click here.

Filed Under: Products, Security News, Snare, Snare Agents

Snare Server version 7.1 Coming Soon

2016/02/18 by admin

Version 7.1 is to be released in February 2016, with the following new features:

  • The Snare Server collection and reflection service has been significantly updated. The Snare Server can now perform format conversion, apply filters to events on a per-destination basis, and can also search/replace event contents on the fly. The core of the collection services and the reflector has been rewritten in C++ for speed. Sample use-cases include:
    • Sending events that are marked only with a particular criticality to a specific destination.
    • Sending Windows events to a destination SIEM server, and unix events to a syslog server.
    • Changing syslog RFC 5424 events to RFC 3164 format, to accommodate a SIEM server that can only handle the older format.
    • Switching events from using a TAB delimiter, to comma.
    • Redirecting all events that include a particular username, to a separate SIEM server for analysis.
    • Forwarding any firewall logs that include a particular IP address range, to another system for deep analysis.
  • Update and Removal of “Trusted CA root Certificates” is available from the Configuration Wizard.
  • Snare Server now supports LDAP/SSL, LDAP/TLS and SASL/TLS authentication.
  • A SNMP trap server can be configured in the Snare Server wizard. A new feature has been added to the Real Time Alerts function in the objectives that so a SNMP Trap will be sent to the server as defined in the wizard when there is a match for the Real Time objective.
  • A new “Auto-Remove Data” objective under “System -> Data Backup” is now available. This objective allows the Administrator to create tasks with a range of selection criteria, that are designed to automatically remove data from the Snare Server archive. Selection criteria include: By agent, by date, and by log type. Regular expressions, and date-delta options are available. Each Auto-Remove task has a specific schedule that determines when it executes.
  • TLS Server certificates associated with the TLS collection service should now use the fully qualified hostname of the server on which they are installed. A freshly installed system will use the fully qualified certificate format.
  • Six new Oracle Objectives have been added to the Snare Server, including:
    • Start-up and Shut-down of the Oracle application
    • Database Global Activity
    • Admin DBA Activity
    • Oracle Security
    • Oracle Startup / Shutdown
    • Password Changes
    • User Activity
  • Seven New Microsoft DNS server logs Objectives with Malware domain detection have been added in the Application Audit/Windows Log Data menu tree:
    • DNS Log
    • DNS over TCP empty
    • DNS over UDP
    • DNS search IP
    • DNS Server Failures
    • Malware Domains
    • Non Existent Domains

Filed Under: Products, Security News, Snare

Snare Agents Advisory – Agent Denial of Service

2015/06/30 by admin

New agents released on June 30th please see release notes available at the client login page

A vulnerability exists in some versions of the Snare Agents, which can be triggered to terminate the Snare service. The exploit attempts to overflow an input buffer in the remote management interface, and can be performed by an unauthenticated user using a custom crafted URL.

Impact
This vulnerability does not allow the attacker to gain privileged access, but it does affect the operation of the agent.

Vulnerable Products
This affects the following the Snare Enterprise products:
– Snare Enterprise Agent for Windows
– Snare Enterprise Agent for MSSQL
– Snare Enterprise Epilog for Windows
– Snare Enterprise Epilog for Unix
– Snare Enterprise Agent for OSX
– Snare OpenSource Agents

Countermeasures
– Disabling the remote control interface (GUI) will block this issue. Note that disabling the remote control interface will also disable the ability of the agent management console, to manage the affected agent.
– Appropriate network firewall controls, will limit the sources from which this exploit can be triggered.
– Some Unix operating systems can detect the attack as a potential SYN flood and block the source system.

Vulnerable Versions
The following versions of Snare Enterprise agents, and all versions prior to these versions, should be considered vulnerable to this issue:
– Snare Enterprise Agent for Windows v4.2.12
– Snare Enterprise Agent for MSSQL v1.3.4
– Snare Enterprise Epilog for Windows v1.7.12
– Snare Enterprise Epilog for Unix v1.5.5
– Snare Enterprise Agent for OSX v1.1.3

All versions of the listed OpenSource/SnareLite agents, and prior versions, should be considered vulnerable to this issue:
– Snare OpenSource Agent for Windows v4.0.2.0
– Snare OpenSource Epilog for Windows v1.6.0
– Snare OpenSource Epilog for Unix v1.5.0

Patched Versions
The following versions of the Snare Enterprise agents have been patched, and are no longer vulnerable to this issue:
– Snare Enterprise Agent for Windows v4.3.0
– Snare Enterprise Agent for MSSQL v1.4.0
– Snare Enterprise Epilog for Windows v1.8.0
– Snare Enterprise Epilog for Unix v1.5.6
– Snare Enterprise Agent for OSX v1.1.4

For users who are running the OpenSource/SnareLite agents, it is recommended that the remote control interface be disabled. There is no schedule for fixes to the OpenSource/SnareLite agents at this time.

Filed Under: Log Management, Security News, Snare, Snare Agents

  • 1
  • 2
  • 3
  • …
  • 6
  • Next Page »

Let us help answer any questions you may have

requestmoreinformation.fw

Security News and Updates

  • Was my information part of a breach?
  • Phishing and stolen credentials
  • Ransomware is the Biggest Threat for Small to Medium Businesses

RSS SecurityWeek

  • Italy Temporarily Blocks ChatGPT Over Privacy Concerns
  • FDA Announces New Cybersecurity Requirements for Medical Devices
  • Report: Chinese State-Sponsored Hacking Group Highly Active

Contact

  • Contact Us

Request More Info

  • Request Quote

Site Map

  • Site Map

© Copyright 2016 Symtrex Inc. ; All Rights Reserved · Privacy Statement