LOGbinder Blog

Updates, Tips and News   RSS Feed  

Meet Randy at HP Protect 2015 and learn about our new products

Mon, 24 Aug 2015 11:13:07 GMT

Most of the people who read our newsletter know the LOGbinder founder as the guy behind the Security Log Encyclopedia and the voice of the Ultimate Windows Security webinars. Meet him in person and take the opportunity to chat!

Randy Franklin Smith will again be at LOGbinder’s HP Protect booth, this year to discuss the new LOGbinder SuperCharger for Windows Event Collection and our new solutions for Microsoft’s cloud-based products. Organizations having hundreds of servers and thousands of Windows devices will be particularly interested in our SuperCharger product. And the new LOGbinder solutions will not be limited to Exchange 2016, SharePoint 2016 and SQL Server 2016. Microsoft is doing some great things to make Azure Active Directory and Office 365 more visible to security analysts. Which makes for some exciting opportunities that LOGbinder will make possible for security-conscious organizations.

So we’ve got some really cool things to show and tell, and we’re using the HP Protect venue as the place to do it in person. More than a HP marketing event, these days HP Protect is one of the few events where security analysts and their teams from all over the globe come to network and learn. It’s our kind of audience. We usually get to spend time with customers and consultants who truly grok security at HP Protect conferences. This year the conference will be held September 1-4, 2015 at the Gaylord Marriott in National Harbor, MD just across the river from Washington, DC. (click here to jump to HP Protect 2015 site)

We hope to meet you there! We’ll be at booth #412 in the CyberSecurity Hall. You are going to love what you see.

The State of Application Security

Mon, 24 Aug 2015 11:12:18 GMT

In a recent poll of more than a hundred security analysts and database admins, 80% said their organization put equal or greater emphasis on network and OS auditing than on database security audits. (35% said database monitoring was less important than network or OS audits.) This seems inverse of what it should be.

It would be so awesome if organizations would simply prioritize their audits to the applications where all the sensitive information is stored.

Help us get the word out! It’s not hard to get application security intelligence to the SIEM where it belongs. The right tools make it dead simple:

  1. Choose the relevant LOGbinder application(s), install and configure in minutes, and
  2. Start watching the security events roll in to the SIEM console.

Organizations that don’t have a SIEM need to add a preliminary step and pick the SIEM that has LOGbinder integration already built-in

SQL Server auditing tutorial with Q&A

Mon, 24 Aug 2015 11:12:01 GMT

Monitoring the sensitive data inside an organization is critically important. But to do a good job of it, analysts and admins need to learn the framework of SQL auditing and get some insider tips. We sponsored a webinar to meet this need this week and received a heartening response with registrations and a lot of good questions during the live event. If you missed the webinar or didn’t get the opportunity to register, you can still get the recorded version. It’s worth the hour it will take to see the demo and hear the answers to the attendee’s questions.

LOGbinder use case (Simplified edition)

Mon, 27 Jul 2015 13:51:01 GMT

If an organization has a SIEM (any SIEM) and also has Microsoft’s Exchange, SharePoint and/or SQL Server applications, LOGbinder is required. No SIEM can get the security audit logs from those applications via normal collection methods. What does this mean in real-world terms? And why does it matter, aren’t Operating System logs, packet data and network traffic sufficient?

Some applications make it dead simple to audit. They push the events in plain-text directly to the Windows Event log or a custom application log. Not so the enterprise Microsoft applications Exchange, SharePoint and SQL Server. They do a great job of generating the appropriate events. But they have a unique way of storing them. And they do not make them easy to read and understand. Each of the 3 applications have differing reasons for why this is true and we have published extensive information about this over the years. See www.logbinder.com/resources for the highlights.

By the way, some SIEM solution providers will tell you that their SIEM collects the needed logs via a free collector, but this is not fully the case. Some organizations may be satisfied with a partial collection of the events (which may not be the security events), and they may not require that the event data be understandable or even intelligible. In our experience most organizations are unhappy with such collectors and eventually improve their security intelligence via LOGbinder.

Application security intelligence may be the only thing that truly matters

The logic is very simple. The bad guys’ ultimate goal is information. Operating system logs, net traffic—that’s just data. Therefore:

  1. What causes real harm and embarrassment is when information – that can only be stored inside applications – is breached.

  2. The only way to know what’s happening inside the application is when the application is telling you.

    1. Only Exchange can tell you that John is reading the CEO’s mailbox. Or that a privileged user changed permissions on the CEO’s mailbox.

    2. Only SharePoint can tell you that Bob is downloading a significant percentage of documents in a sensitive library.

    3. Only SQL Server can tell you that Alice changed permissions on the confidential data table(s).

    4. Only the application can tell you that an external APT is downloading mass downloads of content data.

So that’s all the use-cases distilled into a very clear and simple concept. Application security intelligence belongs in the SIEM. And at this point, the only way to get it from Exchange, SharePoint and SQL Server is with LOGbinder software.

Browse our solutions pages (click the Solutions tab up top) or drop us a line to get information specific to your use case. We would love to hear from you!

New technical updates posted and available for customers with current maintenance and support contracts

Mon, 27 Jul 2015 13:43:27 GMT

Within the last few weeks we posted new versions of our software containing features and improvements to all 3 of our applications. Two major features will bring immediate performance benefits:

  1. Split Syslog output if over 100mb. Prior to this update, LOGbinder started a new Syslog output every day (with the file named appropriately), but some organizations’ audit activities would generate more than 1GB of data in a day. This large output file size caused problems. So, we updated all 3 of our applications to create a new file after every 100mb of output and creating a file name suited to this new schema.

  2. Streamlined internal audit request and delivery process. To protect the monitored application’s performance and stability, LOGbinder carefully manages the process by which it requests audit log data. Persistent audit log demands can cause harm to the application. We have released an update to all 3 of our products that adds further refinement to the audit request technology by improving the calculated times for audit request and processing. The net effect is reduced resource demand on the monitored application while maintaining delivery speed and audit integrity.

The new updates are available via the website’s download resource page. Customers with current support and maintenance contracts may download and apply these new updates at no additional charge.

previous | next

powered by Bloget™