Installing Suricata to FreeBSD

I’ve been working through a Suricata course which details how to use Suricata on a Ubuntu base. Since I tend to work more with FreeBSD, here are my notes on how to install Suricata on FreeBSD.

Launch a working FreeBSD system, login, launch a terminal session, then elevate to root privileges. Then run the following commands:

  • freebsd-update fetch
  • freebsd-update install
  • pkg install suricata
  • vi /etc/rc.conf
    • suricata_enable=”YES”
    • suricata_netmap=”YES”
  • vi /usr/local/etc/suricata
    • change all occurences of eth0 to the actual interface identifier, determined by ifconfig
  • service suricata start

Then we can check the health of our installation:

  • suricata –build-info
  • suricata -V – Display version information
  • /var/log/suricata – Log file location, check the contents and ensure that they are growing
  • /usr/local/etc/suricata/suricata.yaml – Configuration file

Interesting Requests for Comment

This post is intended to list Requests for Comment (RFCs) that I find interesting, find myself referring to, and think that I should study.  Hopefully it won’t become an exhaustive list of every RFC used in our networks today.

RFC 1034 – Domain Names – Concepts and Facilities

RFC 1035 – Domain Names – Implementation and Specification

RFC 1149 – A Standard for the Transmission of IP Datagrams on Avian Carriers

RFC 1855 – Netiquette Guidelines

RFC 1925 – The Twelve Networking Truths

RFC 4033 – DNS Security Introduction and Requirements

RFC 4034 – Resource Records for the DNS Security Extensions

RFC 4035 – Protocol Modifications for the DNS Security Extensions

RFC 5905 – Network Time Protocol Version 4: Protocol and Algorithms Specification

RFC 8140 – The Arte of ASCII

RFC 8484 – DNS Queries over HTTPS

RFC 8499 – DNS Terminology

More to follow!

Thotcon 0x9

Last week I attended Thotcon 0x9 in Chicago and heard a few presentations that made me think. The first was the keynote by Cory Doctorow entitled “The war on general purpose computing is an existential threat to infosec – and the world!”. He made an excellent case for the work of the Electronic Frontier Foundation (EFF) and has changed my opinion from one of little respect to one of strong need for their efforts.

The second was by Wendy Nather entitled “Denial of Trust: The New Attacks”. During this speech she raised the idea that companies (or corporations) consider the loss of data to be akin to Acts of God. This reminded me of a time when some people banded together to fight the deaths of 30,000 Americans per year due to boiler explosions – which the manufacturers attributed to Acts of God. Their efforts formed the American Society of Mechanical Engineers and ultimately led to the National Boiler Code and the licensure of Professional Engineers in the United States.

The third presentation by Karen Elazari was titled “Hackers: Still the Internet’s Immune System?” She makes the excellent point that hackers may be the most effective group opposing the domination of the Internet, collection and access to Big Data, and manipulation of the People today. At some point I heard the question of who will hold governments and companies to account if not hackers? The follow up becomes whether hackers are willing and able to organize in some way in order to maintain their effectiveness.

Lastly, “the Hacker Community Must Always Exist” by Chris Wysopal gave an enlightening history of the adversarial relationship between hackers and industry. He questioned the continued effectiveness of this relationship as technologies such as medical devices and blockchains are deployed, and whether there can be enough hackers to keep up with new technologies.

Altogether these speakers have motivated me to become a better Security Engineer and to make some effort to help find the answers. I see many parallels in the development and use of steam power 140 years ago and our problems in technology today. The scale is huge, but if enough people work together I believe that the answers can be found.

The meaning of IP addresses versus host names

An article in the November 2017 issue of The Internet Protocol Journal raises the excellent point that IP addresses have been replaced by host names in defining coherence to a network.

This week I’ve discovered that IP version 6 reserves an address space that is intended for local communications, normally within a site. This space is defined in RFC 4193, and goes on to explicitly state a design objective: the addresses are not designed to aggregate.

Our IT brethren are being driven away from aggregating addresses by the rise of mobile devices and the internet of things. Within the commercial IT world, host names are replacing addresses in allowing technicians to find specific assets, troubleshoot particular problems, and maintain environmental awareness. Our controls IT world is still working with aggregated addresses and organizing our systems using the addresses.

If the controls environments continue to use Commercial Off-The-Shelf components and to rely on Corporate IT for design and high-level support we need to begin migrating our designs from system organizations built around addressing and shift to comprehensive naming and name resolution services.

The Practice of NSM References

I’ve resumed reading The Practice of Network Security Monitoring, by Richard Bejtlich.  In the past I’ve stalled once Security Onion is installed as I haven’t had a good place to implement it and continue learning how it works.  So yesterday I skipped ahead to Chapter 9, NSM Operations and read the chapter.  I was surprised to see a bunch of promising references, so I’m going to list them here for future use along with a couple of choice quotes.

First, an opening quote:  “Too many security organizations put tools before operations. <snip> A tool-driven team will not be as effective as a mission-driven team.  When the mission is defined by running software, analysts become captive to the features and limitations of their tools.” [The Practice of Network Security Monitoring, Richard Bejtlich, page 185]

A textbook reference:  Incident Response and Computer Forensics, Third Edition (McGraw Hill Education, 2014 – Jason Luttgens, Matthew Pepe, Kevin Mandia)

Finally, a closing quote:  “…intruders conduct campaigns, and CIRTs defend in waves.” [The Practice of Network Security Monitoring, Richard Bejtlich, page 200]