LUCY offers a role-based access control (RBAC), restricting system access to authorized users. The permissions to perform certain operations are assigned to specific roles within the user settings. Members or staff (or other system users) are assigned particular roles, and through that role, assignments acquire the computer permissions to perform particular LUCY functions.
No. You have the ability to create as many LUCY users that can access the web console as you want.
This user role created by the admin user can be given individual rights for each LUCY feature. The user can later be added to a specific campaign and bound to a client.
Maintain the overview with access to the campaign specifications. Communicate directly with the campaign creator (user) to suggest changes and give approval to green light the campaign. The supervisor is in the hierarchy above the user. Therefore it is not possible to supervise a system admin. The Supervisor is technically the same as the user account, but you may assign users to the supervisor account and approve/reject their campaigns. Within the settings you can select which users you want to supervise:
You have the ability to define a supervisor who is able to START/STOP the campaign which was created by a user. To do so add a user to a campaign with all permissions selected, add his supervisor to the same campaign with "Campaign start/stop" permission selected. As a result, the supervisor will only be able to go into the campaign and approve or reject the start.
The LUCY admin can save all settings within LUCY and run the campaign. This is the user that you need to perform your awareness campaigns. You cannot segregate administrators in a way, that an admin A doesn't see the clients from an admin B. This can only be done in the LUCY SaaS edition.
The View Only User can only see certain statistics of the campaign. This user cannot start/stop a campaign. The user also has no rights in viewing or changing any of the campaign settings. First, you need to create a client name. The client name is always associated with a campaign. Then you can associate that user with the client. As a result, the View Only User will only see all the campaigns which belong to that specific client.
Please make sure you also add the view only user to the specific campaign:
|Access All Campaigns||Right to access campaigns. If you activate this checkbox, the user can access all campaigns, regardless of who created them.|
|Create/Delete Campaigns||Right to Create or Delete campaigns. The user can create and delete campaigns and later access only the campaigns he created himself. Campaigns of other users are not displayed.|
|Save Campaign As Template||Right to save a campaign as a template. A campaign template can be used in the setup process when generating new campaigns.|
|Attack Templates||Access to the list of Attack Templates. Attack templates are predefined emails or websites which can be used for phishing simulations.|
|Campaign Templates||Access to the list of Campaign templates|
|Awareness Templates||Access to the list of Awareness Templates. Awareness templates are used in training campaigns.|
|File Templates||Access to the list of File Templates. File Templates are used for file based attacks.|
|Not Found Template||Access to the LUCY 404 page|
|Report Templates||Access to the Report Templates|
|Download Templates||Access to the menu of Templates Downloading|
|Clients||Access to the Clients menu|
|Recipients||Access to the list of Recipients. Recipients are the users that get attacked or trained.|
|End Users||Access to the list of End Users|
|User Management||Access to the User Management|
|Reputation Levels||Access to the Reputation Levels|
|SSH Access||Access to the SSH Access menu|
|SSH Password||Right to reset SSH Password|
|Benchmark Sectors||Access to the Benchmark Sectors|
|License||Right to access License menu|
|Update||Right to Update LUCY|
|Reboot||Right to Reboot LUCY|
|Domains||Right to access Domains menu|
|Register Domains||Right to register a domain|
|Dynamic DNS||Access to Dynamic DNS feature.|
|Automated Response Detection||Access to the Automated Responce Detection menu|
|Advanced Settings||Access to the Advanced Settings|
|Performance Test||Access to the Performance Tests|
|Test email||Right to send a test email|
|Spam Test||Access to the Spam Test|
|System Monitoring||Access to the System Monitoring|
|System Status Page||Access to the System Status Page. The status page gives a user access to certain logs|
|Incident Management||Access to the Incident Management|
|Plugin configuration||Right to configure Outlook plugin|
|Incident Management Configuration||Right to configure Incident Management|
|Manual||Access to LUCY manual. This is the WIKI page hosted on th LUCY server|
|Exports||Access to the exports|
|Invoices||Access to the Invoices. Invoices can be created inside LUCY as a receipt for purchases like domains, sms credits etc.|
|Send Logs||Access to "Send Logs" menu.|
|Service Logs||Access to the Service logs|
|Changelog||Access to the Changelog|
|Mail Manager||Access to the Mail Manager|
Lucy has the ability to convert the account to LDAP-based, so existing user can be logged in through LDAP. You can convert multiple accounts at once by selecting the necessary users and clicking the button "Convert to LDAP-based":
Note: Lucy admin should configure the connection to Active Directory service to be able to use this feature. Please find more information about LDAP Integration here.
Yes. It is possible to adjust password policy in the advanced settings. Please find more here.
Yes. It is possible using the AD Federation service and authenticate the users automatically. See chapter SSO.
To set up a multitenant capable administration, you first need an administrator account. From there you can set up the appropriate users and rights. Here are two use cases and the corresponding configuration:
Use case 1: You create a campaign for your customer, but want to give your customer access to the statistics within the campaign. It must be ensured that the customer only sees his own data and cannot intervene in the campaign configuration.
Solution use case 1: You create a view-only account (1) in "settings/users" and assign this account to your customer. As soon as you create a campaign, you will be asked to enter the customer of the campaign (2). The customer can be yourself, an organizational unit or a third party. Next, you should add the user to the campaign (3). You can then assign the rights to view the statistics to the user (4).
Use case 2: You have a customer who wants to create their own campaigns. However, the customer should only have access to his statistics and not see other customers.
Solution use case 2: You create an account with the status "user" in "settings/users". Give the user only the right "Create/delete campaign" (1). As soon as the customer logs in, he can then create his campaign and see only the data of the campaigns he created himself (regardless of the assignment of the customer). He wont have acccess to any other menu item (2). However, there are areas where this limited administrator has access to possibly sensitive data of other customers. Examples are custom created templates that may contain customer-related information. But also all recipient groups created on the system can be seen by this customer when assigning recipients.