Zero instrumentation monitoring with your first steps in eBPF Beatriz Martínez, Isovalent - @beatrizmrg October 28, 2020 2 What will we be doing? 3 How are we going to do it? 4 Demo time 5 Tracing

Is std::mdspan a Zero-overhead Abstraction? Oleksandr Bacherikov Snap IncWhat is std::mdspan? It’s a view over a multi-dimensional array. It’s designed primarily to be used as a function parameter right? 24 Wrong! std::layout_stride supports only all strides specified at runtime. If we target zero overhead, we have to specify one of the strides as 1 at compile time.What does the Standard offer

HTTP Parameter Pollution in Hashicorp secret vault (Low) Orchestration Hardening Network Policy Zero-Trust Concepts RBAC Secrets Management Conclusions Cure53, Berlin · 07/01/20 io/daprio/daprd:0.8.0", "command": [...], "args": [...], "ports": [...], "env": [..., {"name": "DAPR_TRUST_ANCHORS", Cure53, Berlin · 07/01/20 7/19 Dr.-Ing. Mario Heiderich es-networking-792b41e19d69 Zero-Trust Concepts Zero-trust concepts have emerged from the rapid migration to Cloud-based infrastructure. The concept of zero-trust does not solely rely on establishing

Privilege Escalation Who: •Ransomware gangs •advanced adversaries •Game hackers How: •Looking at the trust between medium to high integrity levels •Configurations •Filesystem Lateral movement Who: •Financial Controlled Heap MemoryWhy Remote Code Execution (RCE)? ● High Impact and Exploitability ○ High Value of Zero-Days ● Expanded Attack Surface ○ Cloud computing ○ Remote work ○ Increase in internet-connected Surface? Start by defining Trust BoundariesWhat is a Trust Boundary? Anytime there is a crossing of the trust between an untrusted component to a trusted componentDefining Trust Boundaries Downloads from

participants may not fully trust one another (they may, for example, be competitors in the same industry), a network can be operated under a governance model that is built off of what trust does exist between protocols that enable the platform to be more effectively customized to fit particular use cases and trust models. For instance, when deployed within a single enterprise, or operated by a trusted authority In such a context, there can be no trust other than that the state of the blockchain, prior to a certain depth, is immutable. In order to mitigate this absence of trust, permissionless blockchains typically

participants may not fully trust one another (they may, for example, be competitors in the same industry), a network can be operated under a governance model that is built off of what trust does exist between protocols that enable the platform to be more effectively customized to fit particular use cases and trust models. For instance, when deployed within a single enterprise, or operated by a trusted authority In such a context, there can be no trust other than that the state of the blockchain, prior to a certain depth, is immutable. In order to mitigate this absence of trust, permissionless blockchains typically

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 62.3. Zero Persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Seamless high availability. We provide a HA solution with automatic client failover so you can guarantee zero message loss or duplication in event of server failure. • Hugely flexible clustering. Create clusters a connection TTL imposed upon them by the broker. For STOMP 1.1 and 1.2 clients which send a non-zero client-to-server heart-beat header value then their connection TTL will be set accordingly. However

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 61.3. Zero Persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Seamless high availability. We provide a HA solution with automatic client failover so you can guarantee zero message loss or duplication in event of server failure. • Hugely flexible clustering. Create clusters a connection TTL imposed upon them by the broker. For STOMP 1.1 and 1.2 clients which send a non-zero client-to-server heart-beat header value then their connection TTL will be set accordingly. However

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 61.3. Zero Persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Seamless high availability. We provide a HA solution with automatic client failover so you can guarantee zero message loss or duplication in event of server failure. • Hugely flexible clustering. Create clusters a connection TTL imposed upon them by the broker. For STOMP 1.1 and 1.2 clients which send a non-zero client-to-server heart-beat header value then their connection TTL will be set accordingly. However

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 61.3. Zero Persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Seamless high availability. We provide a HA solution with automatic client failover so you can guarantee zero message loss or duplication in event of server failure. • Hugely flexible clustering. Create clusters a connection TTL imposed upon them by the broker. For STOMP 1.1 and 1.2 clients which send a non-zero client-to-server heart-beat header value then their connection TTL will be set accordingly. However