Day 6: Security

30 Days of FrameFlow

Time to Read: 5 Minutes

Security

In the next few days, we're going to dive into more advanced IT monitoring. First, though, we need to establish security. Up until now, we've been running on a built-in webserver, which is designed to help you set up FrameFlow but doesn't offer the high security needed for monitoring beyond demo purposes. Switching to IIS provides encryption and other security-related options. To learn how to do so, read our tech resources article on running FrameFlow on IIS. Setup only takes ten minutes.

Once you're running on IIS, the next move is to enable login security. To do so, navigate to the Settings section with the menu on the left. From there, choose "Login and Security Settings" and check the box labeled "Login Required". Before you save your changes, you must add your first user using the menu shown at the end of the gif below.

In the login user details section, fill in the information for your first user. Once you fill in the details for your first user and hit "OK", you'll be automatically logged out of FrameFlow. Simply sign back in with the credentials you just created.

Summary

The first login user you create must have admin rights. Not every user needs admin rights, though. To ensure maximum security, give the additional users you create the minimum necessary clearances. Tomorrow, we'll dive into one of the most essential event monitors we offer: the System Health Event Monitor. Stay tuned!

Day 5: Authentication

Day 7: System Health Monitoring