
Il y en a de plus en plus qui témoignent, je trouve. Par contre Le SDEC était l’ancienne appellation de la DGSE.

Ariane Tabatabai, suspected Iranian agent, working for Pentagon as U.S. coordinated Israel defense
The Washington Times
Frustration is swirling on Capitol Hill after a top Defense Department official revealed that a suspected Iranian influence agent was working at the Pentagon last week while national security officials were coordinating international efforts to defend Israel from a coming Iranian attack.
Sparks flew during a Senate Armed Services Committee hearing last week when Christopher Maier, assistant secretary of defense, told lawmakers that Ariane Tabatabai remained on the job in an office overseeing special operations and irregular warfare despite concerns that she operated at the behest of the Iranian regime.
Why Did Boeing Sunset Its Diversity, Equity & Inclusion Department?
Simple Flying
The latest slew of changes at US planemaker Boeing has resulted in the company no longer having a Diversity, Equity, and Inclusion (DEI) department. The troubled manufacturer has reportedly confirmed that staff members who were in the now-defunct department will be re-assigned, while the department's head has since left the company.
The move has undoubtedly led to some questioning why the planemaker decided to follow suit. However, its new CEO, Kelly Ortberg, has been tasked with not only significantly improving the company’s reputation but also its suffering profits.
Accusée de sabotage, la Russie convoque un haut diplomate canadien
Radio-Canada
Un haut diplomate de l’ambassade canadienne en Russie a été convoqué par Moscou vendredi en réaction aux accusations de projets de sabotage visant des infrastructures européennes et nord-américaines. Le Kremlin nie être à l’origine de cette vague d’attaques contre les alliés de l’Ukraine.
Le chef adjoint de la mission diplomatique canadienne à Moscou "a été informé que ces conjectures […] témoignent de la préparation probable d'une grossière provocation antirusse", a indiqué le ministère russe des Affaires étrangères dans un communiqué.
Il s'est vu remettre une note de protestation concernant "de fausses accusations sur un prétendu ''sabotage russe'' planifié contre des pays de l'OTAN, impliquant l'envoi, y compris à des destinataires au Canada, d'explosifs par correspondance postale", a ajouté le ministère.
flanker (./12586) :Heureusement
on pourra difficilement te reprocher d'avoir suivi des recommandations.
Zerosquare (./12580) :Ça se confirme :
Peut-être. Mais ça peut être aussi un raisonnement plus basique : ils ont de lourdes pertes, donc tous les postes qui ne créent pas directement de profits sont sur la sellette.
Et la partie pour Flan :Employees across Boeing face sweeping layoffs this weekThe Seattle TimesBoeing plans to cut 10% of its workforce. Employees learn their fate Wednesday. Non-frontline workers are targeted, though engineering and production won't be exempt.
On an earnings call late last month, new Boeing CEO Kelly Ortberg said that to “reset priorities and create a leaner, more focused organization,” a 10% workforce cut would target overhead and “nonessential” positions, not front-line workers designing and building airplanes.
“We’re going to really focus this workforce reduction in streamlining those overhead activities, consolidating things that can be consolidated,” he said.
“I wouldn’t think of it like we’re going to take people off production or out of the engineering labs,” Ortberg added. “That’s not our intent.”
But a Boeing senior engineering manager in St. Louis said the cuts in the works target a roughly 10% reduction across the engineers supporting military programs, including the F-15 and F/A-18 jet fighters and the Navy’s P-8 submarine hunter, which is built in Renton with military systems installed in Seattle.
Those engineering organizations will shrink, said the manager, who asked not to be identified to protect his job. “If the idea in Kelly’s mind is cutting overhead and programs will not be impacted, that’s not what’s happening.”
An Airbus A380 operated by Australian airline Qantas clocked over 290 hours of flight time despite a tool having been left inside one of its engines, according to a report from the Australian Transport Safety Bureau.
The 1.25 metre nylon rod, a "turning tool", was used during an inspection of the left outer engine's intermediate-pressure compressor on December 6 of last year, during a three-day routine maintenance check at Los Angeles Airport (LAX).
It was left in the engine by a maintenance worker who departed his shift early for medical reasons. The worker was told to leave it in place, as it was still in use, and assumed a colleague would ensure the tool was removed.
Over the course of the three-day inspection period, multiple engineers rotated shifts. It was noted that the tool had not been returned after being checked out. Maintenance crews did search for the tool, but it wasn’t found during two inspections – first because it was dark and an engineer didn't use a flashlight, and the second time because the inlet cowl where it sat was not examined.
According to the Safety Bureau report, at least some of the engineers didn't even realize what part they were looking for and thought the missing tool was a larger gearbox turning tool. If it had been the gearbox tool, it would have been reasonable to assume it would be more visible inside the engine.
Within this assessment, the red team (also referred to as ‘the team’) gained initial access through a web shell left from a third party’s previous security assessment. The red team proceeded to move through the demilitarized zone (DMZ) and into the network to fully compromise the organization’s domain and several sensitive business system (SBS) targets. The assessed organization discovered evidence of the red team’s initial activity but failed to act promptly regarding the malicious network traffic through its DMZ or challenge much of the red team’s presence in the organization’s Windows environment.
The red team was able to compromise the domain and SBSs of the organization as it lacked sufficient controls to detect and respond to their activities. The red team’s findings illuminate lessons learned for network defenders and software manufacturers about how to respond to and reduce risk.