Van Der Beek fue diagnosticado de un cáncer de colon en etapa 3 [el cáncer es grande y puede haber invadido los tejidos cercanos] el año pasado. El tratamiento para esta enfermedad, que puede demorarse años de quimioterapia, radioterapia y cirugías, además de hospitalizaciones y consultas, es muy alto en Estados Unidos, donde no hay sanidad universal y pública.
etiquetas: van der beek, dawson crece, subasta, cáncer
» noticia original (www.20minutos.es)
La presidenta de la Comunidad de Madrid, Isabel Díaz Ayuso, ha criticado este jueves a Vox por su estrategia en materia de inmigración y ha replicado a la formación de Santiago Abascal que «alguien tendrá que limpiar sus casas, recoger sus cosechas y poner los ladrillos de las casas».
etiquetas: ayuso, inmigración, pp, vox
» noticia original (efe.com)
Un análisis internacional elaborado por la Berlin School of Business and Innovation (BSBI) revela que 213 de las 219 multinacionales del sector de la moda no pagan un salario que cubra las necesidades básicas de sus trabajadores, y las grandes empresas españolas no son la excepción. España, con siete grupos de moda analizados (Inditex, Mango, Desigual, Cortefiel, El Corte Inglés, Balenciaga y Pepe Jeans), se sitúa por encima del promedio mundial en cuando a derechos laborales, pero los resultados del estudio muestran un contraste preocupante.
etiquetas: moda, record, trabajadores, inditex
» noticia original (www.infobae.com)
Título original: Letting Go, The Pathway of Surrender
Copyright © by Veritas Publishing
Traducción: Ignacio Torró
Editorial: El grano de mostaza.
Este es el último libro publicado en español del doctor David Hawkins, pionero de la medicina y de la investigación de la conciencia, y maestro de Un curso de milagros.
Basándose en su experiencia personal y en sus más de cuarenta años de práctica clínica, el doctor Hawkins nos propone trabajar conjuntamente con las herramientas del perdón y del dejar ir para mantener en todo momento la paz mental y la alegría, y facilitar la curación.
Este viaje que nos lleva del estrés a la paz no solo es posible, sino que está a nuestro alcance. Como nos recuerda el autor, el sol, siempre radiante, se hace visible cuando las nubes se despejan.
El proceso de dejar ir acelera enormemente la consecución de nuestros objetivos en todos los ámbitos de la vida.
Este es un libro escrito con el corazón, y por la mera exposición a la información que contiene ayuda al lector a dar el siguiente paso en la vida.
El doctor David R. Hawkins practicó la psiquiatría desde 1952, y fue miembro vitalicio de la American Psychiatric Association y otras muchas organizaciones profesionales. Participó en numerosos programas de televisión, entre ellos el de Oprah Winfrey. Hawkins es autor de numerosas publicaciones, libros, vídeos y series de conferencias sobre temas científicos y espirituales. Escribió, junto con el premio Nobel Linus Pauling, el famoso libro Orthomolecular Psychiatry. Durante algunos años fue asesor de las diócesis episcopaliana y católica, de diversas órdenes monásticas y otras organizaciones religiosas. Hawkins ha ofrecido multitud de conferencias en instituciones muy prestigiosas, como el Foro de Oxford, la abadía de Westminster y en las universidades Notre Dame, Michigan, Fordham y Harvard, además de otras en Argentina. Pronunció la conferencia anual «Landsberg» en la Facultad de Medicina de la Universidad de California en San Francisco. También ha asesorado a gobiernos extranjeros en temas de diplomacia internacional y ha jugado un papel fundamental en la resolución de antiguos conflictos que constituían importantes amenazas para la paz mundial. En reconocimiento a sus contribuciones al bienestar de la humanidad, el doctor Hawkins ha sido nombrado caballero de la Orden Soberana de los Hospitalarios de San Juan de Jerusalén, fundada en 1077.
Tiempo estimado de lectura: 42 minutos.
Objetivos de este libro:
Ideas principales:
Algunas de las cosillas que aprendí leyendo este libro que no tienen por qué ser ni ciertas ni falsas ni todo lo contrario:
¿Has leído este libro? ¿Algún libro parecido? ¿Tienes alguna cosa que decir sobre lo que expone este libro? ¿Recomiendas algún libro relacionado a este? Estaré encantado de leer lo que piensas sobre este libro en los comentarios.
Algunos enlaces relacionados:
Algunos libros relacionados:
raul
En el mensaje de esta semana hablo de la frecuencia con la que ocurren los llamados "cisnes negros", sucesos de poco probabilidad de ocurrir y de gran impacto.
The post Cisnes negros first appeared on Toma de Decisiones Miguel A. Ariño.
Amazon Web Services (AWS) announces JWT Verification for Application Load Balancer (ALB), enabling secure machine-to-machine (M2M) and service-to-service (S2S) communications. This feature allows ALB to verify JSON Web Tokens (JWTs) included in request headers, validating token signatures, expiration times, and claims without requiring modifications to application code.
By offloading OAuth 2.0 token validation to ALB, customers can significantly reduce architectural complexity and streamline their security implementation. This capability is particularly valuable for microservices architectures, API security, and enterprise service integration scenarios where secure service-to-service communication is critical. The feature supports tokens issued through various OAuth 2.0 flows, including Client Credentials Flow, enabling centralized token validation with minimal operational overhead.
The JWT Verification feature is now available in all AWS Regions where Application Load Balancer is supported.
To learn more, visit the ALB Documentation.
Today, we’re excited to announce the independent affirmation of our Amazon Elastic Kubernetes Service (Amazon EKS) zero operator access posture.
Because security is our top priority at Amazon Web Services (AWS), we designed an operational architecture to meet the data privacy posture our regulated and most stringent customers want in a managed Kubernetes service, giving them continued confidence to run their most critical and data-sensitive workloads on AWS services. Our services are designed to prevent AWS personnel from having technical pathways to read, copy, extract, modify, or otherwise access customer content in the management of Amazon EKS.
At AWS, earning trust isn’t only a goal, it’s one of the core Leadership Principles that guides every decision we make. Customers choose AWS because they trust us to provide the most secure global cloud infrastructure on which to build, migrate, and run their workloads, and to store their data. To build on this trust, we launched the AWS Trust Center to make information about how we secure our customers’ assets in the AWS Cloud more accessible. Along with this launch, we’re describing how we approach operator access to demonstrate an industry leading data privacy posture, and how we fulfill our part of the AWS Shared Responsibility Model in the AWS Cloud.
Many of the AWS core systems and services are designed with zero operator access, meaning they operate based on an architecture and model that, at the minimum, prevents any form of access to customer content in the management of the service. Instead, their systems and services are administered through automation and secure APIs that protect customer content from inadvertent or even coerced disclosure. Some of these services are AWS Key Management Service (AWS KMS), Amazon Elastic Compute Cloud (Amazon EC2) (through the AWS Nitro System), AWS Lambda, Amazon EKS, and AWS Wickr.
When AWS made its Digital Sovereignty Pledge, we committed to providing greater transparency and assurance to customers about how AWS services are designed and operated, especially when it comes to handling customer content. As part of that increased transparency, we engaged NCC Group, a leading cybersecurity consulting firm based in the United Kingdom, to conduct an independent architecture review of Amazon EKS, and the security assurances we provide to our customers. NCC Group has now issued its report and affirmed our claims. The report states:
“NCC Group found no architectural gaps that would directly compromise the security claims asserted by AWS.”
Specifically, the report validates the following statements about the Amazon EKS security posture:
The detailed NCC Group report examines each of these claims, including the scope, methodology, and steps that NCC Group used to evaluate the claims.
AWS has always used a least privilege model to minimize the number of humans that have access to systems processing customer content. This means that we design our products and services to provide each Amazonian access to only the minimum set of systems required to do their assigned task or responsibility and limit that access to when it’s needed. Any access to systems that store or process customer data is logged, monitored for anomalies, and audited. AWS designs all of its systems to prevent access by AWS personnel to customer content for unauthorized purposes. We commit to that in our AWS Customer Agreement and AWS Service Terms. AWS operations never require us to access, copy, or move a customer’s content without that customer’s knowledge and authorization.
Our operational architecture includes the exclusive use of AWS Nitro System-based instances to provide a confidential compute baseline for the managed Kubernetes control plane.
We use a set of restricted administrative APIs to enable precise control of access so our operators can conduct precise, allow-listed actions for troubleshooting and diagnostics without requiring direct or interactive access to the Kubernetes control plane instances. These APIs have been purposefully engineered without technical means to access customer content in the Kubernetes control plane or the customer’s Kubernetes data plane.
Following our standard change management mechanisms, we enforce a built-in, multi-party review and approval process for modifications to these restricted administrative APIs, and the accompanied policies that further strengthen the guardrails of how we operate the service. This model is implemented consistently across Amazon EKS clusters, regardless of the customer’s chosen launch mode for the Kubernetes data plane.
Additionally, every interaction with these restricted administrative APIs generates logs, with mandatory authentication and authorization, following the least privilege principle. By enabling their cluster’s audit logs, customers can maintain visibility into all actions performed by AWS personnel on the cluster’s API endpoint.
By default, we envelope encrypt all Kubernetes API data before it is stored at rest in the etcd database, and further secure backup storage of the etcd database to add multi-layered protection to prevent access to customer content in cluster snapshots. Furthermore, our system is designed so that no AWS personnel can access any of the plaintext encryption keys used to secure data in the etcd database and its backups.
These operator access controls apply uniformly to the Amazon EKS control plane, regardless of how you run your worker nodes—whether self-managed, through Amazon EKS Auto Mode, or with AWS Fargate. As stated in the AWS Shared Responsibility Model, customers remain responsible for securing the configurations of the Kubernetes worker nodes, with the exception of Amazon EKS Auto Mode and Fargate launch modes. For more information about the security of these AWS managed data plane launch modes in Amazon EKS, see the relevant links in the Learn more section.
Amazon EKS is designed and built to make sure that no AWS employee can read, copy, modify, or otherwise access customer content in Amazon EKS. By using AWS Nitro System‑based confidential compute, tightly‑scoped administrative APIs, multi‑party change‑approval processes, and end‑to‑end encryption, AWS avoids technical pathways for operator access. Independent validation from the NCC Group found no architectural gaps that would undermine these guarantees. In short, Amazon EKS delivers a zero operator access model that can meet the strictest regulatory and sovereignty requirements, giving organizations the confidence to run their most sensitive, mission‑critical workloads on AWS.
If you have feedback about this post, submit comments in the Comments section below. If you have questions about this post, contact AWS Support.
Micah is a Principal Software Engineer at AWS and focuses on Kubernetes and container security.
Lukonde is a Senior Product Manager at AWS in the Amazon EKS team, focusing on networking, resiliency, and operational security. He has years of experience in application development, solution architecture, cloud engineering, and DevOps workflows.
Manu is a program manager at AWS based in Amsterdam, the Netherlands. Manu leads compliance and security assurance audits and engagements across AWS Regions and industries. For the past 20 years, he has worked in information systems audits, ethical hacking, project management, quality assurance, and vendor management
Tari is a Security Assurance Program Manager at AWS, based in London. Tari is responsible for third-party and customer audits, attestations, certifications, and assessments across EMEA. Previously, Tari worked in Security Assurance and Technology Risk in the big four and financial services industry.
I’m off today so here’s an older post from the archives. This was originally published in 2020.
A reader writes:
I’m the executive assistant for a small company. I’m the direct support for the VP of human resources, “Dave,” who is very charismatic and likable and a generally nice guy. He’s also very good looking. However, he’s very professional with great business boundaries. I enjoy working with him.
Two managers in particular, “Karen” and “Nancy,” need to meet with him all the time. All. The. Time. Their departments aren’t undergoing any HR issues, they don’t have any staffing needs, and they’re not hiring or firing anybody right now. They call to schedule multiple meetings a week, drop by to see if he’s available for 1:1s when his schedule doesn’t have a single second free, and call him multiple times a day. Dave always routes them back to me to take a message or schedule them with him. Nancy gets angry with me when I tell her he’s not available and blew up at me last week that I’m “not his chaperone.”
Dave has noticed it and so have a few other execs. Dave’s been very clear about making both of them go through the same process other staff members go through to schedule with him. Just the same, other staff have started calling them his “fan club” and me the “bouncer.”
When I was working with the other assistants and operators on a training, word about his “fan club” had gotten around and one person mentioned that Karen calls me names and tells the other staff I’m in love with Dave and don’t want other women near him, which is why I never let her schedule with him. She even showed me a few emails in which Karen advised her department support professional to go over my head to see Dave and that I wasn’t the “keeper of his zipper.”
I’m not sure how to approach this. I’m more angry than I am embarrassed. I’m also bothered because the support staff report to me, and some of my staff have reported both Nancy and Karen as being difficult to work with and unpleasant in other aspects of the day-to-day, not just in regards to the Dave thing. Where do I start with this?
This is so gross!
If Karen and Nancy were simply trying to meet with Dave all the time, that would be annoying but manageable. Even then, though, at some point Dave would probably need to shut it down more firmly than he has. (Not that he’s at fault here! It sounds like he’s managing an uncomfortable situation pretty professionally — but needs to hear how it’s gone off the rails.)
But this is more than Karen and Nancy trying to get a weird amount of Dave’s attention. Blowing up at your for doing your job, calling you names (!), spreading rumors that you’re in love with him, and ever uttering the words “keeper of his zipper” in a work context is … ugh, so over the line and gross and violating. To you, and also to Dave.
It’s time for you to talk to him. It’s going to be awkward and uncomfortable, and you need to do it anyway. (Remember that the awkwardness is 100% on Karen and Nancy, not you.) He needs to know the full extent of what’s happening, how out of control it’s become, and how it’s affecting you.
If you’re hesitating to do that because it feels uncomfortable or you don’t want to burden him with this or you feel like you should be able to deal with it yourself … you still need to talk to him, for three key reasons. First, he deserves to know what’s being said about him so he can decide for himself how he wants to handle it. It’s not right to let this happen behind his back without informing him. Second, as your boss he needs to be aware that you’re being harassed and mistreated. Third, as the VP of HR, he has a professional obligation to intervene and ensure this is shut down — his job in the company requires it (and there’s a point where not acting will make people question HR’s competence, and how seriously HR would take it if someone else were facing similar issues).
So talk to Dave. Tell him all of it — the name-calling, the yelling at you, the rumors, the undermining you, all of it. And I’m sorry to say, you’re going to have to repeat the “keeper of his zipper” line because that makes it clear just how over the line this has become.
You can tell him you’re embarrassed to have to repeat all this, but it’s important that you tell him it’s happening, and that you tell him it’s at the point that HR needs to intervene and shut it down.
If Dave is as great as he sounds — really, even if he’s only sort of okay — he’s going to be grateful you told him and will deal with it so you don’t have to. It’s his job! Let him have the info he needs to do it.
The post my coworkers have a crush on my boss … and are taking it out on me appeared first on Ask a Manager.
With aggressive ICE raids expanding to an increasing number of cities, I’m sharing the following guidance from a community organizer in Chicago about what to do if ICE shows up at your workplace.
I’m in Chicago, which has been targeted aggressively by ICE and Border Patrol for the last two months. ICE actions are expanding into many other cities, and I wanted to share some resources and tips from our city’s experiences with your readers.
Inc. has a solid article on the rights of business owners when ICE shows up. It’s important to know what your rights are, especially about private areas and documentation. However, ICE frequently and blatantly disregards legal limitations, and when confronted with armed, masked strangers, it may be difficult for individuals to physically intervene to stop them from going into off-limits areas. Owners and managers should provide information to employees about their rights, as immigrants and as citizens. Be prepared to document ICE when they’re at your business; you may need evidence of their actions if they violate your rights or abduct any workers. (The latter is critical to help families find out what happened if someone is taken.)
As an employee, you may be more limited, especially if management isn’t supportive. Many places, especially large corporations, are adopting a neutral position towards ICE’s activities, which effectively means letting them operate unchecked. Employees can leave Know Your Rights (KYR) info in staff areas for people to take. Try to get in touch with your local ICE Watch or immigrant rights groups as well. Many of them are sending out alerts when ICE is active in a particular area, so you can be aware if they’re near your place of business.
Some other, more hands-on tips:
- Landscapers, construction workers, and other contractors are extremely vulnerable. Despite claims that they’re arresting “the worst criminals,” ICE literally drives around and abducts brown people working outdoors. If your business employs any of these services, work with them to develop a safety plan if ICE shows up. For example, letting them come inside and go into an employee-only space until it’s all clear.
- Share information and resources, but do not make risk assessments for other people. Don’t tell Latino coworkers to work from home because it’s safer for them, for instance. Instead, if you’re in a position to do so, allow for more flexible WFH as a choice for anyone who might need it.
- If you’re a manager, try to offer compassion and flexibility. Vulnerable employees are going to be extremely stressed with the constant, unpredictable fear of friends, family, or even themselves being abducted. You may also have employees who are volunteering with ICE Watch organizations, which can be emotionally and mentally draining as well.
- In Chicago, raids have been extremely unpredictable day-to-day. We don’t know when or where they’re going to hit. You unfortunately have to assume that ICE could show up at any time. This is why it’s critical to have plans and education as soon as possible.
- Do NOT post about what you’re doing on social media or non-secure servers — which often includes workplace communications. Use a secure app like Signal or have conversations in person. This goes double if you record a raid. Don’t post it online, save it for the lawyers and immigration advocates.
Above all else, the best thing that you can do in your community is to connect with local ICE Watch and immigrant rights orgs. They have information, resources, and contacts that will help you and your neighbors. Get info, coordinate with your coworkers, and build a community to protect each other.
I’m updating this post to add these additional resources shared by a reader:
The post what to do if ICE agents come to your workplace appeared first on Ask a Manager.
Si te estás preguntando cómo saber si tengo un bloqueo emocional, este post es para ti. A veces no sabes […]
La entrada Cómo saber si tienes un bloqueo emocional (incluye test) se publicó primero en Elena Arnaiz Talento & Acción.
To prioritize the safety and security of the ecosystem, Kubernetes SIG Network and the Security Response Committee are announcing the upcoming retirement of Ingress NGINX. Best-effort maintenance will continue until March 2026. Afterward, there will be no further releases, no bugfixes, and no updates to resolve any security vulnerabilities that may be discovered. Existing deployments of Ingress NGINX will continue to function and installation artifacts will remain available.
We recommend migrating to one of the many alternatives. Consider migrating to Gateway API, the modern replacement for Ingress. If you must continue using Ingress, many alternative Ingress controllers are listed in the Kubernetes documentation. Continue reading for further information about the history and current state of Ingress NGINX, as well as next steps.
Ingress is the original user-friendly way to direct network traffic to workloads running on Kubernetes. (Gateway API is a newer way to achieve many of the same goals.) In order for an Ingress to work in your cluster, there must be an Ingress controller running. There are many Ingress controller choices available, which serve the needs of different users and use cases. Some are cloud-provider specific, while others have more general applicability.
Ingress NGINX was an Ingress controller, developed early in the history of the Kubernetes project as an example implementation of the API. It became very popular due to its tremendous flexibility, breadth of features, and independence from any particular cloud or infrastructure provider. Since those days, many other Ingress controllers have been created within the Kubernetes project by community groups, and by cloud native vendors. Ingress NGINX has continued to be one of the most popular, deployed as part of many hosted Kubernetes platforms and within innumerable independent users’ clusters.
The breadth and flexibility of Ingress NGINX has caused maintenance challenges. Changing expectations about cloud native software have also added complications. What were once considered helpful options have sometimes come to be considered serious security flaws, such as the ability to add arbitrary NGINX configuration directives via the "snippets" annotations. Yesterday’s flexibility has become today’s insurmountable technical debt.
Despite the project’s popularity among users, Ingress NGINX has always struggled with insufficient or barely-sufficient maintainership. For years, the project has had only one or two people doing development work, on their own time, after work hours and on weekends. Last year, the Ingress NGINX maintainers announced their plans to wind down Ingress NGINX and develop a replacement controller together with the Gateway API community. Unfortunately, even that announcement failed to generate additional interest in helping maintain Ingress NGINX or develop InGate to replace it. (InGate development never progressed far enough to create a mature replacement; it will also be retired.)
Currently, Ingress NGINX is receiving best-effort maintenance. SIG Network and the Security Response Committee have exhausted our efforts to find additional support to make Ingress NGINX sustainable. To prioritize user safety, we must retire the project.
In March 2026, Ingress NGINX maintenance will be halted, and the project will be retired. After that time, there will be no further releases, no bugfixes, and no updates to resolve any security vulnerabilities that may be discovered. The GitHub repositories will be made read-only and left available for reference.
Existing deployments of Ingress NGINX will not be broken. Existing project artifacts such as Helm charts and container images will remain available.
In most cases, you can check whether you use Ingress NGINX by running kubectl get pods \--all-namespaces \--selector app.kubernetes.io/name=ingress-nginx with cluster administrator permissions.
We would like to thank the Ingress NGINX maintainers for their work in creating and maintaining this project–their dedication remains impressive. This Ingress controller has powered billions of requests in datacenters and homelabs all around the world. In a lot of ways, Kubernetes wouldn’t be where it is without Ingress NGINX, and we are grateful for so many years of incredible effort.
SIG Network and the Security Response Committee recommend that all Ingress NGINX users begin migration to Gateway API or another Ingress controller immediately. Many options are listed in the Kubernetes documentation: Gateway API, Ingress. Additional options may be available from vendors you work with.
Que vengan a enseñarnos cómo lo hacen. Eso es lo que le ha pedido este miércoles Josep Maria Recasens, presidente de Renault España, a las marcas de coches chinas que están ganando terreno a pasos agigantados en Europa. “Aquí [a Europa] no se puede venir y construir cuatro chapas con ruedas y asientos con poco valor añadido. Lo que hay que hacer es comprometerlas a que nos enseñen, que vengan con productos con valor añadido. No lo hicimos así nosotros cuando fuimos a China, no deben hacerlo ellos cuando vienen a Europa”.
etiquetas: recasens, renault, china, europa
» noticia original (cincodias.elpais.com)
El 'espionaje' cruzado entre los ahora investigados era un 'modus operandi' para garantizarse "participación o silencio"
etiquetas: corrupción, policía, local, granada
» noticia original (www.elindependientedegranada.es)
Madrid ha vuelto a reventar la reunión del Consejo Interterritorial de Salud. Cuando todas las comunidades del PP estaban de acuerdo ya en entregar los datos sobre sus programas de prevención, la presidenta de la Comunidad de Madrid, Isabel Díaz Ayuso, dice que no va a aportar esos datos que Sanidad necesita para dibujar un mapa con estos programas tras graves fallos que se han producido en Andalucía.
etiquetas: madrid, sanidad, cribados, autonomías
» noticia original (cadenaser.com)
Hackmanac es una empresa internacional de ciberseguridad que monitorea diferentes filtraciones y ciberataques a empresas y dependencias gubernamentales. Es conocida en España por haber sido la primera en identificar varios ataques y que ahora ha revelado una nueva filtración, que ha afectado a ING Bank España.
etiquetas: hackeo, ing, datos clientes, filtrados
» noticia original (blog.elhacker.net)
Continúa la polémica entre Ryanair y el Gobierno a cuenta de las tasas de Aena. Pues bien, ¿a que no adivinan de qué lado se ha posicionado la presidenta madrileña Isabel Díaz Ayuso? No había duda ninguna. La presidenta madrileña inauguró este martes un centro de formación de pilotos y tripulantes de la polémica compañía, en medio de su choque judicial y mediático con el Gobierno español.
etiquetas: ryanair, isabel díaz ayuso, humor
» noticia original (www.publico.es)
El sueño continuo es un hábito moderno, no un fruto natural de nuestra evolución. Y eso ayuda a explicar por qué muchos de nosotros seguimos despertándonos a las 3 de la madrugada y nos preguntamos si algo va mal. Puede ser útil saber que se trata de una experiencia profundamente humana.
etiquetas: dormir, turnos, tiempo
» noticia original (theconversation.com)
En el entorno del campus de Somosaguas se han desplegado más de una decena de furgones de la Policía Nacional, que han establecido un amplio cordón de seguridad para mantener separados a los dos grupos congregados: uno frente a la facultad, con banderas republicanas, y otro en la parte superior de la calle, donde se ondeaban banderas de España y la Cruz de Borgoña.
etiquetas: vito quiles, complutense, policía
» noticia original (www.elperiodico.com)
