{"id":2535,"date":"2020-07-28T09:05:57","date_gmt":"2020-07-28T13:05:57","guid":{"rendered":"https:\/\/zzzptm.com\/wordpress\/?p=2535"},"modified":"2020-07-28T09:05:57","modified_gmt":"2020-07-28T13:05:57","slug":"security-for-all-sizes-whats-on-my-network","status":"publish","type":"post","link":"https:\/\/zzzptm.com\/wordpress\/?p=2535","title":{"rendered":"Security for All Sizes: What’s on My Network?"},"content":{"rendered":"\n
\"\"\/<\/figure>\n\n\n\n

There is so much more to security than:<\/p>\n\n\n\n

1. Find the hackers.<\/p>\n\n\n\n

2. Shut them down.<\/p>\n\n\n\n

First of all, we need to know what, exactly, is on the network<\/a> and what it does and whether or not it should be doing that function while connected without restriction to the rest of the network.<\/p>\n\n\n\n

But before we tackle the question<\/a> of what should be on the network, we need to go about discovering what is on the network, and this can be a journey full of surprises.<\/p>\n\n\n\n

Typically, the start of this investigation<\/a> will involve someone saying that everything that is connected to the network are phones, PCs, access points<\/a>, and the printers. Oh, and also the badge readers. And the security cameras. But that’s it. Besides the barcode<\/a> readers. That’s all, though. Hang on, we also have some digital<\/a> signage…<\/p>\n\n\n\n

At this point, you may now take what anyone has to say about what’s on the network with a grain of salt. It’s time to answer this question for yourself.<\/p>\n\n\n\n

In a small company, you may be able to track<\/a> down all the devices<\/a> by hand during an off hour or two. It’s a great exercise and will prove invaluable for doing troubleshooting.<\/p>\n\n\n\n

In a medium-sized company, this cannot be done alone. You’ll need a few other people to help out. That, or you’ll just do it all over a much longer period of time… however it’s done, you’ll likely also need some form of automation<\/a> of tasks to get all that data collected in a usable way.<\/p>\n\n\n\n

For a large company, this cannot be done alone. You will need tools. You will need a project<\/a> manager. You will also need cross-team cooperation.<\/p>\n\n\n\n

For all of these investigations, you will also need to talk to people that don’t usually talk to folks in IT. You will need to talk to them because they have connected things to the network, the likes of which you have never seen on a network ever before…<\/p>\n\n\n\n

… and watch me talk about those things without once using a catch-all phrase that describes all of them…<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

In the small company, especially one that’s going through initial growing pains, there aren’t enough ethernet<\/a> ports<\/a> in wall outlets. That means, most likely, a cascade of cheap, unmanaged switches<\/a>, also known as “cockroach switches” because when you see one of them, there’s a thousand more, hiding in the dark places of the office.<\/p>\n\n\n\n

Because the switches are unmanaged, finding out what’s connected to them can be a chore. It can be done, but it may involve tracing cables up through holes in the ceiling and then dropping down into a room next door. You might also find the switches themselves in the ceiling space, acting as repeaters so the 100m cable from the main switch can extend into the nearby office<\/a> space that was recently leased out.<\/p>\n\n\n\n

In medium and large companies, even those with plenty of accessible wall ports available, people will bring in their cockroach switches and plug ’em in. Why? Maybe you should ask the developers<\/a> who want to run 7 boxes in their cubicles and who don’t know they can requisition an old Cisco 3750 that’s still good, but was decommissioned last year. It could also be a boss that wants to have an extra laptop running or an app<\/a> team that wants to have a concentration of monitoring<\/a> devices for a war<\/a> room or something similar.<\/p>\n\n\n\n

But switches you can expect. I mentioned the unexpected, and I will now deliver on that promise.<\/p>\n\n\n\n

Small companies have it lucky. Once the odd things are found – be they cameras, badge readers, printers, industrial devices, barcode scanners<\/a>, automated<\/a> fryers, refrigeration units, glucometers, or environmental controls, the person doing the discovery is not far away from the person responsible for those devices. And by “not far away”, I mean that both in the sense of both physical and organizational distance. The company is still small enough to have a familial feel to it, where everyone can walk up to everyone else.<\/p>\n\n\n\n

Once you meet the person responsible for the unusual device, you’ll get a story behind it that’s likely to contain the business<\/a> reason to have the device on the network. That, or a promise to get it off the network if it’s causing a problem.<\/p>\n\n\n\n

In the medium-sized company, it’s a longer walk to have that kind of chat, and maybe you also have to go through a manager in order to have permission to engage in that kind of talk. You might even have difficulty finding out who you need to talk to about the serial-to-ethernet devices, the USB-to-ethernet devices, and the parallel-to-ethernet devices.<\/p>\n\n\n\n

Also, you’re now more at risk<\/a> to find ancient history still connected to your network. The small companies also tend to be *new* companies, so they tend to have new gear. Medium companies have likely been around for a while, and that means they could have devices that the company forgot about… devices that are now no longer supported by their vendors<\/a> and which will need replacement in order to not be the security threat<\/a> which they now constitute.<\/p>\n\n\n\n

But for diversity<\/a> and legacy, nothing beats the large company. The bigger it is, the crazier the scenario can get. Time for my disclaimer – I work for a company that makes a product<\/a> designed to discover devices on the network and then classify them (among other things), and I have lots of large companies for my clients. With that disclaimer out of the way, I was recently at a client where, in the space of one hour, we reviewed a proof of concept<\/a> deployment<\/a> and found the following things on the wired<\/a> network:<\/p>\n\n\n\n

1. A cockroach switch.
2. A Nintendo.
3. A Windows<\/a> 98SE PC. (Also connected through a cockroach switch, just for good measure.)
4. A network range used in more than one place.<\/p>\n\n\n\n

Oops<\/a>, forget to mention that fourth thing in my previous paragraphs. But, it’s a sad fact of physics or biology or some kind of science that, as companies grow<\/a>, growing with them is the chance that some self-proclaimed techie will set up a network using an address space already operational somewhere else. The worst case of this was where a site that had a large number of guest wireless<\/a> devices utilized the entire 10.0.0.0\/8 range for it. We found it about a month after it was created, in the course<\/a> of tracking<\/a> down intermittent and unpredictable network timeouts and connection refused errors…<\/p>\n\n\n\n

But I’ve seen earth movers, cows, ATMs, lightbulbs, drug pumps, silicon<\/a> wafer fabs, vending machines, cash registers, information kiosks, ovens, refrigerators, pneumatic drills, scales, televisions, cars, personal health<\/a> monitors<\/a>, vacuum cleaners, and baby monitors all on customer networks. It’s not just that if there’s a thing, there’s both porn of it as well as an Internet-enabled version of it. It’s that those internet-enabled things will show up on your networks<\/a> because either they were purchased and connected by the organization, or because people who work at that organization decided to bring them in and connect them up.<\/p>\n\n\n\n

Some of those things are just fine, if they stay on guest networks. Some of those things are just fine, provided they are on segmented networks with limited or no access to the rest of the corporate networks<\/a> and\/or the Internet. And some of those things don’t belong anywhere on any network. The final say on which devices go where is up to the organization’s mission, values, and overall security posture.<\/p>\n\n\n\n

But, before you can decide what should or should not be on the network, you need to know what *is* on the network.<\/p>\n\n\n\n

\"\"\/<\/figure>\n","protected":false},"excerpt":{"rendered":"

There is so much more to security than: 1. Find the hackers. 2. Shut them down. First of all, we need to know what, exactly, is on the network and what it does and whether or not it should be doing that function while connected without restriction to the rest of the network. But before we tackle […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12],"tags":[],"class_list":["post-2535","post","type-post","status-publish","format-standard","hentry","category-security"],"_links":{"self":[{"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/2535","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2535"}],"version-history":[{"count":1,"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/2535\/revisions"}],"predecessor-version":[{"id":2536,"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/2535\/revisions\/2536"}],"wp:attachment":[{"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2535"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2535"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2535"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}