Cisco ASA three inside networks on three different interfaces to access

what is the reason for setting all the security interfaces at the same level?

Normally, the outside (internet-facing interface is set to security level 0
the inside (most secure) normally set to 100

and a dmz usually set to 50

commands are:

interface Ethernet0/0
 nameif outside
 security-level 0
 ip address XXX.XXX.XXX.XXXX subnet mask
!
interface Ethernet0/1
 nameif inside
 security-level 100
 ip address 192.168.1.1 255.255.255.0

interface Ethernet0/1
 nameif dmz
 security-level 50
 ip address 192.168.1.1 255.255.255.0

This is not good also:

access-list ITGROUP_access_in extended permit ip any any
access-list BlueRidge_access_in extended permit ip any any
access-list ETCTV3_access_in extended permit ip any any

the above allows all traffic in, with no restrictions

you want to use static nat and allow inbound access to only certain ports and services  i.e mail, ftp
static (inside,outside 111.111.111.111  192.168.1.1 netmask 255.255.255.255 0 0


access-list acl_in extended permit tcp any host 111.111.111.111 eq smtp
!
The above example statically maps a server with the public address 111.111.111.111  to an inside address of 192.168.1.1  and the acess-list allows only inbound traffic on port 25   this is an example for a mail server


then bind the access-group to the outside interface:

access-group acl_in in interface outside


I am assuming these are your >outside to inside access rules

If not, then get rid of these (if they are inside to outside rules, they will often prevent traffic from inside flowing to outside)

by default, the asa allows all traffic from inside to outside unless you configure restrictions via access lists

Remove these below:

access-list ITGROUP_access_in extended permit ip any any
access-list BlueRidge_access_in extended permit ip any any
access-list ETCTV3_access_in extended permit ip any any
access-group ETCTV3_access_in in interface ETCTV3
access-group BlueRidge_access_in in interface BlueRidge
access-group ITGROUP_access_in in interface ITGROUP


!

This is an internal firewall. Right now I am not worried about allowing traffic in from the outside world. I am wanting to allow traffic between my internal interfaces. I know you can use the {same-security-traffic permit inter-interface} command, However I only want some of the internal interfaces to have complete access to the other internal interfaces and soem just to have port 80 -- 3389 --- telnet.

I wanted to add that I currently have a firewall in place. I am trying to setup my new ASA to test before putting it in place. My first step in setting it up is to get the internal networks to talk on the port that I want. I will then do my access rules for the outside interface