Keine Bearbeitungszusammenfassung |
USP-2.7>Marcels Keine Bearbeitungszusammenfassung |
||
| Zeile 24: | Zeile 24: | ||
| '''Ab Version 1.24''' sind USP-Administratoren verpflichtet, die '''Zwei-Faktor-Authentifizierung''' als zusätzliche Sicherheitsmaßnahme zu verwenden. Sie sollten die Zwei-Faktor-Authentifizierung in Ihrem Benutzerkonto vor der Veröffentlichung der Version 1.24 aktivieren, andernfalls ist der Login in das USP bis zur Aktivierung der Zwei-Faktor-Authentifizierung gesperrt. Ab Version 1.24 ist die Aktivierung auch über die Login-Maske möglich.<br> Die Zwei-Faktoren-Authentifizierung muss bis dahin aktiviert werden.<br>Weitere Informationen sind in den Wiki-Artikeln [[MS/Voraussetzungen | Voraussetzungen]] und [[MS/Login-Endkunden | Login für Endkunden]] zu finden. | | '''Ab Version 1.24''' sind USP-Administratoren verpflichtet, die '''Zwei-Faktor-Authentifizierung''' als zusätzliche Sicherheitsmaßnahme zu verwenden. Sie sollten die Zwei-Faktor-Authentifizierung in Ihrem Benutzerkonto vor der Veröffentlichung der Version 1.24 aktivieren, andernfalls ist der Login in das USP bis zur Aktivierung der Zwei-Faktor-Authentifizierung gesperrt. Ab Version 1.24 ist die Aktivierung auch über die Login-Maske möglich.<br> Die Zwei-Faktoren-Authentifizierung muss bis dahin aktiviert werden.<br>Weitere Informationen sind in den Wiki-Artikeln [[MS/Voraussetzungen | Voraussetzungen]] und [[MS/Login-Endkunden | Login für Endkunden]] zu finden. | ||
| '''As of version 1.24''', USP administrators are required to use '''two-factor authentication''' as an additional security measure. You should activate two-factor authentication in your user account before the release of version 1.24, otherwise the login to the USP will be blocked until two-factor authentication is activated. From version 1.24, activation is also possible via the login screen.<br>Two-factor authentication must be activated by then.<br>Further information can be found in the wiki articles [{{#var:host}}MS/Voraussetzungen Requirements] and [{{#var:host}}MS/Login-Endkunden Login for end customers]. }} | | '''As of version 1.24''', USP administrators are required to use '''two-factor authentication''' as an additional security measure. You should activate two-factor authentication in your user account before the release of version 1.24, otherwise the login to the USP will be blocked until two-factor authentication is activated. From version 1.24, activation is also possible via the login screen.<br>Two-factor authentication must be activated by then.<br>Further information can be found in the wiki articles [{{#var:host}}MS/Voraussetzungen Requirements] and [{{#var:host}}MS/Login-Endkunden Login for end customers]. }} | ||
{{var | Build 2.7--desc | |||
| ;Features: | |||
:MDM | |||
* In der Benutzerverwaltung lässt sich ein [[MS/deployment/user| Zertifikat einem Benutzer zuweisen]] und dann über Variablen in den iOS-Profilen referenzieren | |||
* In den Android Gerätedetails gibt es einen [[MDM/Geraete|“Protokoll” Reiter]], in dem Aktionen dokumentiert werden und auch widerrufen werden können, solange sie noch nicht ausgeführt wurden | |||
:USC | |||
* [[USC/UTM#Operationen|Update-Aktionen sind für UTMs ab Version 14.1.0 PIN-geschützt]] | |||
* Zeitgesteuerte Update Aktionen bei den Windows VPN-Clients werden im Operationen Log angezeigt | |||
* [[USC/Profile|UTM-Profile können kopiert werden - für Reseller auch tenant-übergreifend]] | |||
* [[USC/Dashboard-Windows-VPN|Für Windows VPN-Clients gibt es jetzt ein Dashboard]] | |||
{{a|5}} | |||
;Changed: | |||
:USP | |||
* Eine Lizenz kann jetzt mehreren Geräten zugewiesen werden, ohne jedes Gerät einzeln bestätigen zu müssen | |||
:MDM | |||
* [[MS/deployment/generierte-Profile|Beim Löschen einer Android Vorlage wird jetzt ein Hinweis zu den Auswirkungen angezeigt]] | |||
* Im iOS Home-Bildschirmlayout kann eine App nur entweder der Schnellstartleiste (Dock) oder dem Home-Bildschirm hinzugefügt werden | |||
:USC | |||
* [[USC/UTM|Die Attribute in der Kachelansicht der UTMs wurden reduziert für eine bessere Übersichtlichkeit]] | |||
{{a|5}} | |||
;Bugfixes: | |||
:MDM | |||
* Schnellere Ladezeit bei der Android Geräte-Übersicht | |||
* Bearbeiten von bereits ins Profil eingefügten Android Apps ist wieder möglich | |||
* Bei der Neuanlage eines neues iOS Profils gibt es keine Verzögerung mehr bei der Eingabe des Namens | |||
:USC | |||
* In dem UTM-Profilen können jetzt auch IPv6 Adressen mit CIDR für den administrativen Zugriff hinterlegt werden | |||
| ;Features: | |||
:MDM | |||
* In user management, a [{{#var:host}}MS/deployment/user certificate can be assigned to a user] and then referenced via variables in the iOS profiles | |||
* In the Android device details there is a [{{#var:host}}MDM/Devices "Log" tab], in which actions are documented and can also be revoked as long as they have not yet been executed | |||
:USC | |||
* [{{#var:host}}USC/UTM#Operations Update actions are PIN-protected] for UTMs from version 14.1.0 | |||
* Time-controlled update actions for the Windows VPN clients are displayed in the operations log | |||
* [{{#var:host}}USC/Profile UTM profiles can be copied] - for resellers also across tenants | |||
* [{{#var:host}}USC/Dashboard-Windows-VPN There is now a dashboard for Windows VPN clients] | |||
{{a|5}} | |||
;Changed: | |||
:USP | |||
* A licence can now be assigned to multiple devices without having to confirm each device individually | |||
:MDM | |||
* [{{#var:host}}MS/deployment/generierte-Profile When deleting an Android template, a note on the effects is now displayed] | |||
* In the iOS home screen layout, an app can only be added to either the quick launch bar (dock) or the home screen | |||
:USC | |||
* [{{#var:host}}USC/UTM The attributes in the tile view of the UTMs have been reduced for a better overview] | |||
{{a|5}} | |||
;Bugfixes: | |||
:MDM | |||
* Faster loading time for the Android device overview | |||
* Editing of Android apps already added to the profile is possible again | |||
* When creating a new iOS profile, there is no longer a delay when entering the name | |||
:USC | |||
* IPv6 addresses with CIDR can now also be stored in the UTM profiles for administrative access }} | |||
{{var | Build 2.6--desc | {{var | Build 2.6--desc | ||
| ;Features: | | ;Features: | ||
| Zeile 62: | Zeile 123: | ||
:Cloud Shield | :Cloud Shield | ||
* Profile können wieder kopiert werden | * Profile können wieder kopiert werden | ||
| | | Features: | ||
:MDM | |||
* [{{#var:host}}MS/deployment/profile/reiter-einschraenkungen Apple Intelligence can be activated/deactivated via the iOS profiles for end devices with iOS version 18.4 or higher] | |||
:USC | |||
* [{{#var:host}}USC/UTM#Detailed_authorizations As of UTM version 14.1.0, authorizations for actions (e.g. open web session, perform PIN-protected actions, perform update or cloud scan) from the USP can be prohibited on the UTM. Tabs and buttons in the UTM details are then deactivated and provided with an explanatory tooltip.] | |||
* [{{#var:host}}USC/VPN/Core-Satellite-UTMs-austauschen The core or satellite UTM can now be replaced in the VPN configuration (ASC)] | |||
:Cloud Shield | |||
* [{{#var:host}}Cloud_Shield New tab in the Cloud Shield profiles to use AI-driven detection of suspicious domains] | |||
* [{{#var:host}}Cloud_Shield Advanced DNS rebinding protection can be used in the profiles to block internal IPv6 addresses reserved for special network purposes such as documentation, tunneling or packet discarding] | |||
{{a|5}} | |||
;Changed: | |||
:USP | |||
* [{{#var:host}}MS/Datenschutz If pseudonymization is deactivated for portal statistics and USR, a justification must be provided, which is also stored in the audit log for traceability] | |||
:MDM | |||
* [{{#var:host}}MDM/Gereate The maximum length of device names has been extended to 120 characters] | |||
:USC | |||
* [{{#var:host}}USC/Profile Configured components are displayed in the tile view of the UTM profiles] | |||
{{a|5}} | |||
;Bugfixes: | |||
:USP | |||
* The import of multiple groups from different Entra ID tenants works again | |||
:MDM | |||
* Resetting passwords for Exchange accounts on managed iOS devices has been fixed | |||
* Selection of tags on iOS devices works reliably again | |||
* The name for web clips is displayed correctly in the preview | |||
:USC | |||
* A web session can be started again via the cross-tenant USC dashboard | |||
:Cloud Shield | |||
* Profiles can be copied again }} | |||
{{var | Build 2.5--desc | {{var | Build 2.5--desc | ||
| ;Features: | | ;Features: | ||
| Zeile 110: | Zeile 207: | ||
:Cloud Shield | :Cloud Shield | ||
* Logs werden wieder korrekt angezeigt | * Logs werden wieder korrekt angezeigt | ||
| }} | | ;Features: | ||
:USC | |||
* [{{#var:host}}USC/VPN/Windows-Profile For Windows VPN clients from version 3.1.0 that are integrated in a VPN configuration, the setting of a PIN can be enforced via the ‘’'VPN configuration'‘’ tab in the Windows profile] | |||
* [{{#var:host}}USC/VPN/Windows-Clients It is now possible to reset the PIN of a connection for Windows VPN clients] | |||
* As of UTM version 14.1.0, authorizations for actions via the USC can be assigned individually on the UTM. If an authorization is not available, an error message is displayed in the USC | |||
:MDM | |||
* There is now a log entry for setting the automatic reset of an Android device | |||
* If a password is selected for Android devices under “Reset password” that does not correspond to the set password guidelines, a tenant notification is generated | |||
<!--* [[MS/deployment/user|A certificate can be assigned to a user in the iOS user management and then referenced via variables in the iOS profiles]]--> | |||
* [{{#var:host}}MS/DEP-Profile DEP profiles without a PIN are marked with a label in the overview] | |||
* [{{#var:host}}MS/DEP-Profile In the DEP profiles] and [{{#var:host}}MDM/Geraete of the iOS device overview], a note is displayed if there are profiles without a PIN due to future changes in iOS enrollment {{info|From portal version 2.8}} | |||
:Cloud Shield | |||
* [{{#var:host}}Cloud_Shield External blocklists can be added] | |||
* [{{#var:host}}Cloud_Shield#Einstellungen Logs can be deleted] | |||
* IP subnets can now also be included in the allow list and the block list | |||
* [{{#var:host}}Cloud_Shield#Domain_überprüfen Domains can now be checked to see if they are allowed or blocked] | |||
{{a|5}} | |||
;Changed: | |||
:USC | |||
* An error message has been integrated if the core UTM cannot be deleted from the VPN configuration | |||
* Renaming “Upgrades” to “Firmware” for UTM operations | |||
* [{{#var:host}}USC/Api-Keys The API key list is now sorted alphabetically and there is a sort function] | |||
MDM | |||
* [{{#var:host}}MDM/Geraete Under “Applications” the app data can be deleted for individual apps on Android devices] | |||
* When enrolling a new Android device, the Zero-Touch DPC extras can now be copied so that they can be easily pasted into the Google Zero-Touch portal | |||
* [{{#var:host}}MS/deployment/profile/android Android profiles that have at least one assigned device can no longer be deleted] | |||
* [{{#var:host}}MS/deployment/profile/android Regrouping of attributes and adjustment of info texts in the Android profile for status message, networks, personal use] | |||
* Clear error message when uploading an invalid certificate for the DEP token | |||
* [{{#var:host}}MS/Einstellungen#Apple_DEP If no DEP PIN has been configured in the settings, this is now automatically generated when a new DEP profile is created and used for this and all future profiles] | |||
* [{{#var:host}}MS/deployment/profile/Status For new iOS profiles, all sliders of the declarative management are activated by default] | |||
Cloud Shield | |||
* [{{#var:host}}Cloud_Shield/Profile The profile type “MDM” has been renamed to “Managed Devices”] | |||
* [{{#var:host}}Cloud_Shield The content filter category is displayed in the logs for blocked websites] | |||
{{a|5}} | |||
;Bugfixes: | |||
:USP | |||
* Login works reliably again for the RSP role “Technology Reseller” | |||
* When importing Entra users, the name of the local group can be edited again | |||
:MDM | |||
* Faster loading time of the iOS device overview | |||
* All apps are reliably displayed again in the iOS home screen layout | |||
* When creating generated profiles for Android devices that were previously assigned to a different profile, the name of the previous profile is displayed correctly in the audit log | |||
:USR | |||
* If a recipient email address is stored in the UTM, the USR is also reliably sent to this address | |||
:Cloud Shield | |||
* Logs are displayed correctly again }} | |||
{{var | Build 2.4--desc | {{var | Build 2.4--desc | ||
| ;Feature: | | ;Feature: | ||
MS/Changelog Portal.lang: Unterschied zwischen den Versionen
Aus Securepoint Wiki