24.11.2012 Views

CHAIR'S CORNER Andy Kraus - National Conference of State ...

CHAIR'S CORNER Andy Kraus - National Conference of State ...

CHAIR'S CORNER Andy Kraus - National Conference of State ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>CHAIR'S</strong><br />

<strong>CORNER</strong><br />

Inside this issue:<br />

Virginia Legislature –<br />

Learning the Blackberry<br />

Prayer<br />

Louisiana Legislature Moves<br />

to FTR Gold<br />

Minnesota Senate Implements<br />

Wireless<br />

Idaho Offers New Web Site<br />

Design<br />

Nevada Legislature - Securing<br />

the Future<br />

Kansas Technology Update<br />

Arkansas Legislature - The<br />

Scourge <strong>of</strong> Spyware<br />

2004 NALIT PDS:<br />

Mischief in the Mountains<br />

Editor's Corner<br />

Officers and Directors<br />

2004-05 NALIT Committees<br />

N A L I T<br />

<strong>National</strong> Association <strong>of</strong> Legislative Information Technology<br />

Winter 2005<br />

<strong>National</strong> <strong>Conference</strong> <strong>of</strong> <strong>State</strong> Legislatures • 7700 E. First Place • Denver, CO 80230 • (303) 364-7700<br />

Recent changes within NALIT have allowed me the opportunity to become your Chair a<br />

bit early, so I would like to use this Chair’s Column to outline my strategy for the next year<br />

and a half. First, though, I would like to extend a big thank you to Todd Jewell. I am speaking<br />

for everyone when I say that we appreciate your service on the NALIT Executive Committee.<br />

We are currently in the process <strong>of</strong> finalizing committee assignments for this year.<br />

Committees are really the core <strong>of</strong> NALIT because much <strong>of</strong> the “grunt work” is done there.<br />

You will find a list <strong>of</strong> the committees, including the description, later in the newsletter. I would<br />

really encourage you to look through the list and see if anything piques your interest. At the<br />

same time, we have identified a list <strong>of</strong> “candidates” who we<br />

think would be a good fit for the committees, so we will<br />

contact you soon. Between the volunteers and our list, we<br />

will have many fine people on the committees this year.<br />

<strong>Andy</strong><br />

<strong>Kraus</strong><br />

One <strong>of</strong> my immediate goals for NALIT will be undertaken<br />

by the Outreach Committee. In order to continue NALIT’s<br />

growth and the search for varied sources <strong>of</strong> information, it is<br />

important to include as many people as possible. The<br />

Outreach Committee will find ways to attract more<br />

international participants and speakers to the Annual<br />

Meeting and Pr<strong>of</strong>essional Development Seminar. They will<br />

also work on ways to include states that have not been<br />

involved with NALIT in the past. The bottom line is that the more people and organizations<br />

we can include, the more we will all benefit from our pooled knowledge.<br />

A longer-range goal I would like to set for NALIT is to transform our organization into a<br />

source <strong>of</strong> information for the other NCSL staff sections, in addition to our respective state<br />

legislatures. The first step is the formation <strong>of</strong> the “IT Seal <strong>of</strong> Approval Exploratory<br />

Committee.” As the committee description notes, the committee’s first year will consist <strong>of</strong><br />

establishing a way to implement a technology review system that will allow our panel <strong>of</strong><br />

experts to examine existing systems and methodologies and publish “opinions” on what<br />

makes them work so well. When new products or systems come out, this committee will find<br />

out who the experts are and work with them to learn and share the knowledge with the rest <strong>of</strong><br />

NALIT. I am really excited about this project’s potential. We will start small this first year, and<br />

once we determine a target scope, we will march ahead next year. This idea is still in<br />

development, and I have already received some excellent suggestions for tweaking it.<br />

Nonetheless, I want to put the idea out there so we can all start considering its possibilities. I<br />

will try to keep you all updated via the listserv as things develop, and to give you an<br />

opportunity for feedback.<br />

Finally, the “PDS Site Selection Committee” will work to select the seminar locations for<br />

2006 and 2007. If your state is interested in hosting either <strong>of</strong> these seminars, you should let<br />

the selection committee know. If you want to have a say in where we meet, then please<br />

consider being on this committee.<br />

I am honored to serve as your Chair. Be assured that I am always happy to talk to you<br />

and find out what’s on your mind about our great organization. If there is anything I can help<br />

you with, please feel free to call, e-mail, or if you are in Topeka, stop on by. This is a great<br />

time to be involved with NALIT, so here’s to another great year!<br />

1


W ithin 10 minutes,<br />

I had coordinated<br />

a solution with<br />

other Blackberrycarrying<br />

staff and, as<br />

we confirmed a<br />

successful resolution<br />

to this particular<br />

problem, the phrase<br />

“Blackberries Rule”<br />

was transmitted.<br />

2<br />

Virginia Legislature –<br />

Learning the Blackberry Prayer<br />

By Sharon Crouch Steidel<br />

As is sometimes the case in a legislative<br />

environment, you don’t always get to<br />

choose the timeline <strong>of</strong> projects. Such was<br />

our case when we received a request for the<br />

integration <strong>of</strong> a Blackberry server with our<br />

Domino mail server. The request came the<br />

week before our 2005 session began, but we<br />

decided to give it a try.<br />

As mentioned, we are a Domino (Lotus<br />

Notes) environment. We needed to<br />

configure mail and calendar events to auto<br />

synchronize to mail boxes in two distinct<br />

mail domains. Technical staff from Nextel<br />

assured us this would not be a problem, so<br />

we embarked on our journey to deploy the<br />

Blackberry Enterprise Server. Nextel<br />

estimated the installation would take<br />

approximately two to four hours. The<br />

installation itself only took about 45 minutes,<br />

but to say things were flowing perfectly at<br />

that time would be a drastic overstatement.<br />

In fact, initially, we spent one afternoon from<br />

1:00 p.m. until about 8:00 p.m. on the phone<br />

with technical staff from RIM, who makes<br />

the Blackberries. After 30 or so hours <strong>of</strong><br />

phone support, a few edits to our registry<br />

files and many different configuration edits<br />

(most <strong>of</strong> which failed), we had a fully<br />

functional BES server.<br />

To their credit, Nextel and RIM remained<br />

steadfast in their support. There were<br />

several multiple-hour conference calls as we<br />

were trouble shooting the quirky problems<br />

that persisted, and RIM hung in there to<br />

insure that we were fully operational. There<br />

are still some lingering quirks that we are<br />

ironing out, but all in all the project has been<br />

successful. We now have the staff <strong>of</strong> the<br />

House and Senate Budget committees,<br />

Speaker’s Office, and some House Clerk’s<br />

staff using Blackberry 7520’s – walking the<br />

halls practicing what is sometimes called the<br />

Blackberry Prayer – heads bowed down to<br />

the Blackberry, thumbing away at the next<br />

important message. Since we were already a<br />

Nextel customer, those staff carrying Nextel<br />

phones were able to easily move their<br />

phones over to the Blackberry device. To<br />

anyone considering a similar project I would<br />

suggest allowing a month for installation and<br />

testing. After many hours chatting with RIM<br />

technical support staff, we did find out that<br />

the server we were deploying had just been<br />

released a few weeks before. Perhaps that<br />

contributed to the additional tweaking<br />

required.<br />

So, has the Blackberry improved<br />

productivity in our <strong>of</strong>fice? It has definitely<br />

proved useful in providing around-the-clock<br />

support to members during session. As an<br />

example, one recent Sunday afternoon I was<br />

sitting on a car wash bench, my dog asleep at<br />

my feet, when I got a call for help via email.<br />

Within 10 minutes, I had coordinated a<br />

solution with other Blackberry-carrying staff<br />

and, as we confirmed a successful resolution<br />

to this particular problem, the phrase<br />

“Blackberries Rule” was transmitted. Of<br />

course, the greatest advantage <strong>of</strong> the device<br />

is also its biggest flaw – it is an electronic<br />

tether that can keep you attached to the<br />

<strong>of</strong>fice until you choose to hit the power<br />

button. And as the devices’ nickname<br />

“Crackberries” suggests, it is evident that<br />

many users cannot ever bring themselves to<br />

hit that power button. To that end, I am<br />

providing two articles I found recently about<br />

these devices that may be food for thought.<br />

I, for one, am enjoying the ability to leave<br />

the <strong>of</strong>fice, comfortable that if a problem<br />

comes up, I will know about it. I can browse<br />

the web, send email, check my calendar, and<br />

stay in touch with the <strong>of</strong>fice and home from<br />

anywhere. It’s a very handy tool when<br />

stranded at an airport for most <strong>of</strong> the day – as<br />

I was a few weeks ago. It is the ultimate, allin-one,<br />

portable <strong>of</strong>fice.<br />

But as I sit down to dinner with my<br />

husband, I do have to remind myself that<br />

there is a power button….<br />

Resources:<br />

Blackberry or Crackberry: A PDA Culture War<br />

http://www.npr.org/templates/story/<br />

story.php?storyId=4279486<br />

Blackberry Jam<br />

http://www.govexec.com/features/1104-01/1104-01s2.htm<br />

Avoiding Addiction<br />

http://www.govexec.com/features/1104-01/1104-<br />

01s2s1.htm


Louisiana Legislature<br />

Moves to FTR Gold<br />

By Gary Schaefer<br />

In 1999, the Louisiana Legislature began<br />

using FTR version 3.3 (For The Record) to<br />

record its committee meetings. FTR was<br />

implemented because it provided all staff and<br />

legislators with the means to listen to any<br />

recorded meeting on their PCs in the Capitol.<br />

Recordings can be annotated to locate the<br />

discussion on a particular instrument and the<br />

testimony <strong>of</strong> a specific witness. Annotations<br />

also allow staff to find specific portions <strong>of</strong> a<br />

recording, which facilitates meeting excerpt<br />

duplication requests.<br />

Although FTR provided more flexibility and<br />

capabilities than the old cassette recording<br />

system, some problems were experienced. The<br />

most common complaints from personnel<br />

staffing the meetings were: the system would<br />

freeze and lock up randomly, difficulty in<br />

starting and stopping a recording, cumbersome<br />

to monitor a meeting while in progress, and<br />

unable to edit annotations during the meeting.<br />

The most significant problem occurred when<br />

meetings in multiple rooms were being recorded<br />

simultaneously. A user in one meeting could<br />

inadvertently stop another user’s recording. If<br />

users were not extremely alert, they did not<br />

realize their recordings had been stopped until<br />

their meeting was over.<br />

Following the 2003 regular session, the<br />

Legislature initiated an upgrade to FTR Gold<br />

s<strong>of</strong>tware. An upgrade was necessary because<br />

s<strong>of</strong>tware support for version 3.3 was being<br />

phased out, and Windows XP was being<br />

installed, for which version 3.3 was not<br />

designed.<br />

The FTR Gold version purported to allow:<br />

• better control over starting, pausing, and<br />

stopping a recording,<br />

• easier methods for annotating the meeting,<br />

• flexibility to add notes to a meeting,<br />

• enhanced audio monitoring during a<br />

meeting to ensure the system is functioning<br />

properly,<br />

• improved storage capabilities utilizing less<br />

disk space (i.e., the ability to store more<br />

meetings on line),<br />

• ability to convert existing recordings and<br />

annotations to the new more efficient format,<br />

and<br />

• more options for providing audio copies <strong>of</strong><br />

the meeting (e.g., cassette tape, CD).<br />

The upgrade to the new FTR Gold product<br />

was implemented for the 2004 regular session.<br />

Senate staff responsible for the recordings and<br />

duplication requests has had very positive<br />

comments concerning the new s<strong>of</strong>tware. The<br />

purported improvements have been realized, and<br />

the new s<strong>of</strong>tware is more user-friendly.<br />

Procedures for starting and stopping a recording<br />

are much simpler, and users cannot inadvertently<br />

stop another recording. Annotations are entered<br />

more easily and annotation text wraps<br />

automatically. Users also have the ability to<br />

correct text for an entered annotation, and add<br />

text to an annotation while the meeting is in<br />

progress. The old version required such editing<br />

to be done as a “post” annotation. In version<br />

3.3, the time stamp associated with annotations<br />

was not always correct. This caused problems<br />

when trying to locate a particular instrument or<br />

specific testimony. There have been no<br />

problems with the time stamp when using FTR<br />

Gold. Users report increased flexibility when<br />

playing a recording to transcribe minutes and<br />

when performing post annotations.<br />

Senate staff responsible for duplication <strong>of</strong><br />

these recordings has also been very satisfied<br />

with FTR Gold. They particularly like the fact<br />

that they can duplicate a recording from their PC<br />

versus going to another location and a dedicated<br />

PC to create the copy. The audio quality is much<br />

better, and CDs can be produced in several<br />

different formats: a file for use with the FTR Gold<br />

player; a “.wav” file for use with RealPlayer,<br />

Windows Media Player or “GearPlayer;” a<br />

“.wma” file for use with Windows Media Player;<br />

or a “.cda” file for use with car and home CD<br />

players.<br />

The only unresolved issue is the FTR file<br />

conversion <strong>of</strong> recorded meetings from 1999<br />

through 2003. PSA (Public Systems Associates),<br />

the Legislature’s computer consultant, reports<br />

that the recordings must first be “archived” to<br />

CD in order to convert the old file format to the<br />

new file format. When FTR was implemented,<br />

the Legislature decided to keep all recordings on<br />

line for easy access. There are approximately<br />

3,000 recorded Senate and House committee<br />

meetings in the old file format totaling 300 GB <strong>of</strong><br />

disk storage. PSA estimates it will take one year<br />

to archive and convert all the old files. Until all<br />

files are converted, users must keep both<br />

versions <strong>of</strong> the FTR player on their PCs. Overall,<br />

Senate staff is very pleased with the<br />

implementation <strong>of</strong> the FTR Gold product.<br />

T he audio quality is<br />

much better, and<br />

CDs can be produced<br />

in several different<br />

formats: a file for use<br />

with the FTR Gold<br />

player; a “.wav” file<br />

for use with<br />

RealPlayer, Windows<br />

Media Player or<br />

“GearPlayer;” a<br />

“.wma” file for use<br />

with Windows Media<br />

Player; or a “.cda”<br />

file for use with car<br />

and home CD players.<br />

3


For security, we are<br />

implementing MAC<br />

address lock-downs for<br />

senate users and<br />

authorized agency<br />

users. This will keep<br />

any new devices not<br />

setup by the Senate IT<br />

staff from connecting<br />

to any “non-public”<br />

state networks.<br />

4<br />

Minnesota Senate<br />

Implements Wireless<br />

By Jim Greenwalt<br />

The Minnesota Senate has finally begun<br />

implementation <strong>of</strong> wireless access in the <strong>State</strong><br />

Capitol Building. Initially, access is available in<br />

the six major senate hearing rooms <strong>of</strong> the<br />

building. The Senate Chamber, having already<br />

been hardwired, is not included.<br />

Wireless access will be provided on three<br />

levels: (1) members and senate staff; (2) other<br />

legislative and state agencies; and (3) the<br />

general public.<br />

The architecture is built around the<br />

Airespace Wireless product (recently acquired<br />

by Cisco). It consists <strong>of</strong> a redundant wireless<br />

access network in each <strong>of</strong> the hearing rooms. In<br />

each <strong>of</strong> these areas, for senate members and<br />

staff, we are using the 802.11a protocol to give<br />

us the best coverage, with the fastest access,<br />

and with the smallest chance <strong>of</strong> being interfered<br />

with by other wireless networks in the building.<br />

Using 802.11a will also eliminate anyone from<br />

walking from the street with a handheld and<br />

connecting to the network. 802.11b and 802.11g<br />

service is available on the system for the others<br />

without investing in additional hardware.<br />

In each <strong>of</strong> the hearing rooms we have<br />

installed two wireless access point radios, each<br />

connected to a different switch, giving full<br />

redundancy <strong>of</strong> hardware and access in each<br />

area. This also allows for double the bandwidth<br />

and double the number <strong>of</strong> available channels in<br />

each area.<br />

We are very excited about hosting the<br />

2005 seminar. Tentative plans are to have<br />

an authentic Native American cuisine<br />

dinner at the Crazy Horse Memorial, visit<br />

the Mount Rushmore Memorial and travel<br />

to Historical Deadwood for dinner and, if<br />

desired, a little gambling. Unfortunately,<br />

due to the distance between Rapid City<br />

and Pierre, it will not be possible to take<br />

everyone to our beautiful <strong>State</strong> Capitol<br />

Building. However, if anyone would like<br />

to stop for a tour on their way through,<br />

For security, we are implementing MAC<br />

address lock-downs for senate users and<br />

authorized agency users. This will keep any<br />

new devices not setup by the Senate IT staff<br />

from connecting to any “non-public” state<br />

networks.<br />

Access for each level <strong>of</strong> user is directed<br />

through VLANs set up on the senate’s network.<br />

One is exclusively for members and staff,<br />

allowing access to the Senate’s network and all<br />

applications and data necessary for users.<br />

Another is for other legislative or state<br />

agencies, directing them to the appropriate state<br />

network for which they are authorized. For the<br />

public, the senate will broadcast an 802.11b/g<br />

signal, which will allow anyone within range<br />

access to just the public internet. The public<br />

can then access legislative information through<br />

the Senate’s public web site, or their e-mail<br />

through their Internet providers.<br />

There is no charge for access by agencies<br />

or the public. The Senate accepts NO<br />

responsibility and provides NO maintenance for<br />

the service they receive.<br />

The Airespace solution, reasonable in cost,<br />

was very easy to implement. The systems can<br />

be easily and seamlessly integrated with most<br />

vendors' switches. It has proved to be very<br />

scalable, allowing us to implement in stages and<br />

provide a variety <strong>of</strong> services with a single<br />

solution.<br />

2005 NALIT Pr<strong>of</strong>essional Development Seminar<br />

October 5-8, 2005<br />

Rapid City, South Dakota<br />

By Lou Adamson<br />

Scott or I would be very happy to<br />

accommodate you.<br />

If you have any suggested speakers or items<br />

you would like sessions on, please contact:<br />

Pam Greenberg (pam.greenberg@ncsl.org),<br />

Scott Darnall (scott.darnall@state.sd.us), or<br />

Lou Adamson (lou.adamson@state.sd.us).<br />

Any suggestions will be welcomed.<br />

Hope to see you all in October.


NALIT at the NCSL Annual Meeting<br />

August 16-20, Seattle, Washington<br />

Mark your calendar for the 2005 NCSL<br />

Annual Meeting, to be held Aug. 16-20, 2005.<br />

The preliminary schedule for NALIT and other<br />

staff sections begins with meetings from 1 p.m.<br />

to 5 p.m. on Tuesday, Aug. 16. On Thursday,<br />

Aug. 18, NALIT will meet from 11:45 a.m. to 5<br />

p.m.<br />

The traditional all-staff luncheon, where<br />

legislative staff achievement awards are<br />

presented, is scheduled for Friday, Aug. 19 from<br />

Idaho Offers New Web Site Design<br />

By Brenda Wilkening<br />

The Idaho Legislature has a new and<br />

improved web site. Over the interim, the<br />

Legislative Services Office web group along<br />

with the Idaho Department <strong>of</strong> Administration<br />

redesigned the web site to be more accessible,<br />

useful, and aesthetically pleasing. The new site<br />

went live the first part <strong>of</strong> January, just in time for<br />

the legislative session.<br />

The web team determined the use <strong>of</strong> rollover<br />

menus greatly decreased the amount <strong>of</strong><br />

clutter on the web pages, and allowed easier<br />

navigation throughout the site. The designers<br />

utilized style sheets to create the menus which<br />

insures complete accessibility and allows<br />

viewing from any browser.<br />

The introduction <strong>of</strong> ColdFusion into our<br />

website has been one <strong>of</strong> the best improvements,<br />

generating many <strong>of</strong> our pages dynamically. The<br />

use <strong>of</strong> this tool has greatly reduced errors as<br />

well as the amount <strong>of</strong> time it takes to update<br />

legislator and staff information.<br />

12:30 p.m. to 2 p.m., to be followed by NALIT<br />

meetings from 2:15 p.m. to 4:15 p.m.<br />

In addition to these time slots, NALIT may<br />

sponsor additional sessions during other times.<br />

In addition, tours <strong>of</strong> Seattle or Olympia-area hightech<br />

firms or organizations may be scheduled.<br />

Additional information about the NCSL<br />

Annual Meeting is available at www.ncsl.org/<br />

annualmeeting. Watch for more details about<br />

NALIT sessions at www.ncsl.org/nalit.<br />

2005 NCSL Annual Meeting, Preliminary Schedule (Abbreviated)<br />

Tuesday<br />

August 16<br />

Wednesday Thursday Friday Saturday<br />

August 17 August 18 August 19 August 20<br />

Registration Opening Standing Concurrent Sess. Plenary Session<br />

Plenary Committees NCSL Closing Event<br />

Business Mtg.<br />

NALIT Standing NALIT Legis. Staff Lunch<br />

1 p.m. - 5 p.m. Committees 11:45 a.m.-5:00 p.m. 12:30 p.m. - 2 p.m.<br />

NALIT<br />

2:15 p.m. - 4:15 p.m.<br />

Opening Washington Social <strong>State</strong>s’ Night<br />

Reception Event<br />

Currently, the Idaho Legislature web site<br />

spans across three servers. The Idaho statutes,<br />

constitution and legislation are held on a Linux<br />

Apache server, while the search criteria for these<br />

documents is hosted on a Windows 2000<br />

Advanced server. The remainder <strong>of</strong> the website<br />

is on a Windows 2000 server.<br />

Looking ahead to future improvements, the<br />

web team plans to combine all pages to a single<br />

server, extend the use <strong>of</strong> ColdFusion and,<br />

utilizing XML, push legislation and statutes to<br />

the web site from our new bill drafting system<br />

currently in development. (Stay tuned for more<br />

information about that topic once it hits<br />

production.)<br />

Having spent several months and countless<br />

hours on the new design, the web team is<br />

considerably proud <strong>of</strong> the finished product.<br />

However, we will continue to take advantage <strong>of</strong><br />

new technology available to better serve the<br />

citizens <strong>of</strong> the state <strong>of</strong> Idaho and beyond.<br />

T he web team<br />

determined the<br />

use <strong>of</strong> roll-over menus<br />

greatly decreased the<br />

amount <strong>of</strong> clutter on<br />

the web pages, and<br />

allowed easier<br />

navigation throughout<br />

the site.<br />

5


D ual gigabit fiber<br />

connections allow<br />

for 2 Gbps <strong>of</strong> throughput<br />

to each hub room while<br />

still providing active<br />

redundancy. Utilizing<br />

VLAN’s, ACL’s and QoS<br />

also provided a secure<br />

way <strong>of</strong> segmenting our<br />

users and providing the<br />

appropriate level <strong>of</strong><br />

service for each group.<br />

6<br />

By Eric Dugger<br />

Securing the Future<br />

During the last year the Nevada <strong>State</strong><br />

Legislature has gone through a rebirth <strong>of</strong> its IT<br />

infrastructure. Facing changing times and more<br />

demands for IT services, it was determined that a<br />

complete upgrade was in order. A new network<br />

consisting <strong>of</strong> the latest switches, routers,<br />

firewalls, and VPN products would be the base<br />

<strong>of</strong> the upgrade. Upon that was a move from a<br />

Windows NT 4.0 domain to a Windows Server<br />

2003 Active Directory structure as well as a new<br />

mail server and anti-spam gateway along with an<br />

internal instant messaging server. Might as well<br />

just do everything, right?<br />

Having the opportunity to do everything<br />

new allowed for a clean, secure design. With a<br />

group <strong>of</strong> four people, we had around half a year<br />

to plan, configure, install and tune, which<br />

towards the end seemed to be not enough time!<br />

Our first move was to a Windows 2003 Active<br />

Directory domain structure. This foundation<br />

allowed us to do many new things, including an<br />

upgrade to Exchange 2003 mail server. The new<br />

Exchange is much more stable and secure than<br />

the old 5.5 version, and allows for much more<br />

control and growth. Outlook Web Access alone<br />

is worth the upgrade if you have remote users.<br />

The features <strong>of</strong> 2003 Active Directory allow our<br />

group <strong>of</strong> four to manage over 500 users and their<br />

PCs, 30 servers in our main Carson City location,<br />

and our remote <strong>of</strong>fice in Las Vegas.<br />

Our old network infrastructure was comprised<br />

<strong>of</strong> Cisco 2600 routers and a Cisco Catalyst<br />

5500 switch. We only had 200 Mbps to each <strong>of</strong><br />

our hub rooms, which serve upwards <strong>of</strong> 100<br />

users per room. This configuration was both<br />

slow and inefficient, therefore we wanted our<br />

new network to provide more bandwidth,<br />

redundancy and security. New Cisco 3550<br />

switches in the hub rooms and a Cisco Catalyst<br />

6500 as the backbone were the answer. Dual<br />

gigabit fiber connections allow for 2 Gbps <strong>of</strong><br />

throughput to each hub room while still providing<br />

active redundancy. Utilizing VLAN’s, ACL’s<br />

and QoS also provided a secure way <strong>of</strong> segmenting<br />

our users and providing the appropriate level<br />

<strong>of</strong> service for each group.<br />

Wireless by nature is not secure, therefore<br />

we wanted to implement new technologies and<br />

procedures to improve security. We consolidated<br />

our two wireless networks (one for the<br />

public and one for internal users) into one<br />

network outside <strong>of</strong> our firewall. We selected the<br />

Cisco 1200 APs running A/B/G and split the<br />

users into two SSID networks, one running A for<br />

faster speeds for our users and the other running<br />

B/G at slower speeds for the public users. We<br />

incorporated Cisco’s WLSE and ACS to help<br />

manage the network <strong>of</strong> 40 APs as well as keeping<br />

it more secure. This system is projected to have<br />

over 200 users online during peak times.<br />

Due to the move <strong>of</strong> the wireless network<br />

outside the firewall and the additions <strong>of</strong> remote<br />

<strong>of</strong>fices, we were forced to take VPN seriously.<br />

Cisco’s 3000 VPN concentrator allows our staff to<br />

connect seamlessly while on our wireless<br />

network. This makes wireless a secure option<br />

while giving our legislators the flexibility to do<br />

their own thing when not connected to the VPN.<br />

When connected to the VPN, staff and legislators<br />

will receive the latest Windows patches and antivirus<br />

system updates.<br />

Security was implemented everywhere it<br />

could be. On the domain side, we are using<br />

Micros<strong>of</strong>t’s MOM server to monitor all servers<br />

for any security or hardware faults. We also use<br />

policies to make sure any PC that logs onto the<br />

domain is updated with the proper patches. On<br />

the network side we use MAC authentication<br />

where needed and ACL’s to secure traffic flows.<br />

This helps each division within the Nevada<br />

Legislature maintain the type <strong>of</strong> operating<br />

environment they want without having multiple<br />

domains and networks, which can become very<br />

expensive. Our next step is to create an intelligent<br />

network by integrating our intrusion<br />

detection/prevention systems and policies with<br />

our network devices to create a dynamic infrastructure<br />

that reacts to changes in its environment,<br />

making it more secure.<br />

The Nevada <strong>State</strong> Legislature Operations<br />

Team consists <strong>of</strong> Manager Randy Dumbauld,<br />

Rich Tillis, Scott Corbett and myself, Eric Dugger.<br />

References:<br />

Micros<strong>of</strong>t 2003<br />

http://www.micros<strong>of</strong>t.com/windowsserver2003/evaluation/<br />

overview/family.mspx<br />

Cisco Catalyst 6500<br />

http://www.cisco.com/en/US/products/hw/switches/ps708/<br />

index.html<br />

Cisco VPN 3000<br />

http://www.cisco.com/en/US/products/hw/vpndevc/ps2284/<br />

index.html<br />

Cisco Wireless<br />

http://www.cisco.com/en/US/products/hw/wireless/ps430/<br />

index.html<br />

Cisco Enterprise Security Solutions<br />

http://www.cisco.com/en/US/netsol/ns340/ns394/ns171/<br />

networking_solutions_packages_list.html


Kansas Technology Update<br />

By Dave Larson<br />

Three interesting initiatives are occurring<br />

at the Kansas Legislature.<br />

First, the electronic committee experiment<br />

will continue this session. This project was<br />

started last year when the House Health and<br />

Human Services Committee and the Senate<br />

Utilities Committee acquired Tablet PCs,<br />

s<strong>of</strong>tware, wireless networking equipment and<br />

multimedia facilities to conduct a totally<br />

paperless, electronic committee. Feedback and<br />

lessons learned from last session were factored<br />

into revisions to be tested this session. Some<br />

<strong>of</strong> the lessons learned were:<br />

• Legislators, no matter the initial skill level,<br />

eventually overcame their resistance and<br />

adopted the technology. The largest complaint<br />

from legislators was the prohibition on using<br />

state resources in campaigns, therefore they<br />

could not put their campaign material on the<br />

state-provided tablet.<br />

• Legislators who indicated they were<br />

computer literate, overestimated their abilities.<br />

More training is required than was anticipated.<br />

• The process moves too fast for search<br />

technology to be employed effectively. Push<br />

technology is required.<br />

• The tablets were used over traditional<br />

laptops for two reasons. First, it was<br />

anticipated that handwriting recognition would<br />

smooth the transition for the non-computer<br />

oriented legislator. Second, using the PC in<br />

tablet mode kept the legislator from hiding<br />

behind the screen and was perceived to be more<br />

courteous to conferees. Handwriting<br />

recognition is quite good today. Some<br />

legislators liked to mark up bills in handwriting<br />

mode, but ultimately, handwriting capability is<br />

not required for acceptance or success.<br />

• The electronic process did not appear to be<br />

a disadvantage to any conferee. Nearly all<br />

testimony was submitted in electronic form.<br />

Testimony that wasn’t submitted in electronic<br />

form was scanned and entered into the<br />

document database by committee staff.<br />

• The electronic process placed some<br />

additional work on the committee staff to<br />

prepare for the committee meeting. Significant<br />

effort was applied during the interim to relieve<br />

the workload.<br />

• There was a temptation by the committee to<br />

coerce the staff revisor to draft amendments in<br />

committee. Staff revisors prefer to take notes<br />

back to the <strong>of</strong>fice and draft there. Similar<br />

pressures were experienced by the research<br />

staff.<br />

• To be really effective, there may need to be<br />

a technician assigned to the electronic<br />

committee to manage the technology, pan the<br />

camera, etc.<br />

The experiment was funded by a grant from<br />

the Information Network <strong>of</strong> Kansas (INK). INK<br />

is the state’s information portal manager. The<br />

<strong>State</strong> <strong>of</strong> Kansas’ information portal is called<br />

AccessKansas.<br />

Second, the Kansas Capitol is in the third<br />

year <strong>of</strong> a 10-year renovation. As part <strong>of</strong> the<br />

renovation, a wireless survey was conducted by<br />

a Kansas City firm. Surprisingly, the survey<br />

indicated that the massive, stone Capitol<br />

building with all its nooks and crannies did not<br />

pose any significant challenges to wireless<br />

coverage. This is encouraging and indicates<br />

that the installation <strong>of</strong> wireless networking<br />

maybe easier and less expensive than<br />

anticipated. This revelation may allow us to<br />

speed up the implementation <strong>of</strong> wireless which<br />

in turn may help us manage the network through<br />

the renovation.<br />

Third, the Legislature recently completed<br />

the latest revision <strong>of</strong> its strategic computing<br />

plan. This version was created using a new<br />

methodology called the “New Information<br />

Economics (NIE) Model.” The model was<br />

developed by the Beta Group and published in<br />

February 2004. We found the model easy to<br />

understand and implement. The model helped us<br />

focus on the true needs <strong>of</strong> the Legislature and<br />

quantify those results.<br />

The methodology works by aligning<br />

strategic intentions to the mission <strong>of</strong> the<br />

organization. These intentions include an<br />

analysis <strong>of</strong> organizational structure and the<br />

objectives <strong>of</strong> the organizational subgroups. In<br />

turn, the objectives are used to develop<br />

information technology objectives that support<br />

the mission <strong>of</strong> the enterprise. The revised<br />

strategic plan was adopted last fall and we are<br />

busy preparing to implement the first set <strong>of</strong><br />

priorities identified in the plan.<br />

H andwriting<br />

recognition is quite<br />

good today. Some<br />

legislators liked to mark<br />

up bills in handwriting<br />

mode, but ultimately,<br />

handwriting capability is<br />

not required for<br />

acceptance or success.<br />

7


S pyware has eclipsed<br />

viruses and spam<br />

as the fastest growing<br />

threat to users on the<br />

Internet.<br />

8<br />

The Scourge <strong>of</strong> Spyware<br />

By Lorie A. Johnson<br />

Recently, a House member came into my<br />

<strong>of</strong>fice with his laptop. It would not start up<br />

and I noticed a chassis problem, so I<br />

swapped his hard drive into a spare machine.<br />

I booted the machine to check that the hard<br />

drive was working and discovered it took<br />

much longer than usual to boot. After<br />

logging in I observed several icons for a fake<br />

anti-spyware program on the desktop and a<br />

swarm <strong>of</strong> pop-ups appeared on the screen<br />

without opening the browser. It took four<br />

hours to remove all <strong>of</strong> the rogue programs.<br />

This scenario is a reflection <strong>of</strong> the fastest<br />

growing scourge on the Internet: spyware.<br />

Spyware has eclipsed viruses and spam<br />

as the fastest growing threat to users on the<br />

Internet. Spyware can be web bugs that<br />

follow your browsing, ad servers that feed<br />

popups to your system, and key loggers<br />

which record passwords and other private<br />

information. Trojan horses are another form<br />

<strong>of</strong> spyware that open back doors to your<br />

system and enable hackers to use your<br />

system as a zombie for sending spam or<br />

distributed denial <strong>of</strong> service attacks. When<br />

you think you have managed to remove it,<br />

the creators <strong>of</strong> this s<strong>of</strong>tware have disguised it<br />

so that it magically reappears.<br />

Spyware can get into a computer in a<br />

variety <strong>of</strong> ways: through attachments in email,<br />

through unpatched browsers, in socalled<br />

‘drive-by downloads’, inattentive<br />

clicking on pop-ups, in popular s<strong>of</strong>tware like<br />

file sharing and screen savers, and even<br />

through port scans <strong>of</strong> unprotected systems.<br />

Spyware infections and compromises are less<br />

common for state and enterprise systems,<br />

since those systems are normally set up and<br />

patched behind enterprise-level firewalls.<br />

However portable systems, when connected<br />

to outside networks, become magnets for<br />

malware if not properly updated. In addition,<br />

innocent searches made from inside a<br />

protected network can lead to browser<br />

hijackers.<br />

Currently, the spyware and malware<br />

assault is far ahead <strong>of</strong> our means to fix it.<br />

There is no single anti-spyware program<br />

available that will clean all spyware. You have<br />

to install several programs, use them in layers<br />

to get rid <strong>of</strong> the spyware, and hope it has all<br />

been removed. Enterprise level companies,<br />

like Panda and MacAfee, are finally catching<br />

up, but it has taken them awhile. Fake antispyware<br />

s<strong>of</strong>tware is an even more sinister<br />

development for people hoping for a quick<br />

cure. A site called SpywareWarrior.com has an<br />

extensive and continually updated list <strong>of</strong> fake<br />

spyware programs, some with names close<br />

enough to appear legitimate. There are several<br />

excellent free anti-spyware programs available,<br />

such as Lavas<strong>of</strong>t’s venerable “Ad Aware,” Kolla’s<br />

“Spybot Search and Destroy,” and Webroot’s<br />

“Spy Sweeper.”<br />

How do you clean up the messes these<br />

malicious programs leave on systems? The<br />

easiest solution is to re-image the system, but if<br />

you have systems that are not imaged, or are<br />

specialty systems, re-imaging will not work. Here<br />

are some basic steps we utilize to clean infested<br />

machines.<br />

• First, generate a reference list <strong>of</strong> processes<br />

with Task Manager from a clean machine. In<br />

addition, use the program Hijack This! to get a<br />

reference list <strong>of</strong> Browser Helper Objects (BHOs).<br />

• When cleaning a PC, boot into Safe Mode<br />

and get rid <strong>of</strong> suspicious programs using “Add/<br />

Remove Programs.”<br />

• Run Spybot S&D, Ad-Aware, and Hijack This<br />

to find and clean up any strays and recursives.<br />

• For stubborn programs, we use<br />

“MSCONFIG” to turn <strong>of</strong>f hidden programs that<br />

might run in startup, and comb the registry for<br />

other bits and pieces. We also clean out the temp<br />

files.<br />

The key to keeping spyware infestations at<br />

bay is vigilance. Your IT security staff must stay<br />

on top <strong>of</strong> all developing trends in spyware, and<br />

keep your systems patched and protected.<br />

Constant vigilance and swift action, as well as<br />

policies and communication that educate your<br />

staff, are your best tools.<br />

Resources:<br />

CastleCops (formerly Computer Cops)<br />

http://computercops.biz/<br />

Spyware Warrior<br />

http://www.spywarewarrior.com/index.php<br />

Tom Coyote<br />

http://tomcoyote.com/<br />

Gibson Research Corporation<br />

http://www.grc.com/default.htm<br />

Infestation in four minutes:<br />

http://www.techweb.com/wire/security/54201306<br />

Fake spyware listings:<br />

http://www.spywarewarrior.com/rogue_anti-spyware.htm


2004 NALIT PDS:<br />

Mischief in the Mountains<br />

Last September, the 2004 NALIT<br />

Pr<strong>of</strong>essional Development Seminar was held in<br />

Burlington, Vermont. Well over 100 people<br />

attended. To the 20 or so for whom this was<br />

their first NALIT conference... welcome. We<br />

hope to see you at future conferences!<br />

Between the high quality <strong>of</strong> the program<br />

<strong>of</strong>fered and the beauty <strong>of</strong> the venue, a very<br />

good time was<br />

had by all.<br />

Burlington, a<br />

small but<br />

vibrant city<br />

located on the<br />

shore <strong>of</strong> Lake<br />

Champlain, is a<br />

town with a<br />

wide variety <strong>of</strong><br />

restaurants,<br />

bars, and other<br />

entertainment,<br />

and NALIT<br />

people, as<br />

usual, enjoyed<br />

all these facilities to their fullest.<br />

The seminars included sessions on both<br />

technical and managerial topics. And, as<br />

always, I found myself wishing to be in two<br />

places at once. At the Managing Expectations<br />

session, Vermont Rep. Judy Livingston gave an<br />

impassioned plea on behalf <strong>of</strong> legislators<br />

everywhere for more help using the tools we<br />

provide. On the technical side, the Voice Over<br />

IP session provided real world experience in<br />

implementing this fast-growing technology from<br />

people who have actually done it. Other<br />

session topics<br />

included Embracing<br />

Security, Contingency<br />

Planning, RSS, and<br />

XML Editors.<br />

One day was<br />

spent at the <strong>State</strong><br />

Capitol in Montpelier,<br />

where several<br />

sessions were held jointly with both the NALIT<br />

and the Legal Services Staff Section (LSSS).<br />

One joint meeting discussed the public records<br />

implications <strong>of</strong> e-mail. If this session didn’t<br />

scare the pants <strong>of</strong>f <strong>of</strong> you, you weren’t<br />

listening!<br />

Over lunch, Dr. Frank Bryan, a pr<strong>of</strong>essor <strong>of</strong><br />

political science from the University <strong>of</strong> Vermont,<br />

discussed that unique institution, the New<br />

by Duncan Goss<br />

England Town Meeting, a totally new concept<br />

for many conferees, but one as familiar to me as<br />

parades on the Fourth <strong>of</strong> July. Recently, I<br />

attended our town’s 200th consecutive meeting,<br />

and Dr. Bryan’s wry observations were right on<br />

target!<br />

On the way back from Montpelier, we<br />

visited another Vermont institution <strong>of</strong> more<br />

recent vintage, Ben & Jerry’s main ice cream<br />

factory. While this visit may not have provided<br />

any more insights into the legislative process, it<br />

certainly gave people another taste <strong>of</strong> Vermont.<br />

The final day <strong>of</strong> the conference concluded<br />

with a visit to the Shelburne Museum, an<br />

eclectic<br />

collection<br />

<strong>of</strong><br />

Americana<br />

spread<br />

throughout<br />

some 40<br />

buildings.<br />

The<br />

evening<br />

concluded<br />

with a truly<br />

spectacular<br />

dinner on<br />

board the<br />

Ticonderoga,<br />

Pam Greenberg and Duncan Goss<br />

an elegant steamship located at the center <strong>of</strong> the<br />

museum grounds.<br />

After dinner, we presented Pam Greenberg with<br />

a print <strong>of</strong> the Burlington waterfront, signed by<br />

all conference attendees, in gratitude for all that<br />

she does for NALIT.<br />

I appreciated having the opportunity to<br />

welcome all <strong>of</strong> you to Vermont and I am looking<br />

forward to next October and the 2005<br />

Pr<strong>of</strong>essional Development Seminar in Rapid<br />

City, South Dakota. See you all there!<br />

A t the Managing<br />

Expectations<br />

session, Vermont state<br />

Representative Judy<br />

Livingston gave an<br />

impassioned plea on<br />

behalf <strong>of</strong> legislators<br />

everywhere for more<br />

help using the tools we<br />

provide.<br />

9


10<br />

Editor's Corner<br />

By Gary Wieman<br />

Hello to all. I do hope that this newsletter is<br />

finding all <strong>of</strong> you healthy and having a success<br />

filled legislative session. It seems that the winter<br />

edition <strong>of</strong> the newsletter is getting out later<br />

every year, but the late date <strong>of</strong> the NCSL Annual<br />

meeting this year allows me a little more time to<br />

come up with a final product.<br />

In this newsletter I tried to present you with the<br />

latest information <strong>of</strong> what state legislative<br />

technology has to <strong>of</strong>fer. I listened and took<br />

notes at the <strong>State</strong> Roundtable presentations at<br />

the Pr<strong>of</strong>essional Development Seminar in<br />

Burlington, VT. I took this information, compared<br />

it to presentations made at previous PDS and<br />

Annual Meeting seminars, and asked for articles<br />

from states who had not presented their updates<br />

before. Some <strong>of</strong> these may have been topics that<br />

had been discussed previously, but at least they<br />

Executive Committee - Officers and Directors<br />

2004-05<br />

Chair/Vice Chair<br />

J. Andrew <strong>Kraus</strong><br />

Senior Network<br />

Administrator<br />

Legislature<br />

300 SW 10th Ave.,<br />

Ste. 529-S<br />

Topeka , KS 66612<br />

Voice: 785-296-2610<br />

Fax: 785-296-1153<br />

E-mail: andyk@las.state.ks.us<br />

Secretary<br />

Gary Wieman<br />

Network Manager<br />

Leg. Technology Center<br />

1445 K St., Rm. 359<br />

P.O. Box 94604<br />

Lincoln, NE 68509<br />

Voice: 402-471-6210<br />

Fax: 402-479-0990<br />

E-mail: gwieman@unicam.state.ne.us<br />

Past Chair<br />

Maryann Trauger<br />

Manager,<br />

IT Services<br />

North Dakota<br />

Legislative Council<br />

<strong>State</strong> Capitol,<br />

600 E. Boulevard<br />

Bismarck, ND 58505<br />

Voice: 701-328-2916<br />

Fax: 701-328-3615<br />

E-mail: mtrauger@state.nd.us<br />

2004-2005 Directors<br />

Scott Darnall<br />

Programmer/Analyst<br />

Legislative Research Council<br />

500 East Capitol<br />

Pierre, SD 575-01-5070<br />

Voice: 605-773-4296<br />

Fax: 605-773-4576<br />

E-mail: scott.darnall@state.sd.us<br />

<strong>Andy</strong> Harvey<br />

Webmaster<br />

Legislative Counsel Bureau<br />

401 S Carson St<br />

Carson City, NV 89701-4747<br />

Voice: 775-684-1347<br />

Fax: 775-684-1333<br />

E-mail: aharvey@lcb.state.nv.us<br />

Rick Johnson<br />

Senior S<strong>of</strong>tware Engineer<br />

Legislative Service Center<br />

2404 Chandler Court SW<br />

Olympia, WA 98502<br />

Voice: 360-786-7725<br />

Fax: 360-786-7234<br />

E-mail: johnson_ri@leg.wa.gov<br />

Ann McLaughlin<br />

Director<br />

Legislative Information System<br />

Office <strong>of</strong> the Controller General<br />

Legislative Hall, Box 1401<br />

Dover, DE 19903<br />

Phone: 302-744-4207<br />

Fax: 302-739-3794<br />

E-mail: ann.mclaughlin@state.de.us<br />

Jonathan Palmore<br />

Information Systems Director<br />

Senate<br />

P.O. Box 396<br />

Richmond, VA 23218<br />

Voice: 804-698-7410<br />

Fax: 804-698-7670<br />

E-mail: jpalmore@sov.state.va.us<br />

Janet Sullivan<br />

Applications Project Manager<br />

Texas Legislative Council<br />

P.O. Box 12128<br />

Capitol Station<br />

Austin, TX 78711-2128<br />

Voice: 512-463-1160<br />

E-mail: janet.sullivan@tlc.state.tx.us<br />

were from a different perspective.<br />

I want to thank all the contributing authors for<br />

their time and effort in providing information that<br />

is useful to NALIT members. I would like to<br />

encourage those who have not participated<br />

before to get involved with NALIT by<br />

submitting articles, to participate in meetings,<br />

and to volunteer for committees. There are many<br />

great opportunities to meet your peers from<br />

other states through this organization and to<br />

develop friendships and exchange ideas that will<br />

benefit all.<br />

Hope you've enjoyed the newsletter,<br />

Gary Wieman<br />

Secretary<br />

NALIT Executive Committee<br />

2004-05 NALIT Committees<br />

(appointments pending unless noted)<br />

2005 Pr<strong>of</strong>essional Development Seminar Site Selection Committee<br />

The committee will review site selection criteria, solicit bids, and make<br />

recommendations for locations <strong>of</strong> future Pr<strong>of</strong>essional Development Seminars.<br />

2005 Pr<strong>of</strong>essional Development Seminar Planning Committee<br />

Co-Chairs: Lou Adamson, South Dakota; Scott Darnall, South Dakota<br />

The committee will assist the host state staff as requested, plan session content<br />

and activities, locate speakers, and carry out other tasks that would contribute to<br />

the success <strong>of</strong> the seminar.<br />

Outreach Committee<br />

Members <strong>of</strong> this committee will have a two-year appointment. Committee<br />

activities primarily will include the continuation <strong>of</strong> outreach efforts to members<br />

<strong>of</strong> other staff sections and inactive NALIT members. Efforts will be made to<br />

encourage inactive NALIT members to become involved again by issuing<br />

invitations to the NCSL Annual Meeting and the PDS, and to reach newcomers<br />

by developing an information packet explaining the benefits <strong>of</strong> our organization.<br />

Development <strong>of</strong> mentoring programs and other new activities would enhance the<br />

purpose <strong>of</strong> this committee.<br />

IT Survey Committee<br />

Members <strong>of</strong> this committee will have a two-year appointment. Committee<br />

activities will include evaluating the information presently in the survey, and<br />

updating the types <strong>of</strong> information in the survey. The committee will issue<br />

reminders to members to update their information within predetermined time<br />

frames (e.g. quarterly, annually), and decide the best means for presentation on<br />

the NALIT web page. The committee will also develop additional methods and<br />

activities to enhance the value <strong>of</strong> the survey information.<br />

IT Seal <strong>of</strong> Approval Exploratory Committee<br />

Committee activities will include evaluating new and existing technologies and<br />

processes, and <strong>of</strong>fering an unbiased opinion that NALIT and other NCSL staff<br />

sections can use as a source <strong>of</strong> information. The committee will observe existing<br />

solutions, evaluate positive and negative aspects, and provide estimates <strong>of</strong> effort<br />

needed for implementation. The committee will monitor other states’ technology<br />

activities and utilize experts in those states to provide information to the NALIT<br />

membership. Members <strong>of</strong> this committee will have a two-year appointment.<br />

The initial year will be spent forming the scope <strong>of</strong> the committee’s work, and<br />

start a few initial examinations to report at the 2005 Annual Meeting. The<br />

committee membership will consist <strong>of</strong> a mixture <strong>of</strong> management and<br />

technology specialists so that issues can be examined from all perspectives.<br />

2005 NALIT Staff Achievement Awards Committee<br />

The Legislative Staff Achievement Awards Committee will solicit nominations<br />

and recommend award recipients for the 2005 NALIT Legislative Staff<br />

Achievement Award, based on criteria outlined on the NALIT Web Site.<br />

2005 Nominating Committee<br />

The NALIT Nominating Committee will interview and evaluate interested<br />

candidates and present the slate <strong>of</strong> candidates for election at the Business<br />

Meeting at the NCSL Annual Meeting in Seattle in August.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!