Home Blog Page 8

Degree up Your Safety Stack with Splunk on Cisco

codesanitize
-
0
Degree up Your Safety Stack with Splunk on Cisco


Are you a Cisco Safety buyer in search of deeper, extra centralized insights into your safety posture? The Enhancing Cisco Safety Options with Knowledge Analytics (ECSS) Studying Path in Cisco U. is designed that can assist you just do that. This complete Studying Path focuses on the highly effective integration of Cisco Safety merchandise with Splunk, providing a streamlined strategy to information evaluation and a unified view of your safety panorama.

Too many dashboards, not sufficient perception

Cisco merchandise supply incredible choices for assembly all of your safety information wants, however with out Splunk, chances are you’ll want to make use of a number of dashboards or manually correlate information from varied sources.

This could result in:

  • Inefficiencies: Spending helpful time switching between dashboards and manually correlating information.
  • Delayed response: Issue figuring out and responding to threats in real-time, notably AI threats.
  • Elevated complexity: The sheer quantity of information and the shortage of a unified view can simply overwhelm anybody.

The answer: Cisco and Splunk for unified safety intelligence

There’s a solution to get all these insights streamlined into one dashboard.

Splunk gives a unified platform for information aggregation, evaluation, and visualization, providing a single pane of glass into your total safety ecosystem, together with any operational expertise (OT) networks that may have been beforehand siloed.

Right here’s the way you’ll profit:

  • Centralized information assortment: Combination information from all of your Cisco safety merchandise right into a single Splunk occasion.
  • Customizable dashboards: Create tailor-made dashboards that present the precise insights you want.
  • Actual-time monitoring: Monitor your safety setting in real-time and reply to threats sooner.
  • Enhanced operational effectivity: Scale back complexity and streamline your safety workflows.
  • Improved decision-making: Make knowledgeable choices primarily based on complete and correct information.

What does ECSS cowl?

The ECSS Studying Path covers introductory to intermediate-level data of Splunk and methods to use it for detecting, investigating, and responding to safety threats throughout your total community, whether or not on-site or utilized by a contractor globally.

There are six tracks:

  • Observe 1: The Fundamentals of Observability
  • Observe 2: Cisco, together with Cisco XDR, Splunk SIEM, and Splunk SOAR.
  • Observe 3: Cisco Cloud Safety App
  • Observe 4: Cisco Safety Legacy Apps and Know-how Add-Ons
  • Observe 5: Cisco Safety with Splunk Use Circumstances
  • Observe 6: Cisco Apps Troubleshooting and Tuning

A free pre-release of Tracks 1 and three is now out there on Cisco U. The remaining, together with all labs, will probably be launched later within the Summer time of 2025.

Get began on ECSS at the moment

The ECSS Studying Path gives a transparent path to enhanced safety administration by integrating Cisco Safety merchandise with Splunk. By centralizing information, streamlining workflows, and offering real-time insights, you’ll be able to improve your safety posture and defend your group from evolving threats.

Begin studying ECSS at the moment and expertise the advantages of a really unified safety answer. The ability to achieve full visibility and management of your safety setting is at your fingertips.

How will this Studying Path provide help to? Tell us within the feedback!

Additional Cisco U. Splunk studying

Set Up Cisco Duo with Splunk for Multifactor Authentication Logging

Highlight 2024: Safe Syslog from the ASA to Splunk by way of SC4S

Community Entry Management Monitoring Utilizing Cisco Identification Companies Engine and Splunk

 

Join Cisco U. | Be a part of the  Cisco Studying Community at the moment without spending a dime.

Comply with Cisco Studying & Certifications

X | Threads | Fb | LinkedIn | Instagram | YouTube

Use  #CiscoU and #CiscoCert to hitch the dialog.

Share:



Getting ready for TLS certificates lifetimes dropping from 398 days to 47 days by 2029

codesanitize
-
0
Getting ready for TLS certificates lifetimes dropping from 398 days to 47 days by 2029


Earlier this month, the Certification Authority(CA)/Browser Discussion board voted to considerably shorten the lifetime of TLS certificates: from 398 days at present to 47 days by March 15, 2029.

The CA/Browser Discussion board is a collective of certificates issuers, browsers, and different functions that use certificates, they usually’ve lengthy been discussing the potential for shorter certificates lifetimes. 

Because of this vote to alter the TLS certificates lifetime, the lifetimes will step by step shorten over the subsequent 5 years. Beginning March 15, 2026, the utmost lifetime shall be 200 days, after which a yr after that it’ll drop right down to 100 days. Two years following that deadline, certificates lifetimes will hit the brand new restrict of 47 days on March 15, 2029. 

Moreover, beginning March 15, 2029, the utmost interval that area validation info will be reused shall be 10 days. In any other case, it is going to observe the identical schedule because the certificates lifetimes (398 days at present, 200 days after March 15, 2026, and 100 days after March 15, 2027).

Dean Coclin, senior director of Business Technique at DigiCert, joined us on our podcast this week to debate the vote and the adjustments, and he mentioned that one of many primary drivers behind this alteration is to make the web safer. At the moment, there are two forms of certificates revocation processes which might be used. 

One is the certificates revocation record (CRL), which is a static record of revoked certificates that must be continuously checked manually. 

The opposite is the On-line Certificates Standing Protocol (OCSP), the place the browser checks again with the CA’s certificates standing record to see if the certificates is nice. 

“Every of these applied sciences has some drawbacks,” Coclin mentioned. “For instance, CRL can turn out to be very, very massive and might decelerate your internet shopping. And the second, OCSP, has some type of privateness implications as a result of each time your browser makes a request to the certificates authority to examine the standing of a certificates, some info is leaked, like the place that IP tackle is coming from that’s checking that web site, and what’s the web site that’s being checked.”

As a result of neither resolution is good, there turned curiosity in shortening the validity interval of certificates to cut back the period of time a nasty certificates may very well be in use.  

Google had initially proposed a 90 day certificates lifetime, after which final yr Apple proposed going even shorter to 47 days, which is finally the choice that was handed. 

Based on Coclin, automation shall be key to maintaining with shorter lifetimes, and a part of the explanation this alteration is so gradual is to present folks time to place these techniques in place and alter. 

“The times of with the ability to regulate certificates expirations with a calendar reminder or a spreadsheet are actually going to be over. Now you’re going to should automate the renewal of those certificates, in any other case, you’re going to face an outage, which will be devastating,” he mentioned. 

There are a number of applied sciences on the market already that assist with this automation, such because the ACME protocol, which automates the verification and issuance of certificates. It was created by the Web Safety Analysis Group and printed as an open customary by the Web Engineering Process Pressure (IETF). 

Certificates issuers additionally provide their very own instruments that may assist automate the method, resembling DigiCert’s Belief Lifecycle Supervisor.

Coclin believes that after automation is in place, it’s attainable that sooner or later, the certificates lifetimes could lower additional, doubtlessly even to 10 days or much less. 

“That’s solely going to be attainable when the neighborhood at massive adopts automation,” he mentioned. “So I believe this poll, the aim of this was to encourage customers to begin getting automation below their belts, ensuring that web sites shouldn’t have outages, as a result of automation will keep away from that, and preparing for a attainable even shorter validity timeframe to make the probability of a revoked certificates being lively much less possible.”

Tigera extends cloud-native networking with Calico 3.30

codesanitize
-
0
Tigera extends cloud-native networking with Calico 3.30



This logging functionality is uncovered by way of two new elements:

  1. Goldmane: A gRPC-based API endpoint that aggregates movement logs from Calico’s Felix element, which runs on every node.
  2. Whisker: An online-based visualization software constructed with React and TypeScript that connects to the Goldmane API.

The mix of those elements supplies detailed visibility into community visitors patterns inside Kubernetes clusters, addressing a typical ache level for Kubernetes directors who must troubleshoot connectivity points or confirm safety insurance policies.

Staged insurance policies allow safer community coverage implementation

Community insurance policies in Kubernetes are highly effective however probably disruptive if misconfigured. Calico 3.30 introduces staged insurance policies that permit directors to check coverage adjustments earlier than enforcement.

Kelly defined that staged coverage permits community directors to do a dry run of what would occur if a selected coverage is utilized in a Kubernetes cluster. Calico 3.30 is ready to generate movement logs to simulate the affect of how the applying of a selected coverage will affect the cluster. This strategy considerably reduces the chance of service disruptions when implementing community insurance policies, as directors can validate coverage habits earlier than committing to enforcement.

Hierarchical coverage administration with tiers

Past the power to validate coverage earlier than implementation, Calico 3.30 provides new layers of coverage granularity general. Calico 3.30 additionally brings coverage tiers to the open-source version, enabling extra refined coverage administration.

The tier system permits organizations to implement defense-in-depth methods and preserve clear separation between safety insurance policies and application-specific community guidelines. It additionally underpins Calico’s implementation of the Kubernetes Admin Community Coverage function, which is presently in alpha within the Kubernetes undertaking.

The Hidden Information Dangers on Your Cellphone, Half 2

codesanitize
-
0
The Hidden Information Dangers on Your Cellphone, Half 2


Continue

swift – iOS 17 Bug? Including a .sheet to a .fullscreencover makes background opaque

codesanitize
-
0
swift – iOS 17 Bug? Including a .sheet to a .fullscreencover makes background opaque


I’m engaged on making a customized Popup View based mostly on a .fullscreenCover. The .fullscreenCover is used to put the Popup content material on display on a semi-transparent background.

Whereas this works on iOS 18, there’s a drawback on iOS 17: When the Popup content material accommodates a .sheet, the background is just not clear any extra however opaque.

enter image description here
enter image description here

    1. Picture: iOS 17. When exhibiting the Popup an opaque background covers the principle content material. When tapping on the background it turns clear.
    1. Picture: iOS 18. All the things works as meant. When exhibiting the Popup the principle background is roofed with a semi-transparent background.

Eradicating the .sheet(...) from the Popup content material solves the issue. It doesn’t matter if the sheet is used or not. Including it to the view code is sufficient to set off the issue.

Utilizing a .sheet inside a .fullscreenCover shouldn’t be an issue so far as I do know.

Is that this a bug in iOS 17 or is there one thing mistaken with my code?

Code:

struct SwiftUIView: View {
    @State var isPresented: Bool = false
    @State var sheetPresented: Bool = false
    
    var physique: some View {
        ZStack {
            VStack {
                Colour.pink.body(maxHeight: .infinity)
                Colour.inexperienced.body(maxHeight: .infinity)
                Colour.yellow.body(maxHeight: .infinity)
                Colour.blue.body(maxHeight: .infinity)
            }
            
            Button("Present") {
                isPresented = true
            }
            .padding()
            .background(.white)
            
            Popup(isPresented: $isPresented) {
                VStack {
                    Button("Dismiss") {
                        isPresented = false
                    }
                }
                .body(maxWidth: 300)
                .padding()
                .background(
                    RoundedRectangle(cornerRadius: 20)
                        .fill(.white)
                )
                .sheet(isPresented: $sheetPresented) {
                    Textual content("Hallo")
                }
            }
        }
    }
}

struct Popup: View {
    @Binding var isPresented: Bool
    let content material: () -> Content material
    
    init(isPresented: Binding, @ViewBuilder _ content material: @escaping () -> Content material) {
        _isPresented = isPresented
        self.content material = content material
    }
    
    @State non-public var internalIsPresented: Bool = false
    @State non-public var isShowing: Bool = false
    let transitionDuration: TimeInterval = 0.5
       
    var physique: some View {
        ZStack { }
            .fullScreenCover(isPresented: $internalIsPresented) {
                VStack {
                    content material()
                }
                .body(maxWidth: .infinity, maxHeight: .infinity)
                .background(
                    Colour.black.opacity(0.5)
                        .opacity(isShowing ? 1 : 0)
                        .animation(.easeOut(length: transitionDuration), worth: isShowing)
                        .ignoresSafeArea()
                )
                .presentationBackground(.clear)
                .onAppear {
                    isShowing = true
                }
                .onDisappear {
                    isShowing = false
                }
            }
            .onChange(of: isPresented) { _ in
                withoutAnimation {
                    internalIsPresented = isPresented
                }
            }
    }
}


extension View {
    func withoutAnimation(motion: @escaping () -> Void) {
        var transaction = Transaction()
        transaction.disablesAnimations = true
        withTransaction(transaction) {
            motion()
        }
    }
}

1...789...4,116Page 8 of 4,116
© Newspaper WordPress Theme by TagDiv