Your security team's work, in one place with the rest of the company.
TulipFarm is an AI workspace where security teams keep access reviews, vendor questionnaires, policies and the incident log. Agents help with recurring work, and other teams use the same records.
Public beta, open to everyone. Your first signup includes $50 in free credits.
No account needed. The tour runs in your browser and doesn't connect to your accounts.
Where security meets the other teams.
Security trades work with Engineering, HR, Operations and Finance. Each handoff stays in the same workspace, so the next team picks up the original record.
Coming in
EngineeringtoSecurity
Incidents
Engineering adds incidents to a shared Incident log table as they happen. Each row records the system, severity and owner, so your review starts from what Engineering wrote.
TulipFarm for engineering teamsBack to the mapHRtoSecurity
Joiners and leavers
HR keeps start and leave dates in a People table it shares with you. When Thistle prepares the access review, it can check who has left since the last one.
TulipFarm for HR and people teamsBack to the mapFinancetoSecurity
Vendor contracts
Finance keeps vendor contracts and invoices in a table it shares with you, so you can see which vendors the company still pays for when you plan the next reviews.
TulipFarm for finance teamsBack to the map
Going out
SecuritytoOperations
Vendor reviews
Keep each vendor's review status and next review date in a Vendors table you share with Operations. The completed questionnaire sits in Files next to the row.
TulipFarm for operations teamsBack to the map
The security work that comes back every quarter.
Records go in tables, policies and questionnaires in Files, and the recurring work to agents or workflows. Set a job up once in chat, and the next run and the next teammate start from there.
In these examples, Thistle is your team's security agent.
Access review checklists
When: Each quarter
Import each system's user export into an access review table, with system, owner, user and decision. Ask Thistle to mark users who appear on HR's leavers list, and approve each change before it's saved.
Vendor security questionnaires
When: Each vendor
Give each vendor review a project with the vendor's completed questionnaire and your notes. Save your vendor requirements as a skill and add it to Thistle, then ask it to list the answers that fall short. Someone on your team saves and turns on each skill.
Policy docs
When: Each update
Keep each policy in Files, where your team can find the current version. Ask chat to draft an update as a Word document in Files, or to propose a Google Doc that you approve before it's uploaded.
Incident log
When: Each incident
Log each incident in one table, with system, severity, owner, status and follow-ups. Set up a workflow in chat so that when an incident is marked Resolved, Thistle drafts a summary and Slack gets only the message you approved.
Security awareness reminders
When: Monthly
Schedule Thistle to run once a month. It reads your policies and drafts a short reminder for the company in a private task for you to review, then you post it where your company reads updates.
TulipFarm doesn't change anyone's access, and it has no built-in connection to identity providers or security tools. Your team imports the data it needs and makes access changes in the systems it uses today.
One incident, from Resolved to summary.
An example: Daniel, a security lead, wants a short summary in #engineering whenever a serious incident is resolved. Here's how the work moves and where he stays in charge.
What the workflow and run statuses mean
Saved
Daniel saved the workflow from chat. Nothing runs yet.
Activated
He turned it on. A change to an incident row can now start a run.
Run started
Engineering marked INC-14 Resolved, so a run began.
Completed
The run sent the approved summary to #engineering and finished. INC-14 stays in the Incident log with its follow-ups.
Set up a workflow: when a High or Critical incident in the Incident log is marked Resolved, have Thistle draft a summary for #engineering from the incident row and its follow-ups. Check with me before anything goes to Slack.
- Trigger
Engineering sets incident INC-14 to Resolved in the Incident log.
INC-14 set to Resolved - Condition
Checks whether INC-14 is High or Critical. If it's lower, the run stops here.
Passed: severity High - Agent
Thistle reads the incident row and its follow-ups.
Read row and follow-ups - Agent
Thistle drafts a short #engineering summary: what happened, what changed and which follow-ups are still open.
Draft ready - Review
The run pauses until Daniel reviews the draft and responds.
Daniel responded - Slack
Posts the summary to #engineering once Daniel approves the exact message. Nothing is sent before that.
Approved, sent to #engineering
Completed means the run finished its steps. Check the run history to see what each step did.
What stays when the review is done.
When someone leaves the team or a question comes up months later, nobody has to rebuild the record from memory.
- Records
- Access review checklists, the incident log and vendor rows stay in their tables.
- Context
- Policies and completed questionnaires stay in Files. Each vendor review's chats stay in its project.
- Decisions
- Workflow runs and approvals stay in run history, so you can see what was approved and what was sent.
- Procedures
- Skills, saved agents and workflows are ready for the next review cycle, so a new teammate starts with the same steps.
Questions from security teams
What is TulipFarm for security teams?
TulipFarm is an AI workspace where a security team keeps access review checklists, vendor questionnaires, policies and the incident log, with agents and workflows for the recurring parts. Engineering, HR, operations and finance work in the same workspace, so incidents, leave dates and vendor records can stay in one place instead of being copied between apps. TulipFarm Cloud is in public beta and open to everyone.
Where can I ask about TulipFarm's own security?
Contact us. This page is about how security teams can use TulipFarm for their own work, not about how TulipFarm protects its service. Use the contact page to ask how TulipFarm handles workspace data or to report a security issue.
Does TulipFarm replace my security tools?
No. TulipFarm isn't built to replace your identity provider, scanners, SIEM or GRC platform. It holds the work around them: checklists, questionnaires, policies, the incident log and handoffs to other teams. You can start with one recurring job, such as the quarterly access review.
Can TulipFarm change user access or read from my identity provider?
No. TulipFarm doesn't change access in other systems, and it has no built-in connection to identity providers or security tools. Your team imports exports into a table or uploads reports to Files, then makes access changes in the systems it uses today.
How do review and approval work for security work in TulipFarm?
An agent proposes changes to table records, and the person who owns the task approves the exact change before it's saved. A workflow can pause until a person responds, and a workflow step that sends a Slack message waits for approval of that exact message. Slack messages sent from chat or an agent task aren't held for approval, so check an agent's tools before you activate it.
Can other teams see our incident and vendor records in TulipFarm?
Only if you share them. Private chats and agent tasks are visible only to the person who owns them, and workspace admins can't see them either. Project members see their project's chats and files, and you can share tables and files with the people who need them.
How do I get started with TulipFarm for security, and what does it cost?
Sign up for TulipFarm Cloud. The public beta is open to everyone, and your first signup includes $50 in free credits. Public paid plans haven't been announced; see the pricing page to ask for more credits or apply for student, NGO or startup support. You can also take the browser tour, called Explore, without an account; it doesn't connect to your business accounts.
Start with one review.
Sign up for TulipFarm Cloud and set up the job you repeat most, like the quarterly access review or the incident log. The public beta is open to everyone, and your first signup includes $50 in free credits.
Want to check your tools first? Contact us about what your team uses.