If your business needs to comply with Sarbanes-Oxley, HIPAA, PCI, or other government or industry rules and regulations, discover how Automate Schedule can simplify your life. It logs database changes, when they were made, the fields changed, and who made the change. And, its reporting options provide the information your auditors need.
This 15-minute recorded demo can help you save hours when you're preparing for an audit.
Hello and welcome to today's Skybot Scheduler tip clip. Today's quick webinar is on Skybot Scheduler and how it can help you meet some of your auditing needs. My name is Pat Cameron and I will be your presenter today. So if you have any industry or government regulations that you need to comply with in your IT department, Skybot can help you meet them easily and automatically. Let's take a look at how.
First of all, I'd like to do a kind of quick overview of Skybot's architecture. Skybot Scheduler is installed on an enterprise server and that can be either an AIX, Windows, or Linux server, and we install a database and then an HTTP server so that you can access Skybot using your browser. Once your enterprise server is installed, you'll install an agent on each of the servers you want to monitor and schedule in your network. This communication allows all of the servers to communicate with one another and the enterprise server knows the status of all the jobs on your server. So it is really easy to set up dependent jobs on one server that will trigger a job on another. The schedule for all the agents is located on the central database server so you can maintain, monitor, and view the schedule for all the agents from one display.
Let's talk a little bit about security and auditing. Skybot offers role-based security. It is really easy to set up roles for the different job functions with your business and then add users to those roles. You can be very specific in the agents that someone can access, for instance, or maybe only certain jobs people can access. You can also set up change authority for certain jobs, execute for others, view, and exclude. Again, lots of flexibility in how you can set up that security and it can be based on different roles within your department or divisions. We need to support any of the requirements that you have for security.
Then auditing: we log every change to our database. Every time a job runs, we will log that. Every time a job is changed, we log the record that was changed and the fields that were changed within that job. Then you can report on that information as well. So we are going to keep track of every change made to any of the objects within our database.
We've also included reporting with Skybot Scheduler so you can run an audit history report so when those auditors come, it's not going to take you days and days to pull that information together. You will already have it on Skybot and you can run some reports. So audit history reports, job history, if the job failed, or whether it completes successfully and then agent events history. Agent events are those events such as a new file arriving, a directory changing, a process starting or ending that we can track in Skybot Scheduler.
I'm going to go ahead and go online and show you a couple of things with Skybot. We are going to create a new role on one of our little test servers. We are going to create a help desk role. We are going to add a user to that role and I will show you how we can restrict what that user can do. Let's take a look at the audit history report and then we will run a report. So I am going to bring up Skybot; this is the dashboard and this is my initial view that I've got set up for Skybot and it shows me how my job automation is going. One thing I did want to show you on this screen here is that we also track in our dashboard the number of object changes that have occurred in the last seven days. So, once you get Skybot up and running, there should not be a lot of changes so you can kind of use this as a quick view to see what type of objects are being changed and you can drill into the details to take a look at who is making those changes when and what exactly did they change.
So I am going to go into our administration menu and I am going to take a look at the roles that we have got set up on our Skybot server. On our Skybot server, we've got a number of different roles set up. When we ship Skybot, we ship an administratorîof course an administrator can do it allîan operator and a user type of a role. Now we've added some other types as we are doing our testing and demos for customers. What I am going to do is create a role for the help desk for our session today and I am going to do that by copying one of the roles that I have already got out there. So I am going ot go ahead and copy this user role.
We try to make maintenance and changes as easy as possible in Skybot. So we've got a lot of copy options throughout the products. So this is going to be my little help desk role and I will change this description and I am going to add a user that I have all set up out there and this is my help desk status. So I could add multiple users certainly for this role. Now the way this role is set up, you can see the help desk can't change a lot of options within Skybot, but they have view access. So they can take a look at the different options, the schedules, etc., but they can't make any changes. Here they are excluded from our cron imports center, they are excluded from changing any systems setting, and they are excluded from security, users, and roles.
If we look at the secured actions and the areas where you can create new objects, they have user authority to all of the reports that we've got within Skybot, but they are excluded from creating new objects and new environments. What I am going to allow them to do is I am going to let them use our lock or unlock job queues so they can kind of manage the system if one of the job queues gets all backed up, they are going to have the ability to unlock it or if we want to stop everything, we will let them go ahead and lock those queues. I will let them create forecast models so if they want a schedule to run maybe over the next three, five, or seven days, we will let them do that. And I will also let them create job flow diagrams. Again, if they are doing some troubleshooting, they might want to see some of the jobs that are dependent on other jobs or other events so we will let them create some diagrams for that.
Down within the secured areas, you can see that they have got view access again to most of the objects that are down there. For jobs, we are going to let them execute jobs. They can't make any changes to the jobs. They can't change the schedule, but if someone needs a job run out of its normal schedule, we are goign to let the help desk do that. So I am going to go ahead and save this and now I've got my help desk user out there and I've got my help desk user enrolled in that role. So I am going ot create a job for the help desk to manage and I've got a credit card job out there and what I am goign to do again, I am going to copy that job and I am going to change the name so that it's just for our audit webinar and I am going to chagne the time on this guy from running every day at 6 to running every day at 8. Go ahead and make that change. So what I've done is I've created a new job an dI've also changed the time on that new job. I'm going to go ahead and save that.
So now what I am going ot do is I am going to log out and I am logged in as myself and I am going to log in as the help desk user. This is the initial screen for a new user. We've got some getting started information up here. With the status of the system, you can hide this screen and you can bring up the dashboard from here as well. So a couple of things from the first time that you sign on you can do.
So what I am going to do now is I am going to go over to the job that we created and here is my audit job and I've got our job schedule filtered using one of my tags. So I am going to go ahead and try to edit this job. I see that when I open this up that it is set to view only. So when I am logged in as the help desk, I can only see what the schedule is. This job runs every day at 8. I can view the command that it is running. So again, I've got view-only access to this job, so I cannot make any changes to it. But what I can do is I can go ahead and run it. So by doing that, I just right click the job and go ahead and say run that job now and I will go ahead and let that job run.
The other thing that I am going to do so that I have some history to show you is now I am going to cancel it so I can look at the history. We can see now that the job is running on one of my servers. Now I am going to go ahead and cancel this job so I can end it and I can give it a completion code of completed, canceled, or failed. And I am going to go ahead and fail this job. So now I have logged in as the help desk and, again, as you can see, I've got limited access to the jobs that are on my system so I can open them up and view them.
Also, for my scheduling options, I can look at our agent environments that we've got out there and if I open my Skybot user again, I've got view-only access to those options so I can't make any changes. But, again, troubleshooting you are going to want to be able to take a look at those different objects.
So if I go to server history, it is going to show you things that we track here within Skybot. Here's my audit webinar job that I have created, and we can see here that this was submitted to this agent by user help desk staff, and this was the run number. So we are going to track that it was submitted by this user at that time and we are also going to track that this help desk staff went ahead and canceled that job on this date and time. So we are going to keep good track of who is running jobs on my system.
The other thing that we are going to track within our audit history is who is creating and changing objects. We can see here that I created a new job, and if I look at the detail of that, this is the date and time. This is the new job that I created, my audit webinar job, and these are all of the options that the job had. Again, they were pulled from the job that I copied. This is the user that I changed. I added them to the help desk role. Here is the update. Originally, the help desk staff was a user and now it's the help desk. So, again, you can see every change that is made to our database, every job that is run, the date and time and whether it ends normally or not.
The last thing I want to show you is our audit history report. I am going to run this report for today. Any of the reports that we have within Skybot are created as PDFs. We will go ahead and submit that job and it will take just a second for it to pull that information together. If you click on this refresh key, it makes it go a lot faster. So here is my audit history report, and I will go ahead and open that up. That is going to show us from midnight this morning to now, 10:30. These are the changes that have occurred. Here's my job that was created and the type of record that it was and who did it and all of the details behind that record. Again, here is the command that was created. Here is my help desk user, my help desk staff. Originally, it was a user changed from the value of user to the new value of help desk.
So, that is some of the security that is built in to Skybot and the roles that you can create and the auditing. Auditors are going to love it. Thank you for joining us today. Hope to see you again.
Still have questions? We can help. Submit a case to Technical Support.