How To Gain Comprehensive Visibility and Security for Your Hybrid Environment

On-Demand

Video Transcription

Reggie Best:
Hello, this is Reggie Best, president of Lumeta Solutions with FireMon. We’re going to go ahead and get started in just a few seconds. This is our Lumeta CloudVisibility webinar. So, I’m going to go ahead and get started. This is Reggie Best, again, president of the Lumeta business inside of a FireMon. A couple of housekeeping things before we jump into the Lumeta CloudVisibility content. We are going to have an overview presentation of just a handful of slides, and then I’m going to hand off to my colleague Ed Young to give some demonstrations of a visibility solution. We’re hoping that this allows you to generate some questions and we’re going to be happy to accept your chat questions. So, just send them in and we’ll cover them at the end of the prepared content and the demo.

Reggie Best:
I also want to point out that there are some attachments and links in the app. You can go ahead and take a look at those, gives you some little bit more information on Lumeta CloudVisibility offering and the free Community Edition of Lumeta CloudVisibility as well, if you want to download and start using that in your environment. So, let me go ahead with those housekeeping and just jump right into the, what we’re talking about today. Some of you may know Lumeta from its background in providing enterprise-wide visibility and to helping organizations get an understanding of their threat surface within their enterprise by providing a view of what is the layer three infrastructure, layer two infrastructure, a census of all the assets within those environments and profiling of what those attached devices are. That data has been very, very useful to security teams in terms of helping them gain a deeper understanding, particularly as their network infrastructures became more and more dynamic with virtual implementations, mobile wireless infrastructures and so forth.

Reggie Best:
More recently we’ve started to see most of our customers offer access to cloud services within their organizations. Any of the so security teams that we’ve been dealing with have said, “We don’t necessarily have the same level of visibility of what’s going on within those environments as we need, and as we gain on from your offering on the enterprise, within the enterprise itself.” And it’s very, very clear that the train has left the station in terms of adoption of public cloud infrastructure services. You see the rapid growth of those services in use by enterprises for varieties of different applications and use cases. And with the availability of those services from all of the public cloud providers, Amazon, Azure, Google, with more and more services coming, there’s no sense that that is going to slow down.

Reggie Best:
Most of the analysts in the market are representing to enterprises that they have a shared responsibility model. The cloud providers are responsibility for the security of their underlying cloud infrastructure, but security teams, their neck is still on the line within the enterprise in terms of what’s going on within their own cloud infrastructures, within their own virtual private cloud environments. And it’s there where Lumeta comes in and is with Lumeta CloudVisibility, bringing that context into what we are already helping the organization with on the enterprise side, because the general view is that for well into the future, we’re going to be dealing with hybrid environments. Security teams are going to be responsible for data within the firewall infrastructure in their own data centers and their own networks. But they’re also going to need to provide a sense of securing the cloud infrastructure that’s attaching into those enterprises as well.

Reggie Best:
And some of the huge issues that you can identify there that are occurring relate to misconfigurations, shadow IT infrastructure that’s not even being seen, vulnerabilities in terms of configurations or accesses to the internet that might be occurring within those environments. The objective of Lumeta CloudVisibility is to bring those issues to light and to provide that visibility in context with what we’re delivering to security and operations teams already on the enterprise. So, some of the needs that we’ve heard in discussing with these types of security teams and these large organizations, is that they need to have an understanding of risk of vulnerabilities and general situational awareness of what’s going on. And there’s a need for that to be provided on a single pane of glass or available in a single platform. And in many respects to be a kind of single system of record with authoritative data about what’s going on in the physical, the private/virtual environment, as well as public and multi-cloud infrastructure.

Reggie Best:
In many of these environments because the cloud deployments and applications have been very, very siloed, you have a broad number of teams, a wide number of teams who are sort of doing their own thing. You have an administrator of certain number of VPCs who may have one or multiple accounts. And the security group who are responsible for the enterprise, don’t really have visibility of each and every one of those silos. So, the ability, if you identify risky assets, to be able to attribute them to a particular team is very, very important. Who’s the person or group or application team that I need to go to, to remediate what I might have identified or to reconcile what I might have identified in this particular virtual private cloud instance? Another key capability that they’ve asked for is how are these VPCs and these cloud instances attaching into my enterprise, and how are they in turn attaching to the internet?

Reggie Best:
There might be policies that certain traffic has to come in, here pin so to speak into the enterprise before going back out to the internet. If you’re not looking for those or understanding those paths that are occurring from a virtual private cloud environment or to the internet, then you may have paths in fact that are leaking. And if you’re not monitoring those paths, you’re opening yourselves to the potential of enterprise data leaking out or bad actors being able to leverage those, not only to get to the cloud infrastructure, but to get all the way through, into the enterprise infrastructure, because they’re typically attached over virtual private network connections to those cloud environments. And then, certainly one of the other critical needs is not to be an island unto yourself with regard to the data that you’re collecting data. Data integrations, which is something that Lumeta has been providing into inter-host mobility management, endpoint detection or response, into SIM and so forth.

Reggie Best:
Those same types of data integrations and the ability to share what you’re seeing from a visibility perspective, with other tools that are responsible for scanning for critical vulnerabilities or for viruses and so forth is very, very important. And also, being able to provide that data context into enterprise security data-lakes, which we’re seeing very commonly in larger organizations is also a critical data integration that we’re anticipating. So, this is the backdrop of the kinds of needs that we’re being told by security teams they have in terms of bringing that hybrid cloud visibility in their environments. And so, what we were talking about today as in terms of the overall FireMon platform, which includes the network security policy management components, also now includes Lumeta where we’re providing that real time, situational awareness, real time discovery of the hybrid environment and enabling the delivery of the risk, security and vulnerability data into technology partner integrations that we’ve developed those integrations through restful APIs available within the Lumeta platform.

Reggie Best:
We’re also leveraging those same APIs to deliver that visibility and context into the policy management portion of the portfolio as well. So for example, if we see a network infrastructure device like a firewall or router within the cloud environment, we can provide that context into security manager so that it is able to provide a complete policy management across the hybrid enterprise. So, this is full portfolio where Lumeta is providing the situational awareness discovery component is valuable to the policy management infrastructure, as well as to technology partner integrations that we’ve provided. And how do we do that? In the cloud context, we’ve developed a new sensor called a cloud scout. That cloud scout is deployed within a cloud environment. And it’s very similar to how we’ve deployed in enterprise environments, where there’s a sensor that sits on the network and that sensor or scout is responsible for protocols visibility within the physical infrastructure.

Reggie Best:
Well, within the cloud infrastructure, we’re attaching to various APIs that are provided by the cloud providers. And those APIs enable us to look at configuration data, to look at audit data, to look at sub-net information and based on our analysis of that to understand, are we identifying vulnerabilities in the way that, that particular instance or that particular virtual private cloud environment is being configured or very importantly are we networking to it? Are we creating paths to it that are in accordance with policy, or that are maybe a little unusual? Maybe there are too many connections to the internet from a particular VPC when there should only be one, or maybe there should be none. Those are the kinds of things that we would be able to identify via the data that we’re collecting from that cloud situated scout and providing back into a command center, which is in the security operation center and where you’re providing that oversight of what you’re connecting to in the cloud environment, along with, in parallel with what you’re seeing on the enterprise side as well. Many use cases for that certainly risk and vulnerability management programs.

Reggie Best:
I had talked about security data lakes before where the data from Lumeta is one contributor to that data lake, the authoritative system of record for posture census device profiling. Certainly broad use cases in OT and manufacturing environments or IoT in the more general case, network segmentation issues and highlighting those to security teams again, pretty critically important as well. So, within the cloud visibility element of that, some of the key features there relate to multi-cloud. In most organizations, they’re not just dealing with one cloud provider, while there might be one cloud provider, for example, AWS being the market share leader, we certainly see them in a lot of our customers situations, but we also see Microsoft Azure and increasingly Google Cloud Platform as well. You have to provide multi-cloud and multi-account roll up for the security teams so that these risks and vulnerabilities can be assessed in context.

Reggie Best:
And my colleague Ed is going to show some of the risk scoring and how you can rank your instances that you’re identifying by riskiness to the organization. So, that assessment of risk across all of the cloud infrastructure is a critical component. Being able then to allocate that risk or attribute that risk to a specific identified owner or project team so that you can discuss remediation of that particular issue with the data that you’ve collected in an interactive conversation and interactive dialogue with that particular team. And what are some of the security risks and vulnerabilities that we can highlight? Well, perhaps we found an endpoint or an instance within the environment where Amazon Inspector or Qualys, or Tenable have not been configured to actually examine and do deep credential scanning of that endpoint. That’s something that can be highlighted so that, that particular instance can then be spun up or Inspector instance can be spun up to monitor that, or if you’ve got an any-any rule or unusually permissive configuration of a security group, highlighting that as a risk and a vulnerability to the organization.

Reggie Best:
Perhaps you have a certain set of blacklists of IP addresses that you should never be able to connect to, or a violation of a set of whitelists that a particular instance should be able to communicate with usually. If you see a violation of that, that’s something that can be highlighted to a security team for remediation and maybe indicative of a leak in connection, for example. So, that integration also that data directly with, for example, AWS Inspector so that, that piece of the process is fully automated, is another element of Lumeta CloudVisibility. We can automatically send a message to Inspector so that that Inspector can either trigger a scan or so that a configuration and deployment tool can be used to actually spin up Inspector within that environment. Similarly, with Tenable or Qualys if that happens to be what you’re using in an enterprise environment, we can provide that data back into the central command for Tenable or Qualys so that they can gain holistic endpoint coverage.

Reggie Best:
And again, in the demo, we’ll highlight how we do some of that with Amazon Inspector in particular, in this case. Some of the core capabilities data aggregation in a single place, we are collecting and aggregating data from a number of, in this demo, we’re showing Amazon Web Services, but Configuration data, CloudTrail data, and AWS Inspector data aggregated together, analyzed and refined into a target set of your riskiest assets within the environment. We can also do a series of compliance checks. I mentioned white and blacklists for protocol imports and use, IP addresses, wild cards, things that have a too permissive and open to all IP masking and so forth. So, maintaining your compliance across a broad range of dozens or hundreds of accounts within an organization is something that can now be simplified through the use of Lumeta CloudVisibility.

Reggie Best:
We can also as I mentioned, check for public internet leak paths and other risk findings from Amazon Inspector and from a forensic perspective, look at recent configuration changes and how those may have increased your risk within a particular environment. And then, certainly one of the key capabilities that we’ll talk about briefly today is all of this functionality we’re making available in a Community Edition, which is freely available for download today from the firemon.com site. And that’s very useful for evaluations and for initial deployments of functionality up to 10 accounts and up to a hundred instances can be supported with the Community Edition of Lumeta CloudVisibility. And again, that’s available today for download from the firemon.com site. So, I talked a little bit about the Community Edition. This shows you some of its scalability, 10 accounts, a hundred instances, 2,500 IPs.

Reggie Best:
There will also be a marketplace edition that is available as well. And you can see how that compares with some of the capabilities of the full CloudVisibility edition for organizations that expand beyond the needs of the Community Edition. The objective here, we have customers who have in excess of 500 accounts and in excess of 20,000 instances that are being used every day within public cloud environments. And certainly the objective of the CloudVisibility solution just as we’ve scaled to more than a million IPs in enterprise environments is to support those very, very rich, very, very scaled out cloud deployment, and to provide that consolidated security risk and vulnerability information across that hybrid enterprise back into a security operations team in a security operation center. So, I’m going to turn the conversation over at this point to Ed Young who’s product manager for Lumeta and Lumeta CloudVisibility and he’ll walk us through the deployment model and then jump into a demonstration of some of the capabilities that I highlighted in just now. Ed?

Ed Young:
All right, thanks, Reggie. So, yeah. Hi again, my name is Ed Young product manager for Lumeta. The final slide here that we’re presenting is just a basic understanding of the deployment model for Lumeta and how we are giving you the complete visibility into your enterprise, your hybrid, your cloud, your software-defined networks. We have in the sock in your localized area where your security professionals are sitting, we have a command center and the command center is where you’re going to do all of your configuration, your analytics, your reporting capabilities, and aggregate all your data. We also have a smaller footprint of Lumeta, and it’s a scout.

Ed Young:
And the scout is utilized in many ways to gain that protocol visibility into various locations on your network, whether it’s remote location, specific subnets, your cloud environment, the cloud scout, which Reggie has talked about throughout his presentation will peer with your BGP routers, will get OSPF updates. And it’s all about giving you flexible options and getting complete visibility inside of your enterprise, and being able to discover all your network devices, all your network infrastructure and being able to manage those devices and removing any invisible networks, any shadow IT, any old labs that are remaining on your network that are still functioning, but aren’t under management by your security platform and therefore causing you a risk inside of your environment.

Ed Young:
So, I’ll start to share my screen, and we’ll go through some of the dashboards and the information that we’ll be presenting to you from your Amazon cloud instances and the types of information that we can share on a single console, both your enterprise and your cloud environment, one location, to be able to tie together both environments for a single pane of glass for your security professionals to manage and remediate. Right.

Ed Young:
Okay. So, if you’re familiar, a lot of you’re familiar with our Lumeta visibility dashboards. Now, in the offering that we had previously, where we would bring forth devices on your network through active scanning, passive scanning, SNMP credentialed access, things of that nature, where we brought all the visibility to your devices on your network inside of your on-prem enterprise environments, we’re now partnering inside of AWS using the API capabilities to deploy a cloud scout. A cloud scout is an AMI deployable from the marketplace, from the shared areas, so that you can deploy the AMI inside of your environment and connect it back to our command center in order to take advantage of the connectivity that we can provide for you and bring back these vulnerable risks inside of your environment and making sure that you are compliant inside of your security posture.

Ed Young:
The top widget that we’re showing is based on security group risks. So, inside of AWS, we’ve followed along with some best practices, customer feedback, subject matter experts, industry standards, and level of different criteria to assemble security group risks. And you’ll see that they’re sorted by the number. So, the top one has 26 security group risks called out. So, this could be a violation of 26 separate rules or 26 violations of a specific rule inside of your AWS environment that are specific to that instance. And as we go through, these are summary dashboards, but we’ll drill in deeper in just a moment after we go through the summary views and show you how you get more information specifically to that instance, that then you can take action on and remediate anything inside of your environment that’s causing a risk to your security posture.

Ed Young:
As we scroll down through the dashboard, the second and third widgets are showing both the inbound paths and the outbound paths specific to those instances. We were showing both the incidents ID, the inbound path, public IP address, and private IP address should it be assigned to here and showing you how many inbound paths and how many outbound paths are available to your specific instances. So, on the left side, in the pie chart, you’ll see an inbound path. We have two… We have a set of devices that have two inbound paths to it. And more importantly, on the lower part, we have three outbound paths to some specific instances. That may be okay in your environment. More than likely though, if you have multiple inbound and outbound paths to a specific instance, it’s probably a loose posture, as far as your security is concerned. And you want to go and investigate that and see if you truly want to have those types of access paths to your instances inside of your cloud environment, or if you want to shut that down and reduce it down to a single path.

Ed Young:
Further down is a summary risk dashboard. And as you hover over it, you’ll see the type of risk factors that these particular instances fall under. And it’s a summary count. Again, so we can click on these and drill in and see which devices in which instances fall into these categories. Just another representation of how you can go risk category by risk category and drill in deeper to find out how you want to handle your configuration and make sure that as Reggie pointed out earlier, that you don’t have very permissive rules, any large sub-nets availability into there. So, you want to make sure that your instances are under clear security posture and that you have restricted access to these various locations. As we scroll down further this is more information, again about the inbound and outbound paths and broken down into category. So, how can I get to my instances or out through? Is it, am I utilizing internet gateway, virtual gateway? Is it through a NAT rule? How is that configuration in my environment? And again, if we click on into there, it’ll give me the summary information of those instances that fall under that particular category.

Ed Young:
Further down, tying in together with Inspector, Amazon Inspector, as Reggie had mentioned is the vulnerability management system for Amazon. So, we are pulling the Inspector product inside of Amazon to not only give us inventory list of what Inspector knows about, but do we have the Inspector client installed? Is it active? When’s the last time it was scanned, should it be scheduled for a new scan? And as we scroll over, we’re also pulling in the categories of high, medium, and low vulnerability categories that have been reported by the Inspector product. If I have an Inspector agent out there on some machines yet it’s turned off, is that a red flag for me? Should be. Maybe a bad actor has turned off its Inspector device, it’s Inspector agent in order to cover his tracks. So again, elevating the risk factors to the security professional for them to investigate further and remediate any issues inside their environment.

Ed Young:
Finally, the final widget is an instance inventory. And this is basically a culmination of everything you’ve seen up on top. And so, we could go left to right in various categories. And this is very… The flow should be very familiar to AWS administrator based on the console and look and feel that you’re familiar with inside of Amazon and AWS based on your provider, your account ID, your instance ID, IP addresses, names, region that it’s affiliated with, and then some of the information that we showed earlier about the security group risks and security group IDs. But the last part I wanted to point out is the attribution that Reggie also alluded to. So, now we can also show utilizing the tagging capability inside of AWS functionality of what’s the owner, what’s the purpose of this instance, and what’s the contact information for that?

Ed Young:
And again, this is going back to being able to take actionable items on a security violation for the web server or database server that does not have the proper compliance to our security posture within our enterprise, within our company standards. And I can contact these people and who are responsible for the instance, who have spun up the instance and give them instructions on what we need to do to become compliant. And so, if I don’t know who owns it, my choices are pretty limited to either shutting it down or letting it go and be a security risk, but at least now I have a step for remediation and be able to contact that person, try and make it compliant and keep that instance running for the function that it was meant to do.

Ed Young:
Okay. So, this is the summary dashboards, as I stated, but what we can also do is we can drill down. So, now I want to go into the incidents details and it will bring me into the screen, so I could get granular information about this particular instance so that I can go and make remediation steps or whitelist or blacklist, depending on the information that I garner from going into a deeper dive. So, here’s our Inspector dashboard, again, a lot of the same information as what we saw before the inventory of what the instance details has. And if you see over here, I just want to point out that we have a column here for risk. And if we hover over the risk, because it’s a list of risky factors that are associated with this particular instance, I can then look through there and get a better understanding of why we’ve considered this a risky asset and what type of violations that this particular instance is showing to me. And now I can go in and take some action on it.

Ed Young:
Similarly to that, if I go on to the security tab, here’s a detailed list of all of the violations of the previous dashboard that I had showed. So, this is a security group violation where I showed a summary count of 23, 10, 13, depending on the number of violations. And now, I could go through and I could see exactly what violation and how many of those violations brought us up to that summary count. The final, a bit of information that we bring out is the interface information based on inside of AWS. So, I can give public and private IP addresses. I can put, if I have multiple interfaces, they will be listed here. Mac addresses, interface IDs, the status, giving you complete visibility into your cloud and your cloud instances a lot like you had seen previously from Lumeta in the past about your enterprise devices, tying them together and being… Taking it an instance and providing device type information to those instances for you to be able to categorize it and implement any sort of security features and or posture that you need to remediate against.

Ed Young:
Okay. Additionally, with our summary dashboards and our details inside of our summary dashboards that we just went through, we have a visualization capability for our for instances. So, it’s based on sort of a containerized view of what sort of category you’re looking at. So, we’re grouping it by this, the false out to group by region. But as you can see we can go by provider strictly to AWS, accounts region, or we go VPC ID, and then we could blow it out into a larger set to see, get a visual representation of what’s out there, what’s in my cloud environment? I can double click on the different instance IDs, or I’ll go a little higher up. I’ll go… Oh, I’m sorry, we’ll go back to the region. And where we have a larger subset as I hover over, I get basic information about the region where it’s located, but I double click on it and there’s all my VPCs inside of that region.

Ed Young:
Again, with the simple hover, I could get the basic information right at my fingertips of what we know about that device or what we know about that instance and what we can bring back to the user. You’ll see the security group violations for this one, particularly is from inside of here, we can go to device details and bring to the screen that we had just shown previously that you’re familiar with. So, there’s a lot of flexibility on how you drill down and how you get through the information in order to be able to bring to the surface, any sort of information that you need to uncover or route in the instances around the risk parameters inside of your cloud environment and how you’re going to take action items on it.

Ed Young:
And finally, the configuration. So, the scout and the cloud scout are a deployable tool used by the command center. So, the cloud scout will be deployed via AMI inside of your cloud environment, to which we are integrating with and connecting to. So, this first section is simply the acceptable credentials to allow my command center to communicate with the cloud scout. And once it’s set up, I can set it up on a polling interval of however often I want to retrieve the information in my environment. And that could be broken up per cloud scout. If you have multiple cloud Scouts, you can make these pulling intervals at separate times. If you have a higher risk area, a more locked down area, and you want to have more frequent updates on it, you can break it up like that.

Ed Young:
Second tab is we’ve got the credentials, and this is strictly about your Amazon credentials. This is how you have traditionally interacted with your AWS accounts. Inside of your instances, you’ve gotten information is how you spin up your instances. This is how you manage your AWS environment. You’ll see two basic credentials areas where we’ve added a single basic credential to gain access to this particular region. But if I go to add the cloud credentials, I get the ability to add basic role or instance. And role is a kin to the AWS organizational capabilities. So, if you have… If you’re utilizing AWS organization feature inside of Amazon, you can use that and populate large number of accounts and instances information instead of going one at a time. So, we’re working with a lot of the same authentication methodology that AWS provides for you. We’re able to do that inside of our environment as well.

Ed Young:
And finally, configurable risk parameters. So, we’ve talked a lot about how we’re servicing risky assets based on configuration, inbound, outbound paths, security group violations, various types of risk to your environment, to your security posture. But in specific use cases, you may have a need for a more permissive access rule, or you may have a need for multiple paths, inbound and or outbound. So, what we’re giving you here is the ability to configure to your own security standards, your own security posture. So, you can set up whitelists and blacklists based on your IPv4s, your IPv6, images.

Ed Young:
You can whitelist a complete image. So, an instance will be completely removed from any rule application. You can set up your protocol posture inside of those instances to be the whitelisted or blacklisted. So, based on our information and our security group risks that were security group violations and risks, you can whitelist or blacklist depending on how you want to move forward inside of your environment. So, if you don’t want to be alerted that a specific instance or set of instances violates a rule, you just, you whitelist it here, and you’re good to go.

Reggie Best:
Okay. Thanks.

Ed Young:
That’s it.

Reggie Best:
So, thanks Ed. I’m going to go ahead and start asking some of the questions that have come in from the audience in the time that we’ve got left. And there’s still opportunity for folks in the audience who have questions for them to send them in and I’ll get them queued up here. So, the first question that came in is, “I saw on the dashboard that there is a kind of in and outbound path information. Can I use that to tell how my enterprise network may be connecting to a particular VPC?”

Ed Young:
Sure. So, that was part of the inbound, outbound paths where we were able to show you the public IP address that’s associated with an instance ID and based on our connectivity for our hybrid environment, where we can identify the on-prem edge devices that have availability to that network. We can make the correlation between the communication paths of your on-prem network and your cloud environment based on the communication paths between those two IP addresses and those device files.

Reggie Best:
Okay. Second question that came in from the audience is, “Do I need to deploy a cloud scout in every region of my, in this case, AWS infrastructure in order to have it work with Lumeta CloudVisibility?” How many cloud scouts do I need to deploy effectively is the question?

Ed Young:
Sure. That’s a good question. So, as I was going through the mapping capabilities and talking earlier, yes and no. So, you can do as many or as little, right? So, you can deploy it in a single region providing that this communication paths between the regions and you have the proper credentials to speak, then you need a single instance. But the example I gave earlier, where if you had a segmented by a region or security group that you wanted to have a more aggressive polling interval, for example, you can deploy multiple cloud Scouts and set them up for as vigorous as a polling cycle, as you want and one that you wanted to have on a daily cycle or something like that. It’s a flexible deployment model where you can deploy a single cloud scout, where you could deploy multiple cloud scouts.

Reggie Best:
Okay, great. The next question that came in Ed is, “What specific API services does Lumeta CloudVisibility require access to?” And so, the answer to that is, there are three APIs that we leverage today. One is the AWS Configuration API, then there’s the AWS CloudTrail API. And then if you’re leveraging Amazon Inspector, then there’s an AWS Inspector API. Couple more questions. One here is a person wants to know what is the instance configuration needed for the cloud scout AMI to support evaluation that has about a hundred EC2 instances in it? So, I think the answer, the minimum configuration, which is also a configuration that you would be able to support with our Community Edition would be four CPU cores, 16 gigabytes of RAM, and about a hundred gigabytes of disc. And that would support an infrastructure, cloud infrastructure of about a hundred instances where we were providing the datasets that Ed had reviewed in the demo.

Ed Young:
Correct.

Reggie Best:
And then, the last question that I see here is, “What is the approximate cost of a deployment if I go beyond the capabilities of the free Community Edition?” And it says, “What would it cost, for example, if I were managing environment with about 2,500 instances?” So, the all-in cost, this is… Lumeta CloudVisibility is available in a subscription model. And for an organization that was fairly large and they had 2,500 instances, we’re probably talking around $5,000 or so per month of subscription to actually provide cloud visibility for all of those instances within an environment. I don’t see any other questions that have come in.

Reggie Best:
So, I’ll go ahead and this is Reggie Best. I’ll summarize, first of all, thank everyone for joining this webinar presentation on FireMon Lumeta CloudVisibility. We hope that you’ll take advantage of some of the links that are available that get you access to the additional information, plus the link on the Community Edition for download available free of charge. And there’s some other collaterals that will be available once you sign up for it, for that as well. And we hope that you will take a look at how Lumeta CloudVisibility can help you gain situational awareness of your hybrid enterprise environments. So, thanks very much for joining today, and we’ll look forward to seeing you at www.firemon.com/community.

Read more

Get 90% Better. See How to Get:

  • 90% EFFICIENCY GAIN by automating firewall support operations
  • 90%+ FASTER time to globally block malicious actors to a new line
  • 90% REDUCTION in FTE hours to implement firewalls

SCHEDULE A DEMO