Author: l0cknsec

  • Binance Hack: $6.3B Loss Reveals Security Gaps

    Binance Hack: $6.3B Loss Reveals Security Gaps

    The Binance hack affected $6.3 billion worth of digital assets, drawing attention as the largest security incident involving a cryptocurrency exchange in history. The exchange initially did not disclose that a compromised engineer laptop was the starting point of the incident, but its acknowledgment that additional entry points had been identified made it difficult to explain the full sequence of the attack through the initial account alone.

    $6.3B in Losses: Tracking Must Continue After Asset Freezes

    Binance said it had frozen roughly half of the affected assets. Nevertheless, the attacker still holds a significant amount of stolen assets, and the company said it would compensate all losses. The freezes do not necessarily mean that the attack has been contained or that the underlying infrastructure for withdrawals has been blocked. Instead, it shows that the process of tracing where the funds moved remains unfinished.

    Tether and Circle said they had frozen a combined total of approximately $2.4 billion in assets in response to the incident. World Liberty Financial said it was working with partners to freeze the stolen assets. Coinbase said it had not been affected by the incident and was monitoring the situation.

    A Multi-Stage Attack From Laptop to Withdrawal Environment

    Binance co-CEO Richard Teng said the initial investigation found that the attack began on a compromised engineer laptop. He explained that the attacker used the laptop to access service containers and submit unauthorized withdrawal transactions.

    The attack was not a simple, one-time click carried out using a single engineer’s credentials. Teng emphasized that it involved a complex, multi-stage attack and said no evidence of a wallet private-key compromise had been found as of the latest update. Jayant Dave of Check Point pointed to similarities with the recent Bitget hack, analyzing that attackers may target the systems and people authorized to use vault keys rather than the keys themselves.

    This structure reveals why the operational environment cannot be considered secure based solely on the safety of private keys. If the process for creating, approving, and executing withdrawal requests is concentrated in a single account or piece of credential information, an attacker who gains control of those privileges could cause widespread losses. To limit the potential scope of an internal breach, organizations must verify that laptop endpoints, administrative privileges, service containers, and the withdrawal approval system are not connected through a single attack path.

    Analysis and Official Positions Diverge Over a TraderTraitor Link

    Check Point and TRM Labs analyzed the attack as connected to the activities of TraderTraitor, a hacking group linked to North Korea. Check Point described the group as also being known in the industry as the Lazarus Group, the organization widely blamed for the 2025 Bybit hack. TRM Labs likewise reported that the incident shared several similarities with previous North Korea-linked cases, including the Bybit hack.

    Chainalysis also assessed with high confidence that a North Korea-linked organization was involved in this hack. Ari Redbord, global head of policy at CipherTrace, characterized the Binance hack as a turning point the industry had not previously seen. Binance, however, has not officially identified the perpetrators and said it is working with law enforcement to determine who was responsible and bring them to justice.

    Withdrawal Suspension and the Remaining Post-Incident Challenges

    Binance suspended withdrawals until it could verify the security environment. Co-CEO Yi He explained that the decision to suspend withdrawals was made because safety had to come first. The suspension is currently an available defense against further damage, but it must lead to verification that the entry points are genuine and proof that the incident cannot recur.

    Binance said it plans to release a detailed post-incident review once the investigation is complete. In the meantime, the company has said it is continuing to gather facts and will share more specific information immediately as it is discovered. The core of strengthening exchange security lies in distributing withdrawal privileges, continuously detecting anomalous activity across operational environments, and rechecking the intrusion path after an attack. The $6.3 billion hack will remain a stark example of how a combined path linking operational privileges with the execution environment can cause damage on a much broader scale than private-key exposure alone.

    Source Note

    This article was written with reference to the following source: BBC Tech — Crypto giant Binance hit by $6.3bn hack suspected to be largest in history

  • Waymo and Toyota Expand Robotaxi Plans to Japan and UK

    Waymo and Toyota Expand Robotaxi Plans to Japan and UK

    Waymo has formalized its cooperation with Toyota on autonomous vehicle supply and system integration. Under the Waymo-Toyota partnership, the companies plan to test vehicles featuring Waymo’s autonomous driving system in the 2027 Toyota bZ4X in Japan, with robotaxi services in Japan and the United Kingdom planned for the future.

    Manufacturing and Autonomous Driving System Integration

    Toyota will manufacture the 2027 bZ4X at its Takaoka plant in Japan and integrate Waymo’s autonomous driving system. The electric vehicle is known as the BZ in the North American market, and Waymo plans to test it first in Japan before deploying it in Japan and the United Kingdom.

    The announcement follows a preliminary agreement between the two companies, signed about 18 months ago, to explore the development and deployment of an autonomous vehicle platform. Although much of the scope remained undefined at the time, the current Waymo-Toyota partnership is closer to a vehicle supply agreement focused on manufacturing and system integration, along with clearly defined roles for supplying vehicles in specific regions.

    Expansion into Right-Hand-Traffic Markets Including the UK

    Waymo and Toyota are considering deploying the bZ4X in other right-hand-traffic countries, including the United Kingdom, after conducting initial tests in Japan. Waymo is already testing autonomous Jaguar I-Pace vehicles in London and plans to launch a robotaxi service if it obtains the necessary permits.

    Further details can be found in the original report.

    Partnership Scope Extending to Personal Vehicles and Transportation Infrastructure

    The companies are also continuing to explore applying Waymo’s autonomous driving technology to privately owned Toyota vehicles. Separately, they are discussing initiatives to improve safety for other road users by applying insights gained through Waymo’s real-world operations, while Toyota has outlined an approach to improving road safety by connecting vehicles with transportation infrastructure.

    The key development is that the Waymo-Toyota partnership could extend beyond supplying vehicles for robotaxis to improving the safety of personal Toyota vehicles and road infrastructure. How thoroughly the technology integration is validated as the Japan trials and UK service launch progress toward commercial operations will be a key issue to watch.

    Source

    This article was prepared with reference to the following original source: TechCrunch — Waymo taps Toyota to supply robotaxis for Japan and the U.K.

  • Design EC2 and RDS Auto-Stop With Instant Recovery

    Design EC2 and RDS Auto-Stop With Instant Recovery

    Manually shutting down instances and RDS resources one by one in the console when they are running overnight but no one is using them will eventually create a gap. When the responsible person is on vacation or handling an incident, shutdown tasks can be missed, leaving only an assumption that everything is in a normal state the next day. AWS cost optimization goes beyond saving money; it requires designing operational rules that ensure resources return immediately when needed.

    The problem is the misconception that automation must be handed over to the next generation. A script that reads tags to find resources may fail or miss targets when tag names change, and an RDS instance stopped on a schedule may automatically start again after seven days. If developers need an instance that was stopped in the evening right away, the productivity loss from recovery delays will outweigh the savings. The starting point of the design should therefore not be “which resources should be stopped,” but rather “what should be stopped and when, who can wake it up immediately, and how will discrepancies in state be detected.”

    Separate Automatic Shutdowns From Scheduled Restarts

    The source mentions AWS Instance Scheduler as an automatic shutdown option for small teams. However, its specific configuration and operational impact have not been made public. The mere existence of a schedule does not complete the operational design. Scheduling times, development environment usage periods, emergency recovery paths, and schedule validation are separate concerns. For small teams, it is safer to first select resources that can be stopped without disrupting business and exclude the rest from automatic shutdowns.

    The source also mentions Cron and Lambda scripts as automation options for small teams. Although the specific implementation has not been disclosed, using tag conditions to query resources is vulnerable to minor changes if tags are the only identifier in a policy. Without a process for detecting mistakes made by people modifying tags, Lambda can remain in a successful state while doing nothing for an extended period.

    Tags should therefore be used only as the starting point for discovery, with actual eligibility checked again against the environment list and a predefined allowlist. When combining automatic shutdowns with manually maintained resources, it is safer to use the AWS CLI resource query commands to verify the target list first and then run the shutdown command as a separate step. As shown in the example below, separating discovery from execution helps prevent commands from being applied to many resources without review.

    # ※ Note: The following configuration and code are conceptual simulation examples (Illustrative Example, not official spec) to aid understanding.
    aws ec2 describe-instances \
     --filters "Name=tag:AutoStop,Values=true" \
     --query "Reservations[].Instances[].InstanceId" \
     --output text
    
    aws rds describe-db-instances \
     --query "DBInstances[].[DBInstanceIdentifier,DBInstanceStatus]" \
     --output table

    After confirming whether the query results match the expected targets, apply the instance stop command to EC2 and the scheduled stop command to RDS. Immediately after running the commands, query the actual status again to verify that the resources have stopped. Relying only on a successful command message can delay the discovery of schedule permission or target selection errors. The recovery path should be validated separately in the same way.

    Build an Operational System That Handles Tag Changes and RDS Scheduled Restarts

    Tag-based management is useful for creating resource groups, but the source also points out its vulnerability to name changes. Rather than stopping after establishing a standard naming convention, teams should connect tag-change alerts with periodic reviews of the target list. These reviews should verify not only whether the resources found by automation are empty, but also whether resources that must be maintained manually have been mixed into the automatic shutdown list because of their tags.

    For RDS, teams should periodically verify that the stopped state is being maintained and manage both the time at which the seven-day automatic start schedule should be reset and the permissions required to perform that reset. It is better to assign this reset task to a scheduled automated check than to rely on a procedure people must remember. The check should confirm not only the stopped state, but also whether the instance restarted and whether any schedules failed, and then send an alert.

    A Recovery Path for When Developers Need Resources Immediately

    When a development environment stopped overnight is needed, teams should not simply wait for the scheduled start. They should clearly document an immediate startup procedure in operational documentation and make it accessible through the team’s channels. Defining the recovery targets and permissions in advance reduces the likelihood that automatic cost savings will slow down development. Conversely, if a resource that requires recovery should be excluded from automatic shutdowns, that exception should also be verified in both the tags and the execution list.

    Validation does not end with a single successful test. Teams should separately confirm the startup immediately after a scheduled start, continued operation after the scheduled period, missing targets after tags change, and failed recovery commands. This process is the key to turning AWS cost optimization automation into a real operational system. Recovery time and reliability should be verified before cost savings are expanded, and the scope of scheduled operations can then be broadened based on the results.

    Trying to automate every resource from the beginning can place a heavy maintenance burden on a small team. Resources with different usage patterns, such as shared development environments, reproducible test environments, and one-off validation environments, should be separated, with automation beginning with the targets least likely to cause disruption. Once a procedure for confirming the actual state after automatic shutdowns is established, teams can manage cost savings and recovery reliability within the same operational routine.

    This issue originated from a source discussion asking how small teams manage idle development and test EC2 and RDS resources. The key is not choosing one tool among AWS Instance Scheduler, Cron and Lambda, or tag-based management, but combining scheduling, execution, validation, and exception handling into a single flow. Automatic shutdown is only one step in that flow, and cost optimization automation is complete only when resources can be recovered with certainty whenever they are needed.

    What to Try Now

    • Query the list of currently running development and test EC2 and RDS resources, and distinguish automatic shutdown candidates from resources that must be maintained manually.
    • Standardize tag names and shutdown policies, then connect tag changes to alerts that revalidate the target list.
    • Create stop and start schedules in Instance Scheduler, then confirm the actual state immediately after each scheduled operation.
    • Check that RDS scheduled shutdowns are being maintained, and register an automated inspection that resets the schedule if it expires.
    • Document the recovery command and permissions developers need for immediate startup, and test an actual recovery.

    Source

    This article was written after reviewing the following source: r/aws — How do small teams handle dev/test EC2 and RDS sitting idle overnight?

  • Context Engineering for Agents: Strategic Forgetting

    Context Engineering for Agents: Strategic Forgetting

    Reduced to a single sentence, the factor that determines the performance of an AI agent is closer to context engineering than the model itself: selecting and delivering the information needed for the current goal. Dividing responsibilities between deterministic code and probabilistic models, and periodically discarding outdated state, are emerging as alternatives that compensate for the limitations of long context.

    Four Failures Created by Long Context

    Long context windows hold not only more information, but also hallucinations, incorrect facts, and conflicting examples. The resulting failures include context contamination, in which the model fixates on incorrect information; attention dilution caused by excessive focus on the context; confusion, in which facts unrelated to the current problem influence the answer; and context collisions, where tools and skills unexpectedly conflict.

    In Gemini 2.5’s Pokémon playing experiment, older game rules and newer tasks were presented together, causing the model to pursue outdated goals for several hours. According to an appendix in a technical report, once the context considerably exceeded 100,000 tokens, the model began repeating past actions instead of creating a new plan.

    In Carolina Camassa and Derek Shiller’s “Do as I Say, Not as I Do” experiment, adherence to original instructions declined across every tested model as the number of conversational examples conflicting with new instructions increased. Gemma 3 12B dropped to less than half its compliance rate with only a few conflicting examples, and Opus 4.6 showed the same problem as examples accumulated.

    Six Techniques for Context Management, from Augmentation to Summarization

    Context management includes enriching information with RAG and skills, as well as selecting tools to expose only those suited to a request, preventing overload. One company loaded 600 skills for each engineer whenever a software project began, causing an abrupt decline in performance and making tool filtering necessary. Context isolation starts subagents and peer agents with an empty conversation history, separating information and goals from other tasks.

    Other techniques include pruning outdated history, external storage that keeps information in Markdown files or databases, and summarization, which condenses older conversations to begin a new context. Claude Code and Codex also removed tool results that had become unnecessary during the initial stages of context compression. In practice, evaluating relevance first and then reducing history before summarizing can produce more useful compression results.

    Moving Context Construction into the Harness

    Context engineering evolved from prompts that dynamically assemble system context into harness engineering, which moves processing into code outside the context. A DSPy demonstration combined a ReAct module and Python function tools in a while loop to accumulate conversation history.

    Tool selection used the large model Claude Sonnet 4.5 together with the smaller judgment model Jev. Jev evaluates requests and tools, selects the necessary tool set, isolates subagents, and reviews each conversation turn to remove unnecessary history. The change that incorporated these four improvements into a single loop was introduced in roughly 16 lines.

    Failures in Long-Running Tasks and Strategic Forgetting

    Long-running task models have introduced new problems: a “fight with the weights,” where learned behavior conflicts with current instructions, and “context inertia,” in which the model continues pursuing hypotheses and subgoals that should be abandoned. Claude Code’s system prompt and tool instructions repeatedly requested parallel execution of independent tool calls, revealing a behavioral bias in the Learning environment.

    The Memento harness used in Anthropic’s self-replication research mitigated fixation by writing brief notes and clearing the context every 90 minutes. It preserved the environment and task results while discarding the ongoing conversation, allowing the agent to restart from a new perspective. Microsoft Research’s Fork-and-Flush addressed the problem of exploration stalling after major improvements, while UC Berkeley’s Scaling Discovery Requires Forgetting, led by Shangyin Tan, reported that performance rose again when the context was periodically cleared while retaining outputs.

    For personal agents, memories and skills accumulate over time, and conflicting instructions are likely to become a new operational challenge. During six months of operating Hermes, unusual modifications accumulated in skills and could worsen problem-solving behavior; a general-purpose agent also faced conflicts between memories and instructions as it solved the same problem in different ways. Existing techniques such as isolation, external storage, and deleting accumulated history remain the available responses. The quality of an agent harness depends less on the size of the context window than on how precisely it automates goal-oriented information selection and strategic forgetting.

    This shift can be observed in material on the current state of context engineering. Teams designing long-running agents must consider not only prompt length, but also what to retain in the context and when to clear it.

    Original Source

    This article was prepared after reviewing the following original source: geeknews — The Current State of Context Engineering

  • Nvidia Explores $2,000-per-GPU Subscriptions for AI Agents

    Nvidia Explores $2,000-per-GPU Subscriptions for AI Agents

    Nvidia has outlined a plan to offer software for running AI agents at about $2,000 per GPU annually, introducing a new direction for Nvidia subscriptions. Nvidia CEO Jensen Huang discussed the potential of a software licensing business that could generate recurring revenue beyond hardware sales at a GTC event held in Berlin, Germany, on October 22, 2026.

    The core of the proposal is the total cost of operating all the Nvidia software required to run agents in an AI factory. It is a strategy to bundle security, access management, and infrastructure operations into a single platform, extending Nvidia’s hardware-focused revenue model into a subscription-based structure.

    The $2,000 Figure Is Not a Final Product Price

    The announced $2,000 figure appears to be an example offered to explain the licensing model rather than a confirmed selling price. Nvidia has not disclosed when the pricing would take effect, the specific software configuration, or the licensing terms. It also remains unclear how the offering would be distinguished from existing products.

    Nvidia’s enterprise AI software platform, AI Enterprise, is currently sold for $4,500 per GPU annually. It is unclear whether the newly mentioned amount covers a narrower agent-specific package or represents a separate licensing system, making it difficult to interpret the figure as a price reduction for existing offerings.

    The Scale of Recurring Revenue and Its Unconfirmed Assumptions

    If subscriptions are introduced on a large scale, they could generate recurring revenue independent of GPU sales cycles, which is the primary commercial value of Nvidia subscriptions. If five million GPUs are covered by paid licenses, the annual revenue would amount to $10 billion, or $50 billion cumulatively if the subscriptions are maintained for five years.

    However, these figures do not represent an actual revenue forecast. Nvidia has not disclosed the number of GPUs eligible for paid licenses or provided a revenue outlook, so the five-million-GPU and five-year figures should be understood as a hypothetical scenario. It is therefore difficult to determine the size of the market based solely on the $2,000 announcement.

    OpenShell and Sentry-Managed Agent Security

    AI agents can access external tools and data and autonomously perform multiple tasks, so large-scale deployment in enterprise environments requires a management system capable of controlling their execution scope and permissions. On October 21, 2026, Nvidia unveiled an open-shell reference architecture that supports isolating AI agent execution environments and restricting access.

    OpenShell is based on Vera Rubin computing infrastructure, the Vera CPU, and the BlueField-4 data processing unit, and it monitors agent activity through Nvidia Sentry. Sentry can isolate agents that attempt to cross configured security boundaries. The key is that control is implemented at the infrastructure layer rather than relying solely on the model’s built-in safeguards.

    Integration with external companies is also beginning. Anthropic is working to integrate OpenShell and BlueField hardware with managed Claude agents to manage access permissions for enterprise agents, while Salesforce is developing administrative capabilities for reviewing agents’ access requests in Slack and approving or rejecting them. These examples show that the security management layer can be applied to real services rather than remaining merely a reference design. A related report from The AI Times also highlighted Nvidia’s subscription expansion and its broader ecosystem impact.

    From Hardware to Full Stack, With Lock-In Risks Remaining

    Nvidia CEO Jensen Huang said people may eventually stop viewing Nvidia as merely a chip company. His remarks emphasized Nvidia’s direction of providing a technology stack that includes software and systems, alongside semiconductors, to industries ranging from healthcare and automotive to telecommunications and life sciences.

    As enterprises build security and management systems on Nvidia’s infrastructure, the cost and effort required to migrate to another platform may increase. Recurring revenue and high switching costs are both advantages of Nvidia subscriptions and factors that could accelerate ecosystem lock-in. As the AI agent market expands, the value of the security layer will also grow. However, a meaningful evaluation of Nvidia’s business plan will require clarity on the rollout timeline, eligible GPUs, included software, licensing units and terms, and whether the offering overlaps with AI Enterprise.

    Source Article

    This article was written with reference to the following original source: The AI Times — Nvidia Considers $2,000 Annual Software Subscription per GPU…Accelerating Ecosystem ‘Lock-In’

  • Control Where AI Training Data Is Stored and Used

    Control Where AI Training Data Is Stored and Used

    The biggest misconception in enterprises adopting external generative AI is treating whether input data is “stored” and whether it is “used for training” as the same issue. These two processes involve different security risks and control mechanisms. Once AI training data is incorporated into a model, it may not be possible to completely eliminate the risk of unintended exposure even after the original data is deleted.

    To address this, companies should not stop at reading a service’s terms of use. They must also verify whether data is used for training and the scope of its storage, logging, and deletion through contracts, technical configurations, and policy settings.

    Storage and Training Carry Different Risks

    Stored data may be exposed through breaches or unauthorized access by third parties. However, enterprise AI services generally provide some degree of control over access scope, retention periods, and deletion policies through contractual terms and administrative settings. Training creates a different kind of risk. Once data has been incorporated into the training process, deleting the original data may not fully reverse its influence, and there may still be a possibility that sensitive or confidential information could surface through future outputs or internal representations.

    The central question therefore goes beyond simply asking whether data is stored. It must also ask whether contracts and configurations can confirm that stored data will not be used to train the model.

    Major Services Have Different Data Handling Policies

    For consumer services, the scope of data use can be misunderstood based on feature names alone. When ChatGPT’s “Improve the model for everyone” setting is enabled, conversations involving research, work, or personal data may be used to improve and train the model. Claude Free, Pro, and Max allow users to choose whether their data is used during the signup and usage processes. However, the opt-out setting is checked by default, so conversations and coding sessions may be used to improve the model unless users change it. Gemini manages related data use through its “Keep Activity” setting.

    Service Relevant setting or method Data use risk to verify
    ChatGPT “Improve the model for everyone” Conversations may be used to improve and train the model unless this setting is disabled
    Claude Opt-out method enabled by default Conversations and coding sessions may be used to improve the model unless users change the setting
    Gemini “Keep Activity” Data use is managed through the activity retention setting

    Even when a company pays for employees’ personal subscriptions, it does not automatically gain control over those accounts. If work information is entered without separate security controls, the company’s internal data may be transmitted to and stored by the provider, and it may be used for training in accordance with the service’s policies.

    Verify Contracts and Settings Before Deployment

    Enterprises should ensure that internal data is not used to train or improve models in external services. They should not overlook storage risks simply because training has been prohibited. The preferred storage method is ZDR, or Zero Data Retention. ZDR is described as a policy or contractual condition that prohibits the retention or separate logging of prompts, images, and other content beyond what is necessary to process requests, and also prevents their use for model training.

    However, ZDR is not available by default across all services and pricing plans, and it is often offered only on a limited basis even under the top-tier Enterprise contract. Operational reviews should verify not only whether training is prohibited, but also whether data is actually stored, the retention period, the scope of log management, and the deletion policy.

    RAG Security Must Follow the Entire Data Flow

    Even in a retrieval-augmented generation (RAG) environment, using internal tenants or dedicated accounts does not eliminate all risks. Organizations should review encryption, storage region, filtering of personal and sensitive information, retention and deletion policies, SLAs, access permissions, and whether personal information is transferred outside the country.

    If internal documents are transmitted to a vector database or an external AI service, the storage location, authorized access, and deletion timeline must be managed across the entire data flow. The starting point for enterprise AI security goes beyond determining whether input data is stored. It requires verifying, through contracts and configurations, the scope and purposes for which AI training data remains. Boan News’ original analysis also illuminates this control framework.

    Source Article

    This article was prepared after reviewing the following original source: Boan News — Debating Information and Communications Technology Security: Misconceptions and Truths About AI Training, Part 50

  • AI Financial Payoff Remains Unclear at Non-Tech Giants

    AI Financial Payoff Remains Unclear at Non-Tech Giants

    TechCrunch reported, based on an analysis by Apollo Global Management’s chief economist Torsten Slok, that the financial payoff from AI has yet to emerge at large non-tech companies. Slok examined 493 S&P 500 companies, or the S&P 493, excluding Alphabet, Amazon, Apple, Meta, Microsoft, Nvidia, and Tesla. The analysis focused on whether large-scale AI investment and hype have translated into actual productivity gains.

    Margins and Revenue per Employee Remain Flat

    The margins and revenue per employee of the companies analyzed were largely flat, with no evidence that AI had improved productivity. Slok expressed skepticism about the argument that increasingly affordable intelligence can be linked to higher revenue growth and margins. This appears to mean that adopting AI alone does not establish that AI investments have produced financial gains.

    Slok’s Judgment Matters More Than the Numbers

    Slok said that while AI can be an excellent calculation tool, intelligence in businesses is primarily about judgment. AI lacks an understanding of responsibility, trust, culture, implicit rules, ethical trade-offs, and fairness, all of which affect reputational risk, revenue growth, and margins.

    When assessing the effects of AI investment, companies should examine productivity changes by role, revenue per employee, revenue growth, and margin improvements alongside the scope of tool adoption. The financial payoff from AI is better verified by whether it is reflected in actual profits and operational efficiency than by investment size or the number of use cases.

    The available information, however, is based on a single analysis interpreted by Slok and does not include comparisons of the indicators with operational data by role. Rather than expanding the findings into a general conclusion for every industry, the analysis is best used as a starting point for evaluating the profitability of AI investments at non-tech companies.

    For a detailed analysis, see TechCrunch’s report on the Apollo economist.

    Source

    This article was written after reviewing the following source: TechCrunch — AI delivers ‘zero financial payoff’ to most companies, Apollo economist says

  • Enforcing SAST and DAST Across Every Team Pipeline

    Enforcing SAST and DAST Across Every Team Pipeline

    The original post asked how to enforce SAST and DAST scans when each engineering team maintains its own CI/CD pipeline. In a custom pipeline environment, tool versions, scan targets, failure criteria, and exception conditions may vary. Without shared execution criteria like these, security testing enforcement risks depending on tool-specific execution rates or individual teams’ cooperation.

    The original post was published as a question about how to ensure Snyk, Trivy, IaC, and other scans run within team pipelines. The author wrote in the software section that GitHub’s enforcement features alone are not sufficient. Controlling repositories through configuration alone makes it difficult to prevent manually modified pipelines, bypassed deployments, and unverified exceptions. One approach is to connect organizational policies to a shared execution path and deployment approval structure.

    First, define security testing enforcement criteria as policy

    The first decision is not whether to block every vulnerability immediately, but which changes require which scans and which results should prevent deployment. Define the repositories in scope, deployment artifacts, IaC and dependency scan coverage, environments subject to DAST, approval authorities, and exception expiration conditions in a version-controlled policy file. This file should undergo code review alongside application code and retain a record of changes.

    Decisions should not rely on severity alone. They should also account for asset criticality, potential internet exposure, remediation difficulty, and active exceptions. A reasonable starting point is to block high-risk vulnerabilities and warn on medium-risk findings, but manage the criteria as enforceable policy rather than documentation to prevent teams from disabling scans or accumulating excessive exceptions. Immediately failing the pipeline for every vulnerability creates excessive operational strain and eventually leads to workarounds.

    A shared pipeline should do more than invoke scans

    A shared pipeline module centrally manages tool versions, scan configuration, result uploads, policy evaluation, and failure decisions. Team pipelines provide only the minimum repository-specific configuration and invoke the shared stages. In an environment that uses Trivy, for example, the scan results can be passed into policy evaluation as follows.

    trivy image --format sarif --output trivy-results.sarif IMAGE_NAME
    

    ※ Note: The following is a conceptual simulation example (Illustrative Example, not official spec).
    It must be adjusted to match the actual image reference and execution environment.

    The shared module should preserve metadata beyond execution logs, including the target commit, tool version, policy version, results, decision, and exception identifier. Without this information, it is impossible to determine after the fact which scans a specific deployment passed. Merely confirming that a results dashboard exists does not establish whether enforcement is in place.

    Separate deployment gates from pipelines

    If scans run only inside a team-owned pipeline, security stages may be removed when the pipeline changes. A safer architecture uses an independent deployment gate. Link scan status, policy version, and exception expiration status to deployment requests and artifacts, and prevent approval or promotion whenever the required status is missing or a policy violation exists.

    In this architecture, security testing enforcement is determined by whether an artifact is eligible for deployment promotion, rather than by whether a pipeline execution succeeded. A central service verifies that the scans were executed by the pipeline, that the target commit and artifact match, and that the policy used for the decision remains valid. Even when a pipeline changes, artifacts that skipped testing cannot automatically move into a deployment environment.

    Run SAST and DAST differently within the same gate

    SAST, dependency scans, and IaC scans can target code and configuration, but DAST requires a running application. DAST needs an isolated test environment, credentials, test data, and execution-time management. Define target and network scopes to prevent arbitrary requests from reaching production, and normalize scan results into a shared result model.

    Share the common policy and approval system while separating the execution layer. Run static scans quickly on every commit, and perform dynamic scans in a deployable test environment once the application is ready. Because the two scan types have different characteristics, one may block the other before it finishes. The policy should therefore specify which stage is a prerequisite for the other.

    Treat exceptions as managed objects, not permanent bypasses

    A security exception is not something to fear; it is a temporary mitigation that can be controlled. Record the justification, owner, remediation deadline, applicable tools and scope, and exception identifier for every exception. Automatically transition expired exceptions to a blocked state and require reevaluation before expiration. Repeated use of the same exception identifies a tool configuration or shared pipeline that should be improved.

    Periodically review artifacts deployed without scans, bypasses of failed pipelines, expired exceptions, and repeated exceptions together. These metrics show the practical effectiveness of security testing enforcement more accurately than tool-specific execution rates. Policies, pipelines, deployment gates, and exception lifecycles must be integrated into one operating system to preserve standards even in uncooperative teams and mutable pipelines.

    This issue originates from the original discussion about CI/CD security enforcement, with its central concern being an architecture that guarantees execution across distributed development organizations rather than the tools themselves.

    What to try now

    • Inventory every repository and deployment pipeline currently in use, and mark gaps in SAST, DAST, and IaC scan coverage.
    • Manage a policy file in your repositories that defines scan targets, blocking criteria, approval authorities, and exception expiration dates.
    • Create a shared pipeline module that manages tool versions, result collection, and policy decisions, then connect one team to it.
    • Verify that artifacts without scan status or a policy version are blocked during the deployment promotion stage.
    • Record the justification, owner, expiration date, and scope of existing security exceptions, and classify repeated exceptions as candidates for improvement.

    Source

    This article was written after reviewing the following original source: r/devops — Enforcing SAST and DAST Tools at Enterprise Level

  • LLM Formal Verification: Claude Verifies 123 Libraries

    LLM Formal Verification: Claude Verifies 123 Libraries

    Anthropic and Theorem used Claude to formally verify 123 open-source libraries targeted by Google OSS-Fuzz, covering 239 fuzzing entry points at the binary level. After fixing the bugs, they expanded the verification to prove that the compiled code would not crash under specified execution environments and input-size conditions. This experiment demonstrated both the scale and reusability of LLM-based formal verification, while revealing that defining the boundaries of its guarantees remains a central issue.

    Turning Fuzz Tests into Code That Never Crashes

    Formal verification translates code into a mathematical model and demonstrates that it does not violate defined rules. Conventional tests check whether specific inputs pass or fail, but they do not guarantee that every code path will be explored, even when execution time is increased. This experiment transformed fuzz tests, which developers design to generate inputs that expose crashes, into a specification requiring that the code not crash with any input below 64MB.

    After compiling the libraries and fuzz tests as RISC-V executables, Theorem modeled the behavior of the actual binaries using its formalizations of RISC-V instructions and Linux process semantics. Claude was used to handle large-scale proofs covering the possible behavior and interactions of tens of thousands of instructions, while the Rocq code it produced allowed the kernel to check whether the specification had been satisfied. Using AddressSanitizer to expose invalid memory accesses as crashes provided the foundation for memory-safety specifications.

    Bugs Revealed at the Boundaries Missed by Fuzzing

    During the proof process, Claude immediately patched the bugs it found, regenerated the specifications, and continued its work, confirming hundreds of bugs. A counter underflow in decompression code caused an out-of-bounds write in a rare arrangement of inputs of approximately 20MB, while an out-of-bounds read in an image decoder required a 64MB input and more than 2GB of memory. In another library, an out-of-bounds read occurred only when two handles to the same file were used in a specific call order.

    Claude also rediscovered CVE-2026-56132 in libexpat, which required deeply nested inputs. Even in tasks that ultimately failed to produce a successful proof, the proof attempts helped identify bugs that required actual fixes. This shows that the failure of formal verification does not necessarily mean the conclusion must be discarded; instead, it can identify areas that require further investigation and patching.

    The Trust Boundary of Machine Checking and Proof Reuse

    The full proof consisted of approximately 180 million lines of Rocq code, far larger than the roughly 600,000 lines typically required for an ordinary proof. Although humans do not need to review every line of such a massive proof, its guarantees depend on the assumptions that the target is a single-threaded static binary and that it executes on a Linux system with a RISC-V CPU. It is still necessary to confirm that the formal models of RISC-V and Linux processes accurately reflect reality and that the statements of the proven theorems are correct.

    Because proof generation requires an enormous number of tokens, reducing costs also emerged as a central challenge. Across 36 small verification tasks created from OSS-Fuzz code, Opus 5.5 proved half of the tasks using approximately 40% fewer tokens than Opus 5. A shared workspace that allowed agents to copy one another’s proofs reduced token usage by 17% and enabled some tasks to succeed that had failed when attempted independently. Recursively combining common code with smaller proofs was presented as a key strategy for improving the scalability of LLM-based formal verification.

    Conditional Proofs Rather Than a Guarantee of No Bugs

    The verification target was a single-threaded static RISC-V binary linked with musl libc. Since real-world deployment environments generally use binaries dynamically linked with glibc on x86 or ARM, verification would require a system model closer to the deployment environment and accurate x86 semantics. ASan also fails to detect every memory-safety bug, and verifying every entry point does not guarantee the entire library, including code that is unreachable.

    Formally verified does not mean bug-free. A checker can determine only whether a formal specification has been satisfied; it cannot judge whether that specification accurately reflects reality. Problems outside the guarantees may remain if callers misuse public functions or if execution conditions not covered by the specification exist. The significance of this experiment does not lie in the claim that AI can provide complete and correct answers for all software. Instead, it lies in expanding machine-checkable guarantees to cover testable properties while making their scope and trust boundaries equally clear.

    The experiment’s summary and additional background can be found in coverage of LLM-based formal verification.

    Source

    This article was written based on the following source: geeknews — LLMs are making much larger-scale software formal verification possible

  • Chery Unveils Mobo Humanoid Robot for the Home

    Chery Unveils Mobo Humanoid Robot for the Home

    Chery Automobile, China’s largest automobile exporter, has unveiled the home humanoid robot Mobo for the first time. Standing 90 centimeters tall, Mobo handles medication reminders, English education, and caregiving tasks while remembering family members, marking an effort to apply the company’s accumulated artificial intelligence expertise and mass-production capabilities to home robots.

    From Medication Reminders to Long-Term Memory: Home Features Unveiled

    At an event, iMoo demonstrated Mobo’s caregiving and parenting functions, including talking with a grandmother to remind her to take her medication, playing hide-and-seek with a child, and teaching English and dancing. The company staged a scenario in which a robot enters a three-generation household to provide a more concrete picture of the product’s potential uses.

    Mobo distinguishes between people’s faces and remembers conversations and daily life information involving family members so that it can use them in subsequent conversations. It operates through voice commands and supports more than 20 languages, teaching English to children, reading fairy tales, and providing medication and schedule reminders for older adults. Data sent externally is designed to undergo anonymization and security checks inside the device.

    A “Dual Brain” Designed for Multiple Tasks and Unexpected Events

    iMoo Executive Vice President Zhang Peng said Mobo can process up to 16 tasks in parallel and respond to interrupted work situations within 0.2 seconds. In a demonstration, Mobo answered an unexpected question while handling meeting notifications and patrol duties, then resumed its previous tasks.

    iMoo employees explained that Mobo was designed not merely to react to human commands, but also to perceive its surroundings and independently plan multi-stage tasks. Its dual-brain structure combines long-term task planning with immediate responses to unexpected situations.

    Reusing the Automotive Supply Chain for Robot Manufacturing

    Chery highlighted that automobiles and robots can share camera- and sensor-based environmental perception, AI route decision-making, and voice recognition technologies. The company is pursuing a strategy of reducing manufacturing costs and establishing a mass-production system through joint purchasing and standardization of production practices for vehicle components.

    Chery is considering component sharing from the robot design stage onward and standardizing component specifications across product lines to expand joint purchasing volumes. Zhang Yuibing, Chery vice president and president of iMoo, said the company must apply automotive manufacturing cost-management principles to achieve mass production and profitable operations. Its technology organization is also being reorganized into an industrialization system that separates platform research from validation in real-world operating environments.

    Global Commercialization Still Faces Price and Launch Schedule Questions

    iMoo’s cumulative global robot sales have surpassed 3,000 units, while its products and services have entered more than 60 countries and regions and are being used in over 100 fields. After joining a pilot for a global robot leasing brand in Wuhu, the company plans to expand overseas.

    Mobo recognizes people and obstacles, adjusts its route, and slows down or yields when a person approaches. However, its official sales price and specific launch schedule have not yet been announced. Whether services that require memory and emotional interaction can take root in everyday life remains a challenge to be verified in terms of price, safety, and data management.

    Read Hankyung’s on-the-ground report for more on Chery Automobile’s transition into robotics and Mobo’s initial capabilities.

    Source Article

    This article was written after consulting the following source: Hankyung — “It’s time to take your medicine”… The special ‘helper’ who looks after Grandma [China Watch]