SOPHOS ENDPOINT SECURITY - Endpoint Security

ENDPOINT SECURITY - Endpoint Security SOPHOS - Free user manual and instructions

Find the device manual for free ENDPOINT SECURITY SOPHOS in PDF.

📄 54 pages English EN Download 💬 AI Question 10 questions ⚙️ Specs
Notice SOPHOS ENDPOINT SECURITY - page 49
View the manual : Français FR English EN
Pick your language and provide your email: we'll send you a specifically translated version.
Product Type Endpoint Security Suite (software)
Main Functions Antivirus, personal firewall, device control, data control, NAC agent, centralized update
Manual Version Advanced Upgrade Guide, September 2009
Administered Components Enterprise Console 4.0, NAC Manager 3.3, Sophos Endpoint Security and Control 9.0
Minimum System Requirements (console) Windows 2000 SP4 or higher, .NET Framework 2.0 SP1, MSI 3.1, SQL Server 2005 Express Edition
Update Method Sophos Update Manager (download from Sophos or network shares)
Key New Features Delegated administration, data control, device control, temporary NAC agent, encryption assessment
Backup required before upgrade NAC databases (ReportStore, PolicyStore) and Enterprise Console database (SOPHOS3)
Upgrade Order NAC Manager first, then Enterprise Console, then migration to Update Manager, then workstation upgrade
Workstation Compatibility Windows 2000 SP4 and higher, Mac OS X (limited administration), NetWare (automatic update)
Maintenance and Cleaning Not applicable (software); keep automatic updates active
Security Antivirus and firewall protection, removable device control, data leak prevention
Spare parts and repairability Not applicable; technical support via Sophos (website and knowledge base)
General Information Publisher: Sophos Group. Documentation available in French. License required.

Frequently Asked Questions - ENDPOINT SECURITY SOPHOS

What is the difference between Sophos Anti-Virus and Sophos Endpoint Security and Control?
Sophos Endpoint Security and Control 9.0 replaces Sophos Anti-Virus and Sophos Client Firewall. It adds data control and device control functions.
Do I need to upgrade NAC Manager before Enterprise Console?
Yes, it is mandatory. Upgrading Enterprise Console first would place the NAC Manager in an unsupported state.
How to backup the databases before the upgrade?
You must backup the NAC databases (ReportStore and PolicyStore) via SQL Server Management Console, and the Enterprise Console database using the BackupDB tool.
What to do if the migration to Sophos Update Manager fails?
Consult the migration report. If it fails, configure subscriptions, update sources manually, and create new update policies as described in section 13.3 of the manual.
Can I continue to use EM Library after the upgrade?
It is not recommended to run EM Library and Sophos Update Manager simultaneously due to increased network traffic. Uninstall EM Library once the migration is complete.
What are the prerequisites for installing Enterprise Console 4.0?
Windows Installer MSI 3.1, .NET Framework 2.0 SP1, and SQL Server 2005 Express Edition (installed automatically if needed). A reboot may be required.
How to upgrade software on workstations?
After migration to Update Manager, subscribe to version 9 of Sophos Endpoint Security and Control in the software subscription, then apply the new update policy to the computer group. The workstations will update automatically.
What to do if a workstation shows 'Differs from policy' after upgrade?
Right-click the computer in Enterprise Console and select Make Compliant With, then choose the appropriate policy.
How to transfer device control settings from the old policy?
Use the DeviceControlMigration.exe tool located in the Enterprise Console installation folder. It creates new device control policies based on the old ones.
Where can I find recommended and fixed software versions?
In the Subscription tab of the management console. Recommended, Previous and Legacy versions are available. Fixed versions are specific numbers like 9.4.3.

User questions about ENDPOINT SECURITY SOPHOS

0 question about this device. Answer the ones you know or ask your own.

Ask a new question about this device

The email remains private: it is only used to notify you if someone responds to your question.

No questions yet. Be the first to ask one.

Download the instructions for your Endpoint Security in PDF format for free! Find your manual ENDPOINT SECURITY - SOPHOS and take your electronic device back in hand. On this page are published all the documents necessary for the use of your device. ENDPOINT SECURITY by SOPHOS.

USER MANUAL ENDPOINT SECURITY SOPHOS

Sophos Endpoint Security and Control, version 9

Sophos Enterprise Console version 4.0

Sophos NAC version 3.3

Sophos Endpoint Security and Control version 9.0

natural_image Abstract blue graphic with stylized 3D letters (envelope, globe, document) and wave elements on a gradient background (no text or symbols)

Table des matières

Sophos Endpoint Security and Control 9.0

HKLM\SOFTWARE\Sophos\Certification Manager

Only the Sophos NAC Application Server can be installed. To install the Sophos NAC Application Server, click OK.

MaintMode.exe /stop.

15 Support technique

ACE ^1 , TAO ^2 , CIAO ^3 , and CoSMIC ^4 (henceforth referred to as “DOC software”) are copyrighted by Douglas C. Schmidt ^5 and his research group ^6 at Washington University ^7 , University of California ^8 , Irvine, and Vanderbilt University ^9 , Copyright © 1993–2005, all rights reserved.

Since DOC software is open-source ^10 , free software, you are free to use, modify, copy, and distribute—perpetually and irrevocably—the DOC software source code and object code produced from the source, as well as copy and distribute modified versions of this software. You must, however, include this copyright statement along with code built using DOC software.

You can use DOC software in commercial and/or binary software releases and are under no obligation to redistribute any of your source code that is built using DOC software. Note, however, that you may not do anything to the DOC software code, such as copyrighting it yourself or claiming authorship of the DOC software code, that will prevent DOC software from being distributed freely using an open-source development model. You needn't inform anyone that you're using DOC software in your software, though we encourage you to let us ^11 know so we can promote your project in the DOC software success stories ^12 .

DOC software is provided as is with no warranties of any kind, including the warranties of design, merchantability, and fitness for a particular purpose, noninfringement, or arising from a course of dealing, usage or trade practice. Moreover, DOC software is provided with no support and without any obligation on the part of Washington University, UC Irvine, Vanderbilt University, their employees, or students to assist in its use, correction, modification, or enhancement. A number of companies ^13 around the world provide commercial support for DOC software, however. DOC software is Y2K-compliant, as long as the underlying OS platform is Y2K-compliant.

Washington University, UC Irvine, Vanderbilt University, their employees, and students shall have no liability with respect to the infringement of copyrights, trade secrets or any patents by DOC software or any part thereof. Moreover, in no event will Washington University, UC Irvine, or Vanderbilt University, their employees, or students be liable for any lost revenue or profits or other special, indirect and consequential damages.

The ACE ^14 , TAO ^15 , CIAO ^16 , and CoSMIC ^17 web sites are maintained by the DOC Group ^18 at the Institute for Software Integrated Systems (ISIS) ^19 and the Center for Distributed Object Computing of Washington University, St. Louis ^20 for the development of open-source software as part of the open-source software community ^21 . By submitting comments, suggestions, code, code snippets, techniques (including that of usage), and algorithms, submitters acknowledge that they have the right to do so, that any such submissions are given freely and unreservedly, and that they waive any claims to copyright or ownership. In addition, submitters acknowledge that any such submission might become part of the copyright maintained on the overall body of code, which comprises the DOC software. By making a submission, submitter agree to these terms. Furthermore, submitters acknowledge that the incorporation or modification of such submissions is entirely at the discretion of the moderators of the open-source DOC software projects or their designees.

The names ACE, TAO, CIAO, CoSMIC, Washington University, UC Irvine, and Vanderbilt University, may not be used to endorse or promote products or services derived from this source without express written permission from Washington University, UC Irvine, or Vanderbilt University. Further, products or services derived from this source may not be called ACE, TAO, CIAO, or CoSMIC nor may the name Washington University, UC Irvine, or Vanderbilt University appear in their names, without express written permission from Washington University, UC Irvine, and Vanderbilt University.

If you have any suggestions, additions, comments, or questions, please let me ^22 know. Douglas C. Schmidt ^23

The ACE home page is http://www.cs.wustl.edu/ACE.html

References

  1. http://www.cs.wustl.edu/\~schmidt/ACE.html
  2. http://www.cs.wustl.edu/\~schmidt/TAO.html
  3. http://www.dre.vanderbilt.edu/CIAO/
  4. http://www.dre.vanderbilt.edu/cosmic/
  5. http://www.dre.vanderbilt.edu/\~schmidt/
  6. http://www.cs.wustl.edu/\~schmidt/ACE-members.html
  7. http://www.wustl.edu/
  8. http://www.uci.edu/
  9. http://www.vanderbilt.edu/
  10. ://www.the-it-resource.com/Open-Source/Licenses.html
  11. mailto:doc_group@cs.wustl.edu
  12. http://www.cs.wustl.edu/\~schmidt/ACE-users.html
  13. http://www.cs.wustl.edu/\~schmidt/commercial-support.html
  14. http://www.cs.wustl.edu/\~schmidt/ACE.html
  15. http://www.cs.wustl.edu/\~schmidt/TAO.html
  16. http://www.dre.vanderbilt.edu/CIAO/

  17. http://www.dre.vanderbilt.edu/cosmic/

  18. http://www.dre.vanderbilt.edu/
  19. http://www.isis.vanderbilt.edu/
  20. http://www.cs.wustl.edu/\~schmidt/doc-center.html
  21. http://www.opensource.org/
  22. mailto:d.schmidt@vanderbilt.edu
  23. http://www.dre.vanderbilt.edu/\~schmidt/

OpenSSL cryptographic toolkit

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts.

Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.

OpenSSL license

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  3. All advertising materials mentioning features or use of this software must display the following acknowledgment:
    “This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)”
  4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.
  5. Products derived from this software may not be called “OpenSSL” nor may “OpenSSL” appear in their names without prior written permission of the OpenSSL Project.
  6. Redistributions of any form whatsoever must retain the following acknowledgment:

“This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)”

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT “AS IS” AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING

NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay license

Copyright © 1995–1998 Eric Young (eay@cryptsoft.com) All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com). The implementation was written so as to conform with Netscape's SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

“This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)”

The word “cryptographic” can be left out if the routines from the library being used are not cryptographic related :-).

  1. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement:

“This product includes software written by Tim Hudson (tjh@cryptsoft.com)”

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The licence and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence [including the GNU Public Licence.]

Index

A

Sophos Update Manager

installation 25

migration vers 22

Manual assistant
Powered by Anthropic
Waiting for your message
Product information

Brand : SOPHOS

Model : ENDPOINT SECURITY

Category : Endpoint Security