Windows 7 Support Information on Symantec.com
We've had numerous questions regarding Windows 7 and which Symantec products will support the new OS and when. In effort not to duplicate information and keep updates as current as possible we are providing this link to the Symantec.com site: http://www.symantec.com/business/theme.jsp?themeid=windows7
When it comes to SECRETS, how secure is your application?
Introduction Enterprises running various heterogeneous workloads ranging from on prem applications to applications spread across various cloud service providers, often struggle to manage credentials securely. We’ve seen a lot of technical debates about how to find a perfect balance between security and flexibility, but there’s no de facto standard hack which fits in for all. We’ve seen (sometimes radically) different opinions on “the right way” to manage secrets: “You should always use vault”, “You should encrypt creds” and the list is never ending! To cope up with these challenges, Veritas introduces Alta Recovery Vault short lived token-based authentication. For us, your data’s security is paramount to us. Prior to short lived tokens, Veritas provided ability to connect to Alta Recovery Vault with Standard Credentials (access and secret keys) as shown below : Diagram1: Creating a Credential with the Storage Account and Traditional Credentials (Access key and secret) given by Veritas Disadvantages of using Standard Credentials in Recovery Vault These standard credentials are long lived in nature. If compromised, they give attackers ample time to exploit the application. If they are stolen it would be a nightmare to discern which operations are legitimate. Thus, the only fail-safe choice is to cumbersomely rotate the keys and redistribute to customers. This is often overlooked action and adds extra pain for the DevOps.( p.s: It's not happier as it seems to be in the adajcent picture) Solution To help alleviate some of the above risks, Veritas has leveraged the ability to enhance security by introducingshort lived token-based authentication. Beginning with NetBackup 10.2 for Azure and NetBackup 10.4 for AWS (...GCP work in progress), users will have cloud storage accounts and a short-lived refresh token to connect securely to the Alta Recovery Vault storage. These new secrets are added as Credentials in the NetBackup Credential Management (as shown in diagram 2a and 2b) Once the initial connection is established, Veritas credential Management API is solely responsible for renewing, refreshing, accessing and sharing access signature. Isn’t it amazing just no pain to rotate the keys and redistribute! ( I see the cyber security team seems happier and overjoyed ) Diagram 2a: Creating a Credential with the Storage Account and Refresh Token given by Veritas for Azure Diagram 2b: Creating a Credential with the Refresh Token given by Veritas for AWS Solution Benefits Enhanced Security : Short-lived tokens have a limited lifespan, reducing the exposure window for potential attacks. If a token is compromised, its validity period is short, minimizing the risk of unauthorized access. Regular token expiration forces users to re-authenticate, ensuring better security. Mitigating Token Abuse : Tokens are often used to authorize access to resources. By making tokens short lived, we limit the time an attacker can use to abuse a stolen token. Thus, minimizing the risk window significantly. Better Management of Permissions : When permissions change (e.g., user roles or access levels), short-lived tokens automatically reflect the updates upon renewal. Long-lived tokens may retain outdated permissions, leading to security risks. Conclusion Introduction to Alta Recovery Vault short lived token authentication adds another layer for ransomware protection thus making applications more secure than ever before. At Veritas, your data’s security is paramount to us and this blog serves just as one simple example of the challenges Veritas short lived tokens can help solve. Further, Veritas is always looking and working for better ways to secure your data. Here are some additional helpful links : Veritas Alta Recovery Vault Technical White Paper Veritas Alta Recovery Vault Security Guide Veritas Alta Recovery Vault Azure ExpressRoute Overview Guide Veritas Alta™ Recovery Vault AWS Direct Connect Overview Guide Please feel free to give feedback and we can answer any queries !! Appreciate everyone time :)NetBackup 10 – Authentication Enhancements with Smart Cards and RBAC
You and your organization have a growing need to ensure authentication methods are robust and resilient. You need to prove you are who you say you are while meeting strict compliance guidelines. Smart-Card authentication For many organizations, Smart Cards provide an excellent method to adopt zero trust security models and, in some cases, comply with federal regulations {link}. This can be a challenge when the Smart Card is not part of the same authentication mechanism as NetBackup. This enhancement provides an option to support the smart card without using a directory service, such AD or LDAP. NetBackup has adapted our smart card authentication in an environment to be more flexible without associating a directory service. The user will be added simply using the Common Name (CN) or Universal Principal Name (UPN) of the certificate for user mapping instead of a complex directory service configuration for the Smart Card. After you toggle on the Smart card authentication, you’ll see the options to proceed without a domain, and which certificate mapping attribute to use. (See picture 1 below) Multi-Factor Authentication for CLI users Your Role-Based Access Control (RBAC) users are granted rights within the WebUI to perform their related workload tasks. There are situations where those RBAC users may need to work on the command line outside of the NetBackup WebUI. There is now a mechanism to allow those users to access the Command Line Interface (CLI). Conversely, you can ensure that this new role is only delegated to those users with the need. Below is the use-case: User already has an RBAC role and has logged into the NetBackup WebUI previously User needs CLI access for short periods (less than 24 hours) In the WebUI, the user must be part of the new NetBackup Command Line (CLI) Administrator Role, in addition to their desired workload RBAC role. This role will allow all commands to be executed by the user, so zero-trust procedures should be taken to grant this role only to users with permissible purpose. From the CLI, a user initiates the login process with the following command, with special attention to the “loginType”: # /usr/openv/netbackup/bin/bpnbat -login -loginType WebUI {CLI screenshot of 2FA workflow, including WebUI popup} Approvals for the CLI login will come to the user’s WebUI session as a 6 digit code. Since the user already had to authenticate in the configured way, this is highly trusted. This allows the bpnbat command to proceed. This allows CLI privileges for the next 24 hours to your user. Therefore, Smart cards are now easier to consume in NetBackup by removing previous directory service requirements, allowing ease-of-use balanced with security. Multi-Factor Authentication for the CLI paired with the new RBAC role offers more control of your users.
Backup Exec 2012 security improvements
Hello, my name is Bill Brown and I'm a software developer for the Backup Exec product team. I've been working on Backup Exec (and its progenitor, Maynard Electronics Maynstream) for nearly 21 years. Over the years I've spent time in just about every part of the product but lately I've been involved in improving the security of the product.
Bring the Power of Symantec's ThreatCon to your Website
Download the free ThreatCon widget from Symantec and you can share Symantec’s threat intelligence with your customers on your website, blog, or intranet. Powered by Symantec’s Global Intelligence Network, this tool provides with up-to-the-minute information on the latest Internet security threats, risks, and vulnerabilities. Download it now at:
OUTLOOK: Can't open archived/stored emails
Hello, Since this week Microsoft updates, Outlook (2010/2016) can't open archived/stored items. Maybe, Outlook is blocking VBScript of custom forms. I'm using EV Client 10/11. To view an email, the users must "restore" to the mailbox and then open it. The message is: This item has been archived by Enterprise Vault. Click here to view the original item (this link doesn't work). Thank you.
