From c03d5e7d3180bcdc3b4aae81fae4e09ce7004728 Mon Sep 17 00:00:00 2001 From: skyanth Date: Fri, 9 Jun 2017 16:43:17 +0200 Subject: [PATCH] implemented Incident Response Management template --- ...enText Doc Generation testing procedure.md | 6 +- xml/RELEASE_NOTES.md | 9 + xml/dtd/common.xsd | 12 +- xml/dtd/ir_quickscope.xsd | 88 ++++++ xml/dtd/offerte.xsd | 68 ++++- xml/dtd/quickscope.xsd | 4 +- xml/dtd/ratecard.xsd | 5 +- xml/source/contract_info.xml | 3 +- xml/source/ir_quickscope.xml | 40 +++ xml/source/snippets/localisationstrings.xml | 8 + .../offerte/en/intro_incident-response.xml | 6 + .../organizational_readiness_assessment.xml | 71 +++++ .../en/security_incident_management.xml | 93 +++++++ .../en/technical_artefact_analysis.xml | 54 ++++ xml/source/snippets/offerte/en/waiver.xml | 2 +- .../offerte/nl/planningandpayment.xml | 4 +- xml/source/snippets/offerte/nl/waiver.xml | 9 +- xml/source/snippets/snippetselection.xml | 53 ++-- xml/xslt/auto.xslt | 22 -- xml/xslt/generate_offerte.xsl | 14 +- xml/xslt/ir2offerte.xsl | 263 ++++++++++++++++++ xml/xslt/placeholders.xslt | 63 ++++- xml/xslt/qs2offerte.xsl | 3 + xml/xslt/rep2off.xsl | 5 +- xml/xslt/waiver.xslt | 7 + 25 files changed, 806 insertions(+), 106 deletions(-) create mode 100644 xml/dtd/ir_quickscope.xsd create mode 100644 xml/source/ir_quickscope.xml create mode 100644 xml/source/snippets/offerte/en/intro_incident-response.xml create mode 100644 xml/source/snippets/offerte/en/organizational_readiness_assessment.xml create mode 100644 xml/source/snippets/offerte/en/security_incident_management.xml create mode 100644 xml/source/snippets/offerte/en/technical_artefact_analysis.xml create mode 100644 xml/xslt/ir2offerte.xsl diff --git a/chatops/PenText Doc Generation testing procedure.md b/chatops/PenText Doc Generation testing procedure.md index ed69008..c3252aa 100644 --- a/chatops/PenText Doc Generation testing procedure.md +++ b/chatops/PenText Doc Generation testing procedure.md @@ -36,14 +36,14 @@ 10. For *each* option, check PDF Invoice: a. contents b. layout -11. From XML Quote, generate an XML Invoice +11. From XML Quote, generate an XML Invoice (that is XML, not FO/PDF!) 12. Check XML Invoice validity EXPECTED OUTCOME: document is valid 13. Edit XML Invoice: a. Add some bogus description and fee to `` b. Set @vat to 'no' for any service/cost 14. Check XML Invoice validity - EXPECTED OUTCOME: document is valid + EXPECTED OUTCOME: document is still valid 15. From XML Invoice, generate FO/PDF Invoice 16. Check PDF Invoice: a. contents @@ -85,7 +85,7 @@ 1. Use the `ratecard.xml` snippet and `generate_ratecard.xsl` to generate a FO/PDF Rate Card. 2. Check PDF Rate Card: - a. contents (do all placeholders resolve) + a. contents (do all placeholders resolve, do the rates have the correct denomination) b. layout ## Contracts diff --git a/xml/RELEASE_NOTES.md b/xml/RELEASE_NOTES.md index 2bbf1bb..f13eeae 100644 --- a/xml/RELEASE_NOTES.md +++ b/xml/RELEASE_NOTES.md @@ -1,6 +1,15 @@ RELEASE NOTES ============= +June 9th +-------- + +### Implemented 'Incident Response Management' template + +Works the same as `quickscope.xml`, only you use `ir_quickscope.xml`. Snippet selection depends on the presence of the optional `` element and its contents (other snippets are mandatory). + +Various little buglets have been squashed as well. + June 8th ('I'm seeing the world in shades of orange' edition) -------- diff --git a/xml/dtd/common.xsd b/xml/dtd/common.xsd index a6ee88d..cede145 100644 --- a/xml/dtd/common.xsd +++ b/xml/dtd/common.xsd @@ -116,15 +116,19 @@ + - - + + + + + @@ -262,9 +266,11 @@ + + - + diff --git a/xml/dtd/ir_quickscope.xsd b/xml/dtd/ir_quickscope.xsd new file mode 100644 index 0000000..30db9a8 --- /dev/null +++ b/xml/dtd/ir_quickscope.xsd @@ -0,0 +1,88 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/xml/dtd/offerte.xsd b/xml/dtd/offerte.xsd index 683f594..e00f2bb 100644 --- a/xml/dtd/offerte.xsd +++ b/xml/dtd/offerte.xsd @@ -13,9 +13,10 @@ + - + @@ -24,11 +25,12 @@ + - - + + @@ -43,18 +45,57 @@ - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -158,10 +199,12 @@ + + @@ -211,8 +254,13 @@ + + + + + diff --git a/xml/dtd/quickscope.xsd b/xml/dtd/quickscope.xsd index 3fed015..ad290bc 100644 --- a/xml/dtd/quickscope.xsd +++ b/xml/dtd/quickscope.xsd @@ -19,7 +19,6 @@ - @@ -33,6 +32,7 @@ + @@ -41,6 +41,7 @@ + @@ -62,7 +63,6 @@ - diff --git a/xml/dtd/ratecard.xsd b/xml/dtd/ratecard.xsd index 5aab931..68bda34 100644 --- a/xml/dtd/ratecard.xsd +++ b/xml/dtd/ratecard.xsd @@ -33,12 +33,12 @@ - + - + @@ -49,7 +49,6 @@ - diff --git a/xml/source/contract_info.xml b/xml/source/contract_info.xml index 93c61af..7334099 100644 --- a/xml/source/contract_info.xml +++ b/xml/source/contract_info.xml @@ -9,8 +9,7 @@ The contract snippets in this repo are provided as an example and should not be used for official contracts. It is the responsibility of the end user to edit the contract snippets and code so that the resulting contract is valid and watertight in the context of their own business operations and legal system. --> - fixed_term - + fixed_term battling the pirates Contractor diff --git a/xml/source/ir_quickscope.xml b/xml/source/ir_quickscope.xml new file mode 100644 index 0000000..3577e80 --- /dev/null +++ b/xml/source/ir_quickscope.xml @@ -0,0 +1,40 @@ + + + + + + + + + + + en + + incident-response + + + Incident Response Management + + + + + + 100000 + + Firstname LastnameExpertise with technical and organizational readiness + Firstname LastnameExpertise with technical and operational readiness + Firstname LastnameExpertise with technical and legal readiness + + + + 250 + + + 250 + + + + diff --git a/xml/source/snippets/localisationstrings.xml b/xml/source/snippets/localisationstrings.xml index 7855b60..4e7db8c 100644 --- a/xml/source/snippets/localisationstrings.xml +++ b/xml/source/snippets/localisationstrings.xml @@ -59,6 +59,14 @@ training training + + incidentresponsmanagement + incident response management + + + incidentrespons + incident response + VOOR FOR diff --git a/xml/source/snippets/offerte/en/intro_incident-response.xml b/xml/source/snippets/offerte/en/intro_incident-response.xml new file mode 100644 index 0000000..a5ef49a --- /dev/null +++ b/xml/source/snippets/offerte/en/intro_incident-response.xml @@ -0,0 +1,6 @@ + +

suggests to offer the following key incident response services to

+
  • Organizational readiness assessment for incident response (including a presentation and training session)
    • +
  • Security Incident Management
    • +
  • Technical Artefact Analysis
+

Prior to providing security incident services, strongly advises to conduct a ‘readiness assessment’. A readiness assessment analyzes the current state of and provides advice to prepare and improve its capabilities for incident response handling.

diff --git a/xml/source/snippets/offerte/en/organizational_readiness_assessment.xml b/xml/source/snippets/offerte/en/organizational_readiness_assessment.xml new file mode 100644 index 0000000..41bebca --- /dev/null +++ b/xml/source/snippets/offerte/en/organizational_readiness_assessment.xml @@ -0,0 +1,71 @@ + + +
+ Organizational Readiness Assessment for incident response +
+ Scope +

A readiness assessment analyzes the current organizational, operational, technical and + legal incident response capabilities of the client for specifically incident response + management:

+ +
    +
  • Organizational status analysis focuses on the governance and communication lines + both within the organization as well as with external stakeholders:
      +
    • Are there playbooks ready in case of incidents?
      • +
    • How will other departments and teams of + be informed in case of + incidents?
      • +
    • How will management be informed and advised about actions to be taken?
      • +
    • Will and if so how will external stakeholders of be informed?
      • +
    • +
  • Operational status analysis focuses on the ticketing, triage, assignment, + processing, and closure process of an incident. Underlying documents:
      +
    • Availability of documents, reports and logs (e.g. user accounts, contact points, etc.)
      • +
    • Quality of documents, reports and logs (e.g. level of detail, retention period, etc.)
      • +
    • Are there standardized procedures and systems in place for incident management?
      • +
    • +
  • Technical status analysis focuses on for instance:
      +
    • Asset management and information (do you know where +your systems are, specifications of the systems, up-to-date +network diagrams, etc.)
      • +
    • Analytics and monitoring environment
      • +
    • Other tools needed
      • +
    • +
  • Legal status analysis includes questions as:
      +
    • Communication and contacts with national authorities in +case of responsible disclosure of incidents
      • +
    • Existence and quality of procedures for contact with the +police, prosecutors and lawyers to maintain ‘chain of custody’
      • +
    • + +
+

The readiness assessment not only provides a picture of the current state and setup, but also includes recommendations for to improve its organizational, operational, technical and legal capabilities for incident response handling. Advice can be given regarding the architectural design of the organization as well as how to set up monitoring.

+
+
+ Prerequisites +

The client will provide at least one (1) single point of contact who will act as counterpart for the team. The point of contact will help in setting up interviews with e.g. other departments and management and respond to questions and requests from the team (e.g. information and/or access regarding systems).

+

An option would also be to hold a workshop and team exercise to assess incident response readiness.

+
+
+ <company_short/> team +

A team will carry out the readiness assessment. team members will be:

+ +
+
+ Effort +estimation and result +

The duration for the assessment will be two to four weeks (depending on +the access and speed of responses of the client’s contact persons to requests of the team). A report will be drafted after the assessment. The report includes a non-technical summary for management.

+

The number of person-hours estimated for a readiness assessment for incident response services is 160 hours. Part of the assessment will be a training day by the team to:

+
    +
  • to familiarize participants with the incident management process in detail; how to improve incident handling techniques, best practices for publishing communications about incidents, working with the media, and testing and verifying incident management processes.
    • +
  • equip participants with skills to work with information sources to +gather critical information, including open-source intelligence and proprietary intelligence as well as examining processes for information exchange.
    • +
  • expose participants to methods for incident coordination with a focus on how to handle major security events and coordinate incident responses with external entities
    • +
+
+
+ Pricing +

The costs for the readiness assessment are estimated at excluding tax.

+
+
diff --git a/xml/source/snippets/offerte/en/security_incident_management.xml b/xml/source/snippets/offerte/en/security_incident_management.xml new file mode 100644 index 0000000..d49abda --- /dev/null +++ b/xml/source/snippets/offerte/en/security_incident_management.xml @@ -0,0 +1,93 @@ + + +
+ Security Incident Management + +
+ Scope +

will work with clients and agreed subject matter experts and stakeholders to coordinate the response to information security incidents. Incidents are events that have a significant probability to compromise a client’s operations and/or assets. Incidents can be:

+ +
    +
  • Business E-Mail Spoofing / Compromise
    • +
  • System infected with malware (not detected by virus scanner)
    • +
  • Website was hacked or is serving malware
    • +
  • DDOS attacks
    • +
  • Policy breaches / bypasses of security controls
    • +
+

Actions of include:

+
    +
  1. response planning
    + will work with impacted client and relevant stakeholder to assess the status of the information security incident as well as to plan and agree actions to contain and mitigate the threat for the organization
    2. +
  2. response advisory
    will support clients with proposing actions to be taken to contain, investigate and communicate the information security incident
    3. +
  3. incident status updates and incident notifications
    will maintain regular incident status updates and report those to given contact persons. can draft communications for senior manager or third parties. can support in incident inquiries on request
    4. +
  4. technical analysis and incident management
    will provide technical assistance to resolve the incident and +advice to the client for actions to be undertaken
    5. +
  5. post-incident recommendations
    provides recommendations - to the extent possible from the information security incident - to the client organization improve their information security incidents prevention, technical and response capability
    6. +
+
+
+ Prerequisites +

The client will provide at least one (1) single point of contact who will support with planning including navigate the organization, assessing impacts, making decisions and coordinate execution of organizational tasks

+

The client collaborates with and enables to deliver the services by including to:

+
    +
  • provide organizational expertise and decision making
    • +
  • participate in incident calls and meeting
    • +
  • provide access to the client’s technical environment and systems
    • +
  • provide relevant information and data
    • +
  • use a template for data incident notifications
    • +
  • provide guidance on organizational, industry or country specific +policies, laws and regulations
    • +
  • if appropriate, provide appropriate access to communication and +data exchange platforms as well as data (like email)
    • +
  • if required, review, approve and perform official notifications to +authorities
    • +
+
+
+ Out of Scope +

Within the security incident management services WILL NOT:

+
    +
  • take decisions by itself that are in the remit of the client’s +responsibility (like shutting down servers)
    • +
  • provide information to anyone else but the client, agreed subject +matter experts and stakeholders during the incident
    • +
  • perform legally sound forensic data analysis and acquisition. +will suggest potential partner firms to the client who are licensed for legally sound forensic data analysis. can support in legal forensic analysis, but the client will be responsible for the data acquisition as well as establish and ensure compliance to the necessary procedures (such as chain of custody)
    • +
  • provide 24/7 security event monitoring; the client is responsible to alert in case of a potential incident
    • +
+
+
Service levels +

Security Incident Management Services are provided 09:00 to 18:00 CET. 24/7 support is available upon request and subject to extra charges.

+

A service request can be made through:

+
    +
  • email: incident@radicallyopensecurity.com
    • +
  • phone: to be delivered
    • +
  • PGP KEY: to be delivered
    • +
+

Specific service level agreements regarding response times are dependent on the current setup at and availability of personnel during incidents.

+
+
+ Effort estimation +

By nature a security incident’s handling efforts cannot be defined +beforehand. The case can evolve in different directions. In order to allow for a rough idea on potential costs, there are some rough estimations on work items and their estimated average time during incident handling. Work items include administration, preparation and wrap-up. All work items are discussed and agreed during incident handling.

+

For each work item a rough estimate is:

+
    +
  • Incident Status Call: ~ 2,5h
    • +
  • Incident Communication Draft: ~ 1h
    • +
  • Incident Update: ~ 1h
    • +
  • Incident Status Check: ~ 1h
    • +
  • Incident Interview: ~ 3h
    • +
  • Incident Review: ~ 4h
    • +
  • Technical assistance: ~ 1 to 40+h
    • +
+

After the incident, the incident documentation is key. For incident documentation we recommend to calculate ~ 1/5 of the incident’s overall handling time.

+

Important note: These are average estimates to give an idea of potential budget impacts.

+
+
+ Pricing +

Pricing +Incident response management costs per person-hour excluding tax and travel expenses.

+

The team will be formed based on the urgency and skills needed. Client team members can ‘peek over our shoulders’ during incident response management services.

+
+
+ diff --git a/xml/source/snippets/offerte/en/technical_artefact_analysis.xml b/xml/source/snippets/offerte/en/technical_artefact_analysis.xml new file mode 100644 index 0000000..4d55495 --- /dev/null +++ b/xml/source/snippets/offerte/en/technical_artefact_analysis.xml @@ -0,0 +1,54 @@ + +
Technical Artefact Analysis + + + +
Scope +

will support clients in analyzing technical artefacts of an +information security incident. This includes:

+
  1. Data Assessment
    + will analyze data, in particular for being or containing +malicious software
    2. +
  2. Analysis
    + will use practices and techniques to extract data and +indicators from artefacts such as E-Mails, files or malware
    3. +
  3. Attribution
    + will attribute artefacts to the best possible to known threats, +campaigns and exploited attack vectors
    4. +
  4. Indicator of Compromise
    + will use the incidents indicators of compromise and attribution to identify related information or other indicators
+ + +
Prerequisites +

The client will provide at least one (1) single point of contact who will act as counterpart for the team. Technical analysis requires the client to provide the correct, original data and potential context. This includes:

+
  • E-mails to be analyzed need to be the originally received e-mail with all its header information
    • +
  • (Suspected) malware must be attached in a zip or tar archive with password "infected"
    • +
  • Prior to submitting service request, the client validated that the data can be submitted for analysis without additional controls and in line with applicable policies, laws and regulations
    • +
  • must be informed about details on the artefact for any artefact submitted which does not contain all the original information
+
Out of scope +

Within the technical artefact analysis WILL NOT:

+
  • perform legally sound forensic data analysis and acquisition. will suggest potential partner firms to the client who are licensed for legally sound forensic data analysis. can support in legal forensic analysis, but the client will be responsible for the data acquisition as well as establish and ensure compliance to the necessary procedures (such as chain of custody)
+
Service levels +

Technical Analysis Services can be requested between 09:00 to 18:00 CET. 24/7 support is available upon request and extra charge +A service request can be requested through:

+
  • email: incident@radicallyopensecurity.com
    • +
  • phone: to be delivered
    • +
  • PGP KEY: to be delivered
    • +
  • RocketChat
+

Specific service level agreements regarding response times are dependent on the current setup at and availability of personnel during analyses.

+
Effort +estimation +

Technical analysis of artefacts can be easy and straight forward or be +very complex. In order to allow for an idea on potential costs, here are some rough estimations on work items and their estimated average time to analyze. Work items include administration, preparation and reporting aspects. For each estimate:

+
  • Malware Automated Assessment Report: ~ 0,5 h
    • +
  • Malware Manual Reverse Engineering: ~ 4h to 40+h
    • +
  • E-mail Analysis (Scam): ~ 0,5 h
    • +
  • E-mail Analysis including Malware: ~ 1,5 h
    • +
  • Analysis of IP addresses (<=10): ~ 0,25 h
    • +
  • Analysis of IP Links: ~ 0,25 h
+

Important note: These are average estimates to give an idea of potential budget impacts.

+ +
Pricing +

Technical artefact analysis costs per person-hour excluding tax and travel expenses. +The team will be formed based on the urgency and skills needed. Client team members can ‘peek over our shoulders’ during technical artefact analysis services.

+
\ No newline at end of file diff --git a/xml/source/snippets/offerte/en/waiver.xml b/xml/source/snippets/offerte/en/waiver.xml index afa10a0..5f8de7a 100644 --- a/xml/source/snippets/offerte/en/waiver.xml +++ b/xml/source/snippets/offerte/en/waiver.xml @@ -8,7 +8,7 @@

(), with its registered office at - , , and duly represented by + , , and duly represented by

diff --git a/xml/source/snippets/offerte/nl/planningandpayment.xml b/xml/source/snippets/offerte/nl/planningandpayment.xml index 34ac1f4..9fd1f47 100644 --- a/xml/source/snippets/offerte/nl/planningandpayment.xml +++ b/xml/source/snippets/offerte/nl/planningandpayment.xml @@ -2,12 +2,12 @@
Planning en Betaling

houdt de volgende planning aan voor haar werkzaamheden:

-

+

  • voert uit op het doelwit: .
  • levert het definitieve rapport: .
-

+

Ons vaste tarief voor de bovenstaand beschreven is ,- excl. BTW en bijkomende kosten. diff --git a/xml/source/snippets/offerte/nl/waiver.xml b/xml/source/snippets/offerte/nl/waiver.xml index 8af7d25..e9fe585 100644 --- a/xml/source/snippets/offerte/nl/waiver.xml +++ b/xml/source/snippets/offerte/nl/waiver.xml @@ -2,7 +2,7 @@ <company_svc_short/> - VRIJWARINGSVERKLARING -

(), statutair gevestigd te +

(), statutair gevestigd te , en in deze rechtsgeldig vertegenwoordigd door

OVERWEGENDE DAT:

@@ -28,9 +28,9 @@ in de veiligheid van deze systemen. zal zich daartoe toegang ve deze systemen om op zoek te gaan naar kwetsbaarheden. Vervolgens zal worden getracht dergelijke kwetsbaarheden uit te buiten om verdere toegang en verhoogde privileges te bemachtigen. zal de volgende doelwitten testen (de “Doelwitten”): -

-

2. verklaart hierbij en de Consultants – op een datum die + +

2. verklaart hierbij en de Consultants – op een datum die per email zal worden bevestigd – de meest uitvoerige toestemming te verlenen voor het uitvoeren van de opdracht, waaronder toestemming om:

@@ -58,9 +58,6 @@ tegen of de Consultants die door zijn ingescha ter uitvoering van de opdracht voor de Klant, dan zal zijn volledige medewerking verlenen aan in diens verweer tegen een dergelijk onderzoek of strafzaak, waaronder het verschaffen van bewijs dat verband houdt met dit onderzoek of de strafzaak.

- - - diff --git a/xml/source/snippets/snippetselection.xml b/xml/source/snippets/snippetselection.xml index 0d145df..7ed2542 100644 --- a/xml/source/snippets/snippetselection.xml +++ b/xml/source/snippets/snippetselection.xml @@ -101,6 +101,7 @@ waiver + introandscope @@ -114,6 +115,7 @@ waiver + @@ -136,7 +138,23 @@ waiver + + + + intro_incident-response + + + organizational_readiness_assessment + + + security_incident_management + technical_artefact_analysis + + + + + @@ -401,40 +419,5 @@ - diff --git a/xml/xslt/auto.xslt b/xml/xslt/auto.xslt index c66c9da..723f1f1 100644 --- a/xml/xslt/auto.xslt +++ b/xml/xslt/auto.xslt @@ -967,28 +967,6 @@ - - - Generated average rate is based on - 'juniorpentester' and 'mediorpentester' roles, which cannot be found in - client_info.xml - - - - - - -   - - - - -   - - - diff --git a/xml/xslt/generate_offerte.xsl b/xml/xslt/generate_offerte.xsl index 9c1da9c..39b6e67 100644 --- a/xml/xslt/generate_offerte.xsl +++ b/xml/xslt/generate_offerte.xsl @@ -10,7 +10,7 @@ - + @@ -61,13 +61,7 @@ - - - € - $ - £ - - + @@ -91,9 +85,7 @@ - - - + diff --git a/xml/xslt/ir2offerte.xsl b/xml/xslt/ir2offerte.xsl new file mode 100644 index 0000000..ea384b3 --- /dev/null +++ b/xml/xslt/ir2offerte.xsl @@ -0,0 +1,263 @@ + + + + + + + + + + + + + + + + + + + + + + + + + document meta information; to be filled in by the offerte writer + + PROPOSAL + + + + + + + + + + + + + + if there is a shorter way of saying the same thing, you can type it here (it makes for more dynamic offerte text). If not, just repeat the long name. + + + + + + + + + + + + + + + snippets/company_info.xml + + + + client_info.xml + + + + + + + + + + + needed for date on frontpage and in signature boxes; it is possible to add a new <version> after each review; in that case, make sure to update the date/time + + T10:00:00 + actual date-time here; you can leave the number attribute alone + ROS Writer + name of the author here; for internal use only + Initial draft + for internal use only + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/xml/xslt/placeholders.xslt b/xml/xslt/placeholders.xslt index 378b928..7d71853 100644 --- a/xml/xslt/placeholders.xslt +++ b/xml/xslt/placeholders.xslt @@ -2,6 +2,22 @@ + + + + + € + $ + £ + + WARNING: NO DENOMINATION FOUND + + + @@ -167,7 +183,9 @@ - + + +   @@ -217,7 +235,7 @@ - +   @@ -302,7 +320,9 @@ - + + +   @@ -346,6 +366,37 @@ + + + + + + +   + + + + + + + + + +   + + + + + + + + + +   + + + + @@ -367,11 +418,13 @@ - + + +   - + diff --git a/xml/xslt/qs2offerte.xsl b/xml/xslt/qs2offerte.xsl index 2790bef..2418932 100644 --- a/xml/xslt/qs2offerte.xsl +++ b/xml/xslt/qs2offerte.xsl @@ -29,6 +29,9 @@ document meta information; to be filled in by the offerte writer + <xsl:call-template name="getString"> + <xsl:with-param name="stringID" select="'coverpage_offer'"/> + </xsl:call-template> diff --git a/xml/xslt/rep2off.xsl b/xml/xslt/rep2off.xsl index de6e145..e5739c5 100644 --- a/xml/xslt/rep2off.xsl +++ b/xml/xslt/rep2off.xsl @@ -36,6 +36,9 @@ document meta information; to be filled in by the offerte writer + <xsl:call-template name="getString"> + <xsl:with-param name="stringID" select="'coverpage_offer'"/> + </xsl:call-template> client_info.xml - + diff --git a/xml/xslt/waiver.xslt b/xml/xslt/waiver.xslt index 08594dc..dcd2e6e 100644 --- a/xml/xslt/waiver.xslt +++ b/xml/xslt/waiver.xslt @@ -20,6 +20,7 @@ + @@ -57,6 +58,7 @@ + @@ -203,6 +205,11 @@ + + + + +