iboss Reviews

We use it primarily for simpler filtering because we're a K12 entity.

The console is cloud-based, which is something I really appreciate. When I first had it, it was a cloud-based console, but we had on-prem appliances, so when we went to the cloud, the management of the cloud nodes that handle the users' traffic and everything was significantly easier.

The console definitely helps us save costs. It protects us from situations where a parent or anyone may say, 'Hey, the student is doing this; your filter isn't working properly.' The reporting feature we have inside iboss is fantastic, especially with the new features in reporting and analytics, allowing us to give a high-level report to a parent or a school administrator. It absolutely saves us money because if we have the data to back it up, no one can really come after us with a lawsuit or anything like that.

The reporting and analytics are pretty awesome, and we recently got the Zero Trust platform. We've just been starting to dive into that because it's something new for us, as they just started offering it to K12 as part of their new package. It's given us a lot more visibility into our computer assets that may be infected with viruses and also shows us people who have unusually large uploads or might be engaging in high-risk activities, such as searches or going to sites not categorized by their web crawler. It's pretty awesome.

I have a couple of thoughts for improvement, but usually when I address them with my rep, they put it into the feature roadmaps because I've been with them for a while, and I typically see that feature get implemented. One thing I would like to see differently with their Zero Trust platform is that some of the AI aspects related to high-risk activities have more false positives. I would like to see the AI tuned a little more. They communicated that the AI is still learning, which I appreciate, but it probably could have been given more time before being released.

I have been using it for around six to seven years.

I don't think I've ever had any downtime with iboss, and they are really good about sending alerts if they do any maintenance on the cloud nodes. Most of my nodes are based all over the United States, primarily on the East Coast, but I do have some in the Midwest and some in the West, like California. It's been pretty solid; I've never had an outage with them, and if I ever had, it's only been once out of the seven years.

The scalability is fantastic; if I start seeing sluggishness or anything like that, I just reach out to my rep, and they connect with their dev team, typically resolving it the same day.

It's very easy to use, and for those times that it's not as easy, their support is phenomenal.

I have a support person that I usually reach out to, but if he's not available and I put in a support case, he usually gets answered within an hour.

The quality of the support is fantastic. I don't think I've had any issues with him nor has anyone on my team.

I would give them a score of ten for the support.

My organization was able to remove legacy tech by consolidating into a single solution. Originally, we were on a light speed, and while upgrading our Internet circuit, the hardware we had could not support the speeds we were going up to. We made a change over to iboss because they had better hardware and better speed for filtering for students and staff. Then, about a year or two later into our contract, we went straight to the cloud, which has been fast. 

Anytime we have any sluggishness, we usually reach out to support or my rep, and their dev team gets on it the same day. We recently had an Internet speed increase, going from sixteen nodes to now having around thirty-something nodes, which saves us money in hardware.

The deployment was done by our team and an integrator from iboss.

It took us a couple of days to set it up, but with the growing pains from going from light speed to iboss, it took us anywhere from thirty to forty-five days to fully adjust to the new interface, changes, and the way that things were being blocked or not blocked.

About two or three people were involved overall in the deployment, definitely one from iboss and two from my team.

The Charge GPT risk protection was part of the Zero Trust platform, which they just introduced me to about three weeks ago, and I don't have enough information to provide anything substantial. However, I appreciate that some features allow monitoring of ChatGPT and other AI sites, and you can also input a message in the console when they are on ChatGPT, stating that these chats are being monitored by Aiken County Public Schools or any message you want, giving users a heads-up that they shouldn't put anything inappropriate in there. We just started with that.

iboss is a fully one hundred percent cloud solution today.

I still think iboss is way ahead of light speed. Since they've implemented Zero Trust and some integrations, the ClassLink integration gives us further analytics into our rostering solution, which is really nice. I don't think light speed can compete with them in this aspect.

I rate iboss a nine out of ten.

We used it for student and faculty filtering on campus.

We were a hybrid environment where we were not fully cloud or on-prem. That caused a lot of difficulty for us where we had to go into one system for some of the things we needed to do and then we had to go into another system for other things we needed to do. Because we needed to do inline filtering, we could not move their cloud-based service. That caused a lot of operability issues for us. For us, it was not a single pane of glass. If you are fully cloud-based, that portion is nice, but if you want on-prem inline filtering, it is not a single pane of glass.

Their visibility in cloud, web, and private applications is dependent on whether you have their client and their certificate on your device. For us, that did not work because we did not have that on there, so we had almost zero visibility into SSL traffic.

iboss is among the few products providing inline filtering where no application is needed on the device. It operates on the network side and is not device-based. This feature was one of the main reasons why we stayed with them for so long. Our school is a BYOD environment, so we cannot install software on those devices. Allowing us to filter those devices while on campus was the real reason why we had iboss for so long.

We were able to see its benefits immediately after we started using it. We went from a non-pay model to a pay model to stay with them because they were providing us with the inline filtering service that we could not get from any other provider.

Our biggest problem with their service was it did not recognize the device and filtering did not always work correctly.

We switched to another solution because of increased pricing for licensing and because of customer service. We also had a problem with a transition when we upgraded from one appliance of theirs to another, but their engineer lost a good deal of our data. We had to manually update the new appliance. We had multiple problems with getting the filtering to filter correctly which we escalated to their senior management of customer service. There was no real action in spite of them promising to look into the issues.

Our current vendor offers an Aware product, a self-harm bullying module included with their service. Such a feature did not accompany the iboss service. This is something we would definitely love to see from them if we ever go back to them.

I used iboss until about six months ago. We used it for probably six or seven years.

We experienced issues during migration. Our biggest problem with their service was it did not recognize the device despite our ClearPass sending information to the iboss box. We had AD authentication set up. It randomly assigned a user to the default filter group, restricting access and requiring users to sign in to be correctly filtered.

You can put a couple of boxes in tandem. So, they are definitely very scalable.

We had multiple problems with filtering, which we escalated to senior customer service management. We had promising discussions about resolving these issues, but no real action followed.

Neutral

iboss was initially provided by our Internet Service Provider as part of their service. We then purchased it on our own. We have now switched to Securly for our school-owned devices, while for BYOD, filtering is done through our firewall vendor.

Our Internet Service Provider recently changed to Securly. It is a part of the member services package that drastically cuts down our cost of ownership.

The initial setup was easy. The full setup took probably a couple of days.

The transition to a new appliance from their aged-out appliance was absolutely horrible and caused us a couple of days of downtime.

Its maintenance involved updating the actual hardware on-prem and doing firmware updates. We also had to do updates to the software portion on our devices.

Initially, our ISP did the integration with us. Later, when we continued with iboss, we took the build from ISP's setup and transferred it onto an appliance of our own, which made for an easy transition.

It was just me taking care of its setup and maintenance.

When we initially used it, it was a part of our Internet Service Provider Ocean's service. They provided it as a member service, so it was at no additional cost to us.

We stayed with iboss even after Ocean left. We decided to pay for the iboss service. We had the cost of purchasing a new appliance along with the implementation and licensing costs. However, the following year, the cost of just licensing was similar to what was paid the previous year for a new appliance along with the implementation and licensing costs.

I would rate it a five out of ten.

We use it for URL filtering to enforce our enterprise Internet use policy. We use it for our current initiatives in artificial intelligence. There's a module in iboss for artificial intelligence we're utilizing. 

We use it for forensics when our internal affairs investigators need historical information on website access. We use their cloud configuration to send our enterprise-owned devices anywhere in the world, and we've enabled the protections to travel with the end user. 

We also have some botnet and malware and other protections through that agent, and we are currently evaluating the iboss platform to see if their zero trust framework and legacy VPN solution will work in our environment. We've been fanning out. Iboss started out with us as just a simple URL filter, and it has moved on to be used in several key critical areas of our operation.

We immediately saw value from the moment we deployed it 15 years ago. The product did precisely what people told us it would do. Over the years, it has grown with us and our enterprise's security function. We have had an excellent, mutually beneficial relationship with this vendor.

The solution saves us costs associated with the aftermath of an incident. That's not to mention cyber insurance claims and everything would go through the roof if these attacks had been successful that we've thwarted with iboss. The benefits are clear. We are thrilled it may help us save money again because we are retiring our legacy VPN. The iboss VPN offers more competitive pricing than the other two vendors. 

Using iboss, we've reduced daily security incidents. We have people in and out of our environment left and right. When they leave the environment, they think it's okay to use an asset that belongs to the organization. The solution has prevented things that otherwise could have been a tremendous loss for us. 

Now, the thing to consider here is that money isn't the only loss we measure because we're a government agency. We measure the effect on our reputation. Elected officials run this place. If we have an incident, people believe elected officials are not doing their jobs, affecting our reputation. It has saved us in that area as well. 

The iboss system is highly reliable. The false positive rates are small compared to some other systems we've experienced through other partner agencies who use competing solutions. 

The administrator's console is laid out logically. New features are added in places that make sense, making the console easy to use from an administrative standpoint. It runs in the background seamlessly for an end user. The only time you know it's there is when you get caught in a policy decision that blocks a connection. 

The iboss console has absolutely improved security. We rely heavily on it for command and control traffic analysis, and we're using their SSL decryption function. We can look inside of encrypted connections to catch and prevent these botnets that are out there. It has saved us a countless number of times.

We are a government entity with a Microsoft contract, so the single pane of glass is Microsoft. When we use any third-party tools, such as iboss, we feed into our Microsoft console, except the URL logs. We keep those separate for many internal reasons. We keep the URL logs, but the malware, CASB, and other information go directly into our Microsoft tenant.

We've deployed the iboss into several of our Azure environments, and it does exceptionally well in most cases. It sees the traffic it's supposed to while ignoring the traffic we've told it specifically to ignore. The only thing we don't do with it is by recommendation from the actual vendor. We do not inspect database connections because of the intensity of those connections. The vendor told us not to look at those. It would probably end up causing latency issues with our connections.

We were an early adopter of iboss' ChatGPT risk protection. We still use it because we've determined that it will work for us. We're working with their development team to enhance the feature sets. We tend to be on the leading edge of things in our field, which is rare for a government, but we're kind of a special group. We tell the vendors when we see things emerging and where they should go with these products. They've been excellent at adding these new features. It captures what we expect, and the features are there that we need.

The ability to monitor and secure these conversations is outstanding. In fact, we've put in the framework to allow us to block content that should not be going into ChatGPT, Gemini, or Copilot. It allows you to force users to go to a particular AI console. In our case, we will force users in the near future to only use one AI platform, Copilot. 

We already know iboss can force users to go straight to Copilot if they try to go to any other platform. That's fantastic. It has a DLP feature that will capture data that shouldn't be leaving your enterprise as well when it finds it in any of these AI chats. 

A positive improvement would be to expand into more areas for product monitoring. You have an agent that resides on the endpoint. They are positioned in a way that allows them to log information directly from the endpoint that they couldn't get in the past. They could monitor the process trees and the event logs and help with the overall detection rates of the product. If the URL is bad, the process on the machine has been observed as bad. 

Fold that in with the risk intelligence they're getting from all of the different subscriptions they are a part of. Now, these security companies subscribe to things like emerging threats, databases, etc. You can fold all this intelligence to decide what's happening on an endpoint. I would love to see them start moving into that space. That would compete directly with Microsoft. Maybe that's why they haven't. Having that ability native within the solution would be great. The other area in which I would love to see improvement is more detailed descriptions of why they block websites.

We have been using iboss for 15 years. 

The solution's stability is outstanding. I can't think of one instance when iboss was the cause of latency.

It's super-easy to scale up iboss. If I tell them, "We just lit up another five gigs of bandwidth," they'll spin up some new virtual gateways and dump them in my account.

I rate iboss support 10 out of 10. They are among the best I've ever seen in the support space. Some vendors, you would imagine, have great support, but it's terrible. These guys are fantastic. Whatever they're doing to train their people is working, and it's always a pleasure talking to these people.

Positive

We were using a competitor's product for several years, and it just got to be unusable, which caused us to go out and start looking for a replacement in the market. And iboss was not even part of our list of competitors that we were going to pilot to see if we could get a better solution in place. They were just at the right place at the right time and made a cold call to us, to the CISO. And he said, hey. This company called me about our pilot. It wasn't on our list, but I decided to call these people, and they won. They won me in the bake-off we did. The product did exactly what they said it would do, and the others did not. So that's how it all started.

Setting up iboss was incredibly easy. It took 20 minutes to unbox and rack them the first time. I turned it on our inline Internet pipe, and it immediately began working.

For maintenance, everything is pushed from the admin console. It's a matter of updating policies whenever policy changes occur in the enterprise. It requires me to edit policies when sites on the Internet don't comply with RFC. This causes problems for the end user. The other maintenance is insignificant. Whenever the vendor releases a new firmware, I simply click a button and schedule the install.

Their pricing is excellent. It fits within our meager security budget for these kinds of tools, and we're pleased with the pricing. Like everybody else, things go up when you add features, and we understand that. Overall, we'd pay a significantly larger amount of money to other competitors in the space if we were to get all the features we have with them right now.

We looked at several well-known solutions at the time. They did not measure up to their claims, which we find to be a common theme with vendors. But I, Iboss, unlike many others, did precisely what they said, and everything went exactly as they said it would. And so they won the contract and have kept it all these years.

I rate iboss 10 out of 10. If you're going with the cloud model, there are two different architectures you can use. You can use the agent-based one, which we use. The other is a direct private circuit that runs straight from your enterprise into their cloud. 

If you're going the agent route, make sure you have a good enterprise software management product in place, like Intune or SCCM for Microsoft or Jamf if you're an Apple shop. There's a million of them out there. Make sure you have one of those in place so that you can easily manage pushing out the agent to your users. After that, it essentially drives itself. The endpoints check-in and get updated automatically per your policies. 

We are a K–12 school district. We have an on-prem box. We use our on-prem box to filter the local traffic for our users, staff, teachers, and everybody on there as well as the students.

We also have a cloud instance. We use Chromebooks here in the district. We use their Chrome plug-in to filter the students' devices, both on-site and off-site. When they take the devices home, they are filtered at home as well.

In terms of day-to-day usage, it is very simplistic. You have a cloud interface. Everything is online. You could sign in, make any sort of changes, and view and do active monitoring to see if there is anything that needs to be done. The initial setup, like with any product, takes a long amount of time because you need to figure things out. You need to figure out what you want to block and what you do not want to block category-wise and weighting-wise, but once it is up and running and you have everything in there, there is not much to do. We are not in there every day. You kind of set it and forget it. Once everything is set up, you just leave it alone unless there is an issue, somebody cannot access a site, some site is blocked, or you want to actively block a new site because some kids found some new game site to get to or whatnot. Once it is up and running, you do not have to do much to maintain it.

The console is very good. You can access everything from it. I like the layout of it. It somewhat mirrored some of the older interfaces, but I definitely like the layout and the ease of use of it, and I never struggle to find what I am looking for.

It did help us a bit with consolidation. We removed the on-premise monitoring or filtering thing that was doing the logging. We removed the logging side of it that was on-premises. It did help us do that because that went to the cloud in association with the actual product to do the filtering itself. They have what they call the reporter and then the actual iboss appliance. Moving that reporter to the cloud helped push everything into a single pane of glass, which made everything a lot nicer to work with for sure.

The single-pane-of-glass console helped our organization improve security. We can get in there and see what sites are being attempted to be accessed a little bit more easily through that single pane of glass than before. Previously, we had multiple tabs open, and we were clicking back and forth. I like the real-time log being associated on the cloud, and I also like that it is accessible from anywhere. If I am off-site at a meeting and somebody contacts me about it, I do not have to VPN in. I can just log in to that site from wherever I am and do what is needed.

iboss gives you great visibility into what is being utilized inside the network. You can see the traffic flow, what sites the kids are accessing, and what sites the staff are accessing. It is a very good tool if you are looking to monitor bandwidth or try to figure out what is being utilized within the network. It would be a big tool if you are trying to do this sort of analysis of data traffic because it does log all that. You get to see top sites visited, top sites blocked, and some of that information, which definitely would give you some insight into what your Internet is being used for.

iboss definitely helped our organization reduce security incidents. It is stopping people from going to sites that could potentially be harmful or contain spyware or malware, or something that could potentially get into the network and cause us problems. It is doing its job and blocking out sites that are potentially hazardous. Our network is safer with it in place.

We could see its benefits immediately. Prior to going to iboss, we were using another filtering product. I was very unhappy with it. It was very clunky. I struggled to get things unblocked and manage it. It became very cumbersome. I was new here at the time, so we started to look at different products. We demoed quite a few products. We demoed Lightspeed. We demoed iboss. We demoed a couple of others. We liked the interface of iboss the most, and we all made that decision. Once we got it in and up and running, I was so much happier because I went from such a terrible product to a good product. I felt like it was easy to manage. The iboss team was very good at helping us get everything implemented and get us going in the right direction to get everything in there. I was immediately happy with it after the switchover. 

From a use-case scenario, what I like the most is the plug-in. I like the fact that we can do the filtering of these devices offsite independent of the network they are connected to, and we do not have to have traffic coming back inside our network. With some of the other filtering solutions that we looked at in the past, a lot of times, if you wanted to filter when the devices were not onsite, you had to funnel that traffic back to your network all the time to send the filtering back to them. I like the fact that the plug-in is just in there, and we can control the devices regardless of where they are. Also, that stops kids from circumventing or jumping onto another network or a hot spot or trying to use a VPN client. It does not matter because the plug-in still blocks them from being able to access content that we do not want them to be able to access.

Their on-premise hardware's network interface is capped at one gigabit, which is sort of a problem. If you stand a filter up where all traffic flows through that, according to them, in order to go above a gigabit, you have to have multiple devices, which in today's IT seems a little bit silly. They could easily put in an SFP port into their device that could accommodate 10 gigs or at least offer a box. It may come at a higher cost because it would have higher CPU and RAM, but they should at least offer a box that would be a single pane or a single device that we could put in the network allowing us to go above one gig. That would be the one thing I would say to them. They would probably come back saying that they have put everything into the cloud, which is a possibility, but it is a lot more work. I like the way we have our configuration set up currently, and I hesitate to go away from it because it has been so successful for us for such a long time. Offering an on-premise device that allows something above a gigabit connection would be one thing that I would ask them to provide. I hope they will do that in the future.

We switched to iboss in 2014 or 2015, so it has been nine or ten years since we started using it.

It is super stable. We have not had any issues with the box, even the older boxes. It is super stable. I have not experienced anything in particular that would tell me that it is not stable.

It is super scalable because we could just pivot at any point and go all to the cloud. That is the one benefit of it. If we wanted to scale to that, we could scale to that. They did say that we could stack another box in there. If we want to go with a two-gig inbound connection or a three-gig, we could stack a third box in there. It is scalable. The solution is absolutely scalable, but there is a cost of that.

They are great. They get right back to you. Every time I have been on a call with them, they seem very knowledgeable. We can do a screen share or not. I always walk away from those support calls with a little bit more knowledge than I had about the product before, which is always a good thing.

Recently, we were dealing with something, and I got to know that there is a pack file where you can exclude certain traffic for monitoring because it fills up the logs quite quickly. I did not know that was even there. It might have been a new feature, but they showed us how to do that. I utilized it probably four or five months after the call because I was working on something and I thought I could use that pack file. When I get off those calls, I tend to pick something up that I could put in my pocket and carry on, and down the line that might come in handy.

Positive

When I originally started here, I used SonicWall's firewall. They had a built-in content filter. I used that, and there was this old product that was here when I originally started, which was MX570 or something. I cannot even remember what it was. Those were the two previous filtering applications that I had used.

It was fairly easy. The iboss team was very good. Support worked with us very well and helped us get everything going. I did not have too many problems. Their team did a great job of helping us, and we rolled it out pretty easily.

It probably took us more than a day to get it in place, but it took us several weeks of tweaking the different categories and weights. We set up blocking for what we wanted to block and created our groups and other things. It took us a couple of weeks to configure everything and figure out what is not being blocked, or what is listed as education but it should not be. We had to go through that and work through those problems slowly but surely over time.

The plug-in does require some maintenance. When they release a new version of the plug-in, it needs to be updated. We do have it set to auto-update and whatnot, but we had some issues last year with a site being blocked, and it was weird. We reached out for support. They helped us through it, and we had to unpublish that version and then re-push a new version of the plug-in and make some configuration changes on the backend in Google Admin Console to make sure that they were being filtered properly into the right groups, so there is a little bit of maintenance. You do need to go in there and periodically make sure everything is going as expected.

We did it all in-house by ourselves.

I do not know whether it helped with cost reduction per se because we probably pay a little bit more now. Everything was on-site or on-premises earlier. We paid a licensing fee when we initially set it up and then did a five-year agreement or a three-year agreement. Through the renewal process and going to the cloud, it did end up costing us a little bit more because we are paying per device for that. As far as I know, we are paying per device for the plug-in for Chrome, so I do not know if it is much cost-saving, but I do like the layout of it.

I do not know what we renewed at the last time. It is probably in line with other solutions, but I do not deal with the financial side. I implement the product, manage the product, and also select the product, but somebody else takes care of whether we can afford it.

Lightspeed was one we looked at. The Palo Alto firewall had some sort of thing. We definitely looked at iboss and at least two or three demos of competitors to iboss.

I liked the interface of iboss. I liked the configuration of how it is laid out. I also reached out to a couple of other people. We are in the K-12 school district. We have some friends in other districts who were using the product and had given good reviews. I compared that with some of the other districts that were running Lightspeed and a couple of the other ones. Overall, after looking at the product and then getting recommendations from some outside people, I just thought it was the right path to go down.

Be prepared to work through some problems with pages being blocked or sites being blocked that were not blocked in another filter. Have everything ready to go. I got everything that I needed to be unblocked.

You will have to tweak it, so be ready to tweak it and embrace that. If you run into any issues at all, contact their support. They are good, and they will be able to help walk you through figuring out where you are being blocked. If you run into any sort of thing, be prepared to tweak it. For the first few months of having it in place, you are going to be in that interface a lot. Once you get that all configured, you can just set it and forget it.

I would rate iboss a nine out of ten.

We are a PreK-12 public school district, and we use iboss to filter internet content for our students at home and staff member devices to ensure they do not access inappropriate sites.

iboss alerts us to activities that we would not necessarily know or monitor, such as attempts by users to access proxies to bypass filtering. 

I am sure it saves us costs because it prevents students from loading malware. It saves the amount of time it would take to bring these computers back, rebuild their operating system, and send them out. 

We cut down on staff issues or malware because we are blocking that actively. We let it block things by category. We are preventing all installs of things that would cause work for us. It has cut down about 15% of our time in managing workstations. iboss has reduced security incidents by 25%.

iboss is pretty scalable. They provide good support. The case managers you work with to coordinate what you need are pretty good. They are responsive.

As with any software, there is a learning curve. Overall, it is pretty straightforward. It is web-based. It is easy to use.

I have the same complaint about them that I have about other software companies. Sometimes when you call in support, you get someone who is just following a sheet. It feels like a runaround. You feel that you are running into that support wall. This 'runaround' can be bothersome, but once the sales rep is involved, the issue is usually quickly resolved.

I have been using iboss since 2015, so it has been around eight years.

Since moving to the cloud, we have not experienced any downtime. When it was on-premises, we encountered a hardware failure that took some time to work around. It took half a day of downtime, but the transition to the cloud has been stable. Now that it is in the cloud, we get notifications. They keep us in the loop about when they are having problems, but so far, their problems have not taken us down.

I would rate it a nine out of ten for stability.

iboss is scalable, and increasing the number of devices is straightforward as we only need to inform our representative to adjust capacity. There is a fee associated with that.

We have about 12,000 users. We are in one county, and we have 21 sites or physically different addresses that we manage. All those devices have iboss.

Support is generally good, but the initial engagement through standard protocols can be cumbersome until our sales representative intervenes to assist.

Positive

iboss has been our main vendor. We had another vendor's built-in content filter, which was limited and site-based. We are using iboss globally for filtering our devices off-site.

When we originally got it, it was on-prem. Over the years, we have moved to the cloud. When it was on-prem, it was hands-on. You build an installer and send that installer out, whereas now, they take care of everything. In the cloud, it is fairly straightforward and quick.

The initial deployment of iboss took about half a day, with about a week to fine-tune the settings. Migrating to the cloud took an hour and a half. It was very quick to do that. Making sure everything worked after going to the cloud probably took two or three days. They stuck with us the whole month, so it was pretty good.

In terms of maintenance, we used to have to go in and update the devices for the clients. Since migrating to the cloud and within the last two or three years, they have the ability to auto-release updates. You just need to select the channel you want.

We are on a stable channel. We just sit back, and literally, it takes care of itself from that point.

It is hard to put a number on the ROI, but there have been about 15% time savings overall. 

We have not priced the solution recently, but they were competitive with other vendors in the past.

I would recommend iboss because it has been stable. We have not had any major issues. It served us well during COVID. When the home devices of others were collapsing and not working, all of ours worked.

I would rate iboss a nine out of ten. There is room for improvement when it comes to the support aspect.

We use iboss for cloud proxy, CASB, and SSL inspection. I am gradually evaluating the zero trust feature of it.

iboss helped us consolidate our security solutions that were previously scattered across different platforms. Previously, we had different solutions for CASB, SSL inspection, proxy, and other functions. This consolidation did not significantly reduce the costs, but it did help.

iboss has significantly lowered the number of security incidents. It is crazy how much it blocks and how much it is aware of the outside dangers. It has been helping us a lot.

We were able to realize its benefits within a month and a half. In the beginning, I had to work hard to get it up and running and ensure that people other than me could also run it. From the users' perspective, the benefits were seen right away, but from an admin perspective, it took us about a month and a half to get going and see its benefits.

There are a lot of valuable features. Cloud proxy is valuable, and SSL inspection is also valuable. It is pretty heavy to keep track of it all, but once you get it up and running, it is pretty good. In terms of ranking, I would say that Cloud proxy comes first, followed by SSL inspection, and then CASB.

It is fairly pretty easy to use once you get around it. It took me probably a month to get used to it and get the hang of it. As with the other cloud providers, the UI changes a little here and there every once in a while, so I have to keep up with that. Other than that, it is fairly easy to use. Everything is straightforward. We use their web admin console.

We can integrate with a lot of cloud solutions but not as many as I would hope to. We have a lot of visibility into the major ones, such as Microsoft or Google solutions, but they still have a way to go in getting it integrated with other third-party applications and getting visibility into them.

I am currently doing a PoC of the zero trust aspect of it. Compared to other similar solutions, it is hard to get around each feature. It takes a while to get used to it. Configuring zero trust requires a lot of manual setup, whereas with other solutions, that comes prepackaged. If they can reach the other vendors' level in regards to setting it up, it would be good. That is something that I want to see improved.

We started using iboss approximately three years ago, and including the proof of concept, it's been about four years.

In terms of stability, iboss has been stable for end users for the past couple of years. Initially, there were some issues with agents not starting up, but for the past couple of years, it has been stable for end users. However, on the admin end, we have had a couple of problems with replacing the SSL certificate, which was a big hassle. Additionally, we lost some proxy access logs due to cloud node updates.

We have been running it with two nodes since the beginning and have not had a need to scale beyond that. The only thing that we have scaled is the log partition. That was pretty fast. That was done in about a week after we ordered it. According to what I have read, the scalability of the node is supposed to be fast and reliable, but we have not implemented it yet.

Their support is very good. It is wonderful. They are very fast. I have not seen anything faster than iboss support. The quality of it is exceptional. They go a step further to investigate issues on a case-by-case basis, which has been a tremendous help. I would rate them a ten out of ten.

Positive

We did not use any similar solution before. 

When I joined this company, iboss was not even in the talks. About four years ago, we had to review all our Internet security solutions. I was the one who did the PoC, and I was the one who implemented it. I was the one who pretty much got it up and running with the help of a few people.

The initial setup of iboss was fairly easy because we used distribution software to install it across all clients. It took us about a month from start to finish.

Maintenance-wise, there is not much. I check the admin console every day, but in regards to node maintenance and agent maintenance, everything is done automatically on the iboss end. That is pretty good.

The implementation was carried out in-house with the help of the iboss support team. It was a team effort, involving probably four or five people.

It is not expensive, and it is also not cheap. iboss is priced right in the sweet spot for the number of features it offers.

My company is strict on spending. We cannot go ahead and adventure on a lot of different solutions. iboss was the solution that fit our price range and requirements, so we went for it.

My advice is to thoroughly do proof of concept of iboss because everyone has different use cases. To be able to use iboss smoothly, it is crucial to identify all the small settings and parameters during the PoC phase. Some settings are challenging to change once you go live.

I would rate iboss a ten out of ten. 

We use iboss for the proxy solution. I used iboss in my organization to block a few sites for a few of my employees.

Content filtering is the most useful feature of iboss.

Sometimes the agent stops working in iboss, and we have to reinstall the agent. This is a hiccup that iboss should improve.

I have been using iboss for the last two years.

iboss is a stable solution, and we didn't face any major outages with the solution. I rate iboss a seven out of ten for stability.

iboss is a scalable solution. We deployed it for around 300 users, and there's no limitation on the number of users.

The solution's technical support was pretty good. I rate the solution's technical support a seven or eight out of ten.

Positive

It is easy to deploy iboss on any client's machine. However, configuring the solution is a bit complex.

The solution's end-user deployment is pretty easy and takes five or ten minutes.

We used iboss on our private cloud, but since iboss is a managed service, they provide a public cloud platform for the solution.

Overall, I rate iboss an eight out of ten.

The solution is a corporate proxy server, an intelligence proxy.

From a corporate perspective, I understand that it's important to keep the company data safe. From a corporate point of view, it's a good solution.

The solution is stable.

The solution can scale. 

It was a very easy product to install. It can be deployed very fast.

Technical support is okay in terms of the assistance they provide. 

I've been using the solution for one and a half years at this point. It hasn't been that long just yet.

As simply an end-user, I cannot speak to its stability, however, I have not had any issues. I would say that it is more or less stable.

I'm not managing the solution; I'm only using it. Therefore, I cannot speak to its scalability. That said, from what I understand, the solution can scale. 

All computers and servers are using the solution. I'd say there are about 100,000 users on it in our company.

I've been in touch with technical support and I've found them to be okay. I have no complaints as to the level of service they provide. 

The installation is very simple and straightforward. It's not what I would consider being complex or difficult. 

The deployment is fast and can be done within minutes. 

Our deployment was handled centrally by the global team. I'm not sure how many people were assigned to deployment and maintenance duties. 

I don't have any opinion on the price or any insights into the pricing. I'm mostly just a user. Licensing would be handled by management. They may have a yearly licensing agreement set up.

We did not evaluate other options before choosing this solution. 

As we are using the cloud deployment model, we are always on the latest version of the solution.

I'd rate the solution at a seven out of ten. It's very useful for corporations.

I would recommend the solution to other organizations.