[FADCA] Security guidelines
Jerald A DeLong
kd4yal at tampabay.rr.com
Wed Mar 3 12:39:29 EST 2010
Phil/all,
When evaluating security concern for our HAM Radio Networks one most
really step back and look at the entire picture.
Here is a example:
We as HAM love to make all our software communicate so FPAC talks to
Winklink, Winklink talks to everything and etc.
This is not a bash on Winlink and/or FPAC!
This is what we do, we are HAMS we love to make things communicate and
we are very good at it too.
This is also one of our biggest down falls when it comes to Network
Security.
When we have all these different application that communicate with each
other, all linked over the world.Each application brings it's own set of
security concerns to our network.
So you had your "internal network security specialist" review your setup
and software. What about my setup and the many other nodes we
communicate within our own network.They all communicate with each other,
right?
Your nodes maybe secure but your neighbors node is probably not setup
with the same "Security guidelines" in mind but it is still part of our
HAM Radio network in which we all communicate.
I know of many dos/nos and linux/nos type setups that still have
anonymous telnet login that can currently access our packet network.Most
of these type node operators only concern is not allowing access to
radio ports and they are not concerned with anything that happens over
the Internet links.
It's a good thing your nodes are being monitored which is also what I do
a lot of here. I see constant attacks from the Internet 24/7 never stop.
One of many radio setup on my node routes 4 down stream AMPR Net
Gateways to the 44-net. Because these 4 server were under constant
attack from the Internet I had to just block access to the outside world
and only allow them to communicate within the 44-network.
So what about other nodes in our network.
Anyone care to comment.
Jerry DeLong
More information about the FADCA
mailing list