33,811 results · Most relevant
Coach Kyle instructs engaging everyone in the group — family and friends — running a full-blown interaction rather than a quick opener, and acknowledging the group quickly so you don't come off as a creepy stalker hitting on one girl.
Coach Kyle lays out a locally coherent method for approaching a woman who is with her family or friends: smile and talk confidently, engage everyone in the group with an easy conversation topic they can respond to, show calm confidence and warmth, then pivot back to the woman one-on-one, staying in the conversation with teasing and flirtation for a 5-10 minute interaction to get a solid number.
The speaker recommends enforcing tenant isolation as hard as possible — thinking at the AWS-account/GCP-project level — tightly scoping workload identity to the tenant domain, and checking the tenant on every query, so shared databases cannot leak data across tenants.
Andrey Rybka recommends using workload identity that is tightly scoped with an audit trail and ideally a circuit breaker, so that if a breach happens, the circuit breaker trips and nothing gets exfiltrated. He also suggests thinking about agents' token credentials and when they expire.
Andrey Rybka recommends giving each agent its own identity with short-lived, scoped credentials and no shared keys, and killing any long-lived keys in favor of tightly scoped, short-lived, audience-bound tokens.
The speaker's rule of two for agent security: an agent may combine any two of untrusted input, sensitive data, and external action, but if all three are needed, human sign-off is required. He frames this as the priority to start with today.
Andrey Rybka recommends putting circuit breakers on anything catastrophic, human approval for any high-value actions, scoped credentials limited to intended actions, and tenant isolation.
Andrey Rybka recommends locking down agents using the rule of two: every tool call goes through a deterministic broker, and humans sign off for any high-value actions.
Andrey Rybka recommends sandboxing the environment the agent runs in, setting default deny for outbound network traffic including DNS, and placing egress controls outside the sandbox. He stresses that default deny means everything, including DNS, and that a sandbox with no web access still needs DNS blocked because data can be smuggled through DNS lookups.
The speaker recommends killing any long-lived keys and replacing them with tight-scoped, short-lived, audience-bound tokens, one per agent, scoped to the tenant domain. This limits what a hijacked or social-engineered agent can access.
Andrey Rybka recommends that tools should not be able to wipe anything — use least-privileged tools, and when an agent has access to tools that can wipe or destroy data, remove those tools entirely rather than relying on prompts.
The speaker recommends implementing a deterministic invocation broker for tool calls: every tool call goes through the broker, with human approval for high-value actions and hard rate limits and budgets that halt agent actions rather than just alerting.
Andrey Rybka recommends implementing hard tenant isolation as strict as AWS accounts or GCP projects, with workload identity tightly scoped to the domain, data provenance tagging, and an audit trail. He also advises checking the tenant on every data query.
The speaker recommends pairing sandboxed runtimes with default-deny egress for all outbound traffic including DNS, and adding provenance tagging, output filtering, and circuit breakers. Egress controls should sit outside the sandbox, and a formal runtime is preferred.
Andrey Rybka recommends using deterministic controls outside the model, checking every call, and keeping a kill switch for agents. He also notes that governance prompts must be enforced by deterministic code.
Andrey Rybka recommends implementing agent-to-agent mutual authentication because low-privileged agents should not be able to talk to higher-privileged agents, and using scoped credentials, least-privileged tools, and an audit trail for agent-to-agent interactions.
The speaker recommends circuit breakers on anything catastrophic-capable, wired into credential and egress paths so that when an agent breach occurs, a tripped breaker prevents exfiltration. He also recommends maintaining an audit trail and keeping guardrails outside the model.
Andrey Rybka recommends using a deterministic invocation broker and human approval for high-value actions like token transfers, noting that even a $5 transfer threshold is probably too much to allow without human approval.
Andrey Rybka recommends using supply chain verification, delaying ingestion of new packages on some mergers, and scoped credentials. He elaborates: don't just do supply chain verification; also delay ingestion — don't ingest every package on day zero, maybe wait a week or two.
Andrey Rybka recommends using injection protection, isolation, data separated from instructions, provenance tagging for all data, egress controls, and output filtering to defend against prompt injection and data exfiltration.
Choose sources → to get a library of your own and a daily brief.