Citrix deployments – needless to say but let me say it nevertheless – are complicated. There are too many moving parts, various dependencies, and myriad configurations and customizations. Ultimately, organizations expect seamless connectivity and access to virtualized applications and desktops for their employees and partners whenever and wherever.
According to Best Practices for Managing AWS Access Keys, if you must utilize IAM access keys, it is best to remove or disable unused keys. This will close possible security holes in your AWS account. Today, we’re happy to announce a new action to help with this task: Disable Unused IAM Access Keys. This new action will iterate through the IAM users in your AWS account, determine when any access keys were last used, and if they were not used inside a configurable threshold, disable the keys.
Troubleshooting Citrix XenApp and XenDesktop logon duration is challenging because it’s a complex process, it’s asynchronous, meaning multiple things are happening simultaneously, and it’s also variable. Some logons will have 33 sub-steps in the process, and others will have more than 50. Any technology that doesn’t offer visibility into all the sub stages can only show that there is a general problem and not the true root cause of the issue.
In our last blog post, we learned what the Distributed Denial of Service (DDoS) attack is, and examined the DDoS picture globally. As we walked through some recent and well-known cases, we also surveyed a range of attack types and drilled down to specific examples. In this article, we’ll study the mitigation techniques you’ll need to resist these attacks. You’ll learn: 1. How to avoid becoming a bot; 2. How to prepare your own network for the possibility of an attack and finally; 3.
The term Data Center Monitoring is used in the communications plan of some companies as if it were a product specially designed for this area. However, when it comes to these ideas we believe that they actually refer to a summary of monitoring tools facilities that are intended to support the work of Data Centre managers.
You’ve just recovered from a critical application outage and your team is being asked to report on root cause and recommended remediation steps later this afternoon. Can you quickly analyze all the data, identify all the leading events, and discern which one was responsible for the cascading failure?
We’re excited to announce the general availability of our new On-Prem, Self-Hosted, and Multi-Cloud logging platforms. Our customers will have the capability to log data in their infrastructure of choice. Whether across multiple public/private clouds or within a customer’s own data center, logs can be viewed through a unified interface while addressing any data locality and performance requirements.
By now you’ve learned about reducing the sheer amount of alerts you’re getting as well as automated triage and remediation. In this post, I’ll go into some extra steps you can take to further fine tune Sensu and cut down on alert fatigue.
We are very excited to announce a new capability for our Amazon S3 sources. Until recently, the only method Sumo Logic used for discovering new data in an S3 bucket was periodic polling. However, with our new notification-based approach, users can now configure S3 sources such that Sumo Logic is notified immediately (via AWS SNS) whenever a new item is added to an S3 bucket, eliminating the need to wait for new objects to be discovered via periodic polling.
