<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Engineering insight. Security in practice. on Actiotech | Software engineering &amp; application security</title>
    <link>https://actiotech.com/blog/</link>
    <description>Recent content in Engineering insight. Security in practice. on Actiotech | Software engineering &amp; application security</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 10 Nov 2026 09:00:00 +0530</lastBuildDate>
    <atom:link href="https://actiotech.com/blog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Checking permissions in Forge: when to use asUser and asApp</title>
      <link>https://actiotech.com/blog/forge-authorization-asuser-asapp/</link>
      <pubDate>Tue, 10 Nov 2026 09:00:00 +0530</pubDate>
      <guid>https://actiotech.com/blog/forge-authorization-asuser-asapp/</guid>
      <description>&lt;p&gt;A Forge app works perfectly when you test it as a Jira administrator. You switch to an ordinary project member, try the same action, and get a permission error. It can be tempting to change the API call from &lt;code&gt;asUser()&lt;/code&gt; to &lt;code&gt;asApp()&lt;/code&gt; and move on.&lt;/p&gt;</description>
    </item>
    <item>
      <title>What to check before putting a Forge Remote backend into production</title>
      <link>https://actiotech.com/blog/secure-forge-remote-integrations/</link>
      <pubDate>Tue, 10 Nov 2026 09:00:00 +0530</pubDate>
      <guid>https://actiotech.com/blog/secure-forge-remote-integrations/</guid>
      <description>&lt;p&gt;Suppose two customers use your reporting app. Both have a report numbered &lt;code&gt;42&lt;/code&gt;. The database keeps their records separate, but the remote backend caches a generated report under the key &lt;code&gt;report:42&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>What does an OWASP-based penetration test actually cover?</title>
      <link>https://actiotech.com/blog/owasp-from-top-ten-to-test-plan/</link>
      <pubDate>Tue, 10 Nov 2026 09:00:00 +0530</pubDate>
      <guid>https://actiotech.com/blog/owasp-from-top-ten-to-test-plan/</guid>
      <description>&lt;p&gt;“We need an OWASP test before launch.” It&amp;rsquo;s a reasonable request, but the next conversation needs to be about the application: which users it serves, what they can do, and what would go wrong if a control failed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using AI during a penetration test</title>
      <link>https://actiotech.com/blog/ai-assisted-pentesting-human-validation/</link>
      <pubDate>Tue, 10 Nov 2026 09:00:00 +0530</pubDate>
      <guid>https://actiotech.com/blog/ai-assisted-pentesting-human-validation/</guid>
      <description>&lt;p&gt;An AI tool reads an API specification and suggests a possible access-control problem. That might be a useful lead. Before it belongs in a penetration test report, someone needs to establish whether the endpoint exists in the tested version, whether the suspected behaviour is reachable, and what actually happens when it is tested.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Testing an AI assistant inside a Jira app</title>
      <link>https://actiotech.com/blog/testing-ai-features-atlassian-apps/</link>
      <pubDate>Tue, 10 Nov 2026 09:00:00 +0530</pubDate>
      <guid>https://actiotech.com/blog/testing-ai-features-atlassian-apps/</guid>
      <description>&lt;p&gt;Imagine an assistant that summarises a Jira project and offers to create follow-up tasks. In a demo, it reads the issues, writes a helpful summary, and creates a task when asked. Everything appears to work.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
