(CEP-19129) Security Administration Dashboard
Interaction Date:June 18 - June 28, 2024 Interaction Type:Q&A Interview / Interactive Research Session The Veritas Research Team is conducting an interactive research session about the security administration dashboard. This two part session will focus on understanding your definition and triage of theats, and the second part will focus on walkthrough of some security dashboard the design team is creating to get your feedback. If you are interested in getting more details about this opportunity or in participating in other exciting interactions and are not currently a member of our CPEP program, you can register here:https://cpep.veritas.comthencontact us atcustomer.engagement@veritas.com.138Views0likes0CommentsWhen it comes to SECRETS, how secure is yourapplication?
Introduction Enterprises running various heterogeneous workloads ranging from on prem applications to applications spread across various cloud service providers, oftenstruggle 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 forrenewing, 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 freeto give feedback and we can answer any queries !! Appreciate everyone time :)609Views3likes0CommentsCVE-2023-38545/6 security vulnerability.
In trying to assess implications of the CURL hack upon Data Insight I see the\DataInsight\perl\site\lib\HTTP\Any\Curl.pm perl module listslibcurl 7.21.6 or newer. While that is a very old version and specifically the CVEs call out Affected Versions Affected versions: libcurl 7.69.0 to and including 8.3.0 Not affected versions: libcurl < 7.69.0 and >= 8.4.0 (where a patch has been identified) we are left to wonder as to ramifications of system software changes upon the Application. Our organization will be patching for the various applications utilizing http calls over Socks5 (mentioned as a proxy in the script) and I will need to know a few facts to enter discussions with our security team. Is DI affected by the vulnerability? Will DI be aversely affected by patching to the latest library version? Has Veritas released any statement on the vulnerability and its products? Thank you PixSolved1.3KViews0likes2Comments(CEP-18692) Security Vendor Survey
Interaction Date: June 21 - June 30, 2023 Interaction Type: Online Survey Our Cyber Security PM team is interested to get your feedback about Security Vendors that are in use in your environment (On prem and cloud) If you are interested in participating other exciting interactions, and are not currently a member of our CPEP program, you can register here:https://cpep.veritas.comthencontact us atcustomer.engagement@veritas.com.396Views0likes0CommentsApache Tomcat JNDI features used in DI <Pri:1>
With the release of a POC for theApache Log4j2 CV can we confirm Data Insight is or is not affected? NIST-https://nvd.nist.gov/vuln/detail/CVE-2021-44228 Mitre -https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228,== What effect will setting 'MsgNoLookups' or disabling 'trustURLCodebase' have on DI's operations and logging? ref:https://www.oracle.com/java/technologies/javase/8u121-relnotes.html Thank you PixSolved2.3KViews0likes5CommentsOpenSSL vulnerability <Security>
Can we claim Data Insight is not affected by these known issues? CVE-2021-3449:Crash can be provoked when connecting to a vulnerable server. CVE-2021-3450:Vulnerable client can be tricked into accepting a bogus TLS certificate. What, if any, affect will these exploits have on DI? thank you PixSolved1.3KViews0likes2CommentsI do not see mention of the NFSv4 for Data Insight in the documentation or knowledgebase.
The documents released for the 6.1 version up to 6.1.6 of DI have no mention of 'NFSv4', 'NFS4' and in the SCL only NFS3 version seems supported. Are there plans to update to the latest version available in the coming 6.2 release? The known issues with the older version need be avoided. We would also like to utilize the enhancements of increased performance,File locking, the Delete bits, and benefits of security, mixed mode operations, while removing user group limitations. Thank you Pix1KViews0likes1CommentSubscription for Veritas NetBackup Security Vulnerabilities
Hello All, I have found this linkhttps://www.veritas.com/content/support/en_US/security however is there another way to be notified of Veritas Netbackup critical/high security vulnerabilities along with patch and version releases? Thank you in advance.Solved1.1KViews0likes2Comments